Browsing Network very slow for 1 w2000pro workstation

  • Thread starter Thread starter NewsGr
  • Start date Start date
N

NewsGr

This is updated with SP and patches to date. It is in a win2003 domain.
There are about 40 other workstations that have no issue browsing. I just
noticed it when I was working with this user. It takes about 2-3 minutes
just to get the domain to appear in the prowse window, it then takes about
2-4 minutes for all workstations to show up and even longer to connect- time
out sometimes. I checked all obvious solutions such as broken
connections, spyware, bad network connection, event log etc. Nothing shows
abnormal in event log and ping returns normal speed with IP only.

Anything else could cause this?

thanks

CR
 
More than likely a DNS and or WINS or firewall issue.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| This is updated with SP and patches to date. It is in a win2003 domain.
| There are about 40 other workstations that have no issue browsing. I
just
| noticed it when I was working with this user. It takes about 2-3 minutes
| just to get the domain to appear in the prowse window, it then takes about
| 2-4 minutes for all workstations to show up and even longer to connect-
time
| out sometimes. I checked all obvious solutions such as broken
| connections, spyware, bad network connection, event log etc. Nothing
shows
| abnormal in event log and ping returns normal speed with IP only.
|
| Anything else could cause this?
|
| thanks
|
| CR
|
| --
|
|
| I don't suffer from insanity, I enjoy every minute of it!
|
|
 
More than likely a DNS and or WINS or firewall issue.
Click to expand...

Ive found removing the pc from the domain, deleting computer object and
adding back again to resolve this type of issue, occasionally had to do
this - almost like credentials not working properly.

Check it has correctly both a forward & reverse dns entry, or even a
possible duplicate entry with different ip address's.

Also, updated network card driver resolved it once before.
 
Back
Top