Network Connectivity Problems

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi

I am using Windows XP Pro SP2. I am connected to my university LAN and my
network connection should ideally be up at all times. This is the case when I
run my computer on Linux but not when I run it on Windows XP. The problem is
that my network gets "hung up" every two minutes or so. This problem can be
tolerated when I am surfing since my browser caches in some information but
still I have to wait for the network to start (or I have to restart it
manually) for me to move on to next link. The problem is even worse when I am
remote connected to my university's mainframe via ssh (using Putty) or telnet
since the next set of commands have to wait for the network to be up again.

My IP, DNS, Gateway, Subnet and Hostname settings are the same as those that
I use on Linux and I believe that if they do the job on Linux they should
work on Windows too. Can you help me with this problem?

Any help will be deeply appreciated. Thanks
 
=?Utf-8?B?QXBvb3J2IEtodXJhc2lh?=
Hi

I am using Windows XP Pro SP2. I am connected to my university LAN
and my network connection should ideally be up at all times. This
is the case when I run my computer on Linux but not when I run it
on Windows XP. The problem is that my network gets "hung up" every
two minutes or so. This problem can be tolerated when I am surfing
since my browser caches in some information but still I have to
wait for the network to start (or I have to restart it manually)
for me to move on to next link. The problem is even worse when I
am remote connected to my university's mainframe via ssh (using
Putty) or telnet since the next set of commands have to wait for
the network to be up again.

My IP, DNS, Gateway, Subnet and Hostname settings are the same as
those that I use on Linux and I believe that if they do the job on
Linux they should work on Windows too. Can you help me with this
problem?
Click to expand...

To me this sounds like a connectivity problem. It could be that you
have a marginal 100 MB/s connection and under Linux your network card
configures itself for 10 MB/s whereas Windows might pick up on the
higher speed and then stall out when an error occurs on the wire. (The
two OSs use different drivers).

As a test, try bringing up the network connection driver settings in
the Device Manager
Start -> Run -> devmgmt.msc
Double-click on your network card and click on the "Advanced" tab. The
speed/duplex setting is usually on "Auto" which doesn't always work too
well. Try changing it to 10 Mbps/Full to see if this establishes a
more solid connection. Try other settings but make sure you note the
current settings so that you can change it back if needed.

HTH,
John
 
No John I tried your suggestion and tested all settings but it showed no
effects at all (except that the problem worsoned with some of the settings
which obviously will since these settings are not optimal). I will like to
mention that on this same computer when I was running Windows XP SP2 some one
year back such problems were not there. Recently I had to re-install Windows
on my computer and ever since then the problem has started to occur
 
Hi John and everybody else

I made a change and it worked. I had been using ZoneAlarm firewall and when
I checked the event viewer I saw that there were many logs of "TrueVector
Service" hanging and then dieing. This service is the firewall service of
Zone Alarm and was causing troubles. I have since then disabled ZoneAlarm and
connections seem to run fine.

Thanks for your help.
 
=?Utf-8?B?QXBvb3J2IEtodXJhc2lh?=
I made a change and it worked. I had been using ZoneAlarm firewall
and when I checked the event viewer I saw that there were many
logs of "TrueVector Service" hanging and then dieing. This service
is the firewall service of Zone Alarm and was causing troubles. I
have since then disabled ZoneAlarm and connections seem to run
fine.

Thanks for your help.
Click to expand...

Thanks for the feedback.
I was considering mentioning that the only thing left was a firewall
problem but decided against it. I'm glad you found the problem.

-- John
 
Back
Top