2000 server slow browsing

I'm running a Windows 2003 AD domain with a mixture of 2000 and 2003
servers.  Everything works fine except that one of my 2000 servers is
very slow to browse, it's been this way since I installed it, but it's
starting to bug me now.  When I drill down to "microsoft windows
network", it takes about 30 seconds to show the one available domain,
then when clicking on the domain, it takes about another minute to show
the available computers in the domain.


This server isn't running anything out of the ordinary, mainly IIS and
SQL Server, and it has a gigabit link.  The workstations that use it's
apps don't have a problem running the apps, and they're still fast,
it's just slow browsing from it.


has anyone run into this sort of thing before??


thanks
Randy


 
rhcellxionAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

glenn_1984Commented:
How much free drive space is available on the server?  Does it need to be cleaned up.

Check Task Manager, Processes to see if anything is eating up CPU time.
rhcellxionAuthor Commented:
Machine is running dual 2.8GHz processors and never reaches more that 5% when browsing.  Drive space is fine - 10GB on C, 150GB on D (RAID5), 2GB Memory.
glenn_1984Commented:
Take a look at:

http://www.experts-exchange.com/Operating_Systems/Win2000/Q_21458162.html

Also, is anti virus set to scan all files when you  open them, or only on create and modify.
rhcellxionAuthor Commented:
I checked out the article, and it's not a resolution issue, and there is no netbeui running and it's not multi-homed.  Just so I'm clear, the workstations get to it fine, but it's the server itself that's slow to browse.

One thing I did find strange is that when I ran "nbtstat -n", I got results that I would expect, but there was an extra entry that went like this:
"\Device\NetBT_tcpip_{EAE24DE4-D2EF-4FD8-B797-B4C77A1EDE70}:  Node IPaddress [192.168.234.235]  ScopeID: []"  then it give me the results in the name table.   I have another machine that browses fine, but gives me the exact same results execpt give me "no names in cache".

I don't know where the Node IPaddress [192.168.234.235] portion comes from because it's not in my range of addresses.

glenn_1984Commented:
Did you check your anti virus to make sure it is not scanning files on view?

Are you running any insight managers?

Is the server under warranty? Will hardware Tech help.

Maybe these sites will give you a clue:
http://www.chicagotech.net/winslow.htm#Slow%20opening%20Windows%20explorer
http://www.ms-mvps.com/winslow.htm



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.