Weird w2k3 Server network performance –
Out of ideas on this one, thought I'd see if anyone had some ideas.
Have a client that just installed a new Dell file server over the weekend. Zeon, 1GB RAM--lots of nice, speedy hardware-nearly double the processing power of their previous NT 4 server they took out. 2003 Sever was installed on this, and everything replicated on the new box--same IP, Gateway, Subnet, DNS, etc configuration. No changes to Cisco 1100 Router. Blah Blah--essentially same setup ported to new OS and new Server.
External web access is fine (had to replace a dead DNS IP, otherwise no issues). Internal network is slower than molasses at Christmas. Client accesses to their DB on an AS/400 have started connecting intermittently, fails more often then connects due to timeouts. We can access the AS/400 via the web fine (we are over an hour drive away). They don't have an external client connection to try accessing via web--all clients connect on internal network, so we have not been able to test this (servers connect directly to Cisco, clients connect through switches and hubs). All clients access the web no problem, it is only the internal network that is problematic. Apps run locally on the server take forever to load (over 4 times the expected time). We timed one process at 25 minutes that took about 5 on a laptop. Files move across mapped drives between clients OK--but anything to/from the server is slower. Something appears to be polling the network constantly. Virus scan has come up with nothing.
My only experience with 2003 Server has been just today on a clean build that I have taken over internally. The OS was installed and preconfigured when I got assigned to it. All I've done is pull updates over a mapped drive and I've been terminalling in to run updates and such. The server is in a room that is only wired for external IP's and our switch hosting Internal IP's is full, so I can't even test that server's performance on our internal network to see if I can replicate their problem locally. It's an IBM, and runs smooth as silk with local app's and all file transfers.
They had recently had problems with their Linksys firewall and had to reconfigure it when the NT box was in place. They swapped out this with one from another site and replicated the configurations and the original is fine in it's new location and the new one had no affect on the issue. This was the only other change they have made to their configuration (the problem they were trying to fix was due to failing DNS entries--had nothing with the NAT).
Barring a hardware issue (they are contacting Dell about this), I am at a loss for what it could be in software. We've confirmed the TCP/IP settings--even threw in server IP's in LMHOSTS for good measure and nothing really seems to work. At first it looked like the LMHOST entries were going to help, but the connections still timed out. Pings work sometimes, sometimes they timeout. I am clueless as to what could be causing this flakey behavior. We haven't looked into the Cisco router for issues (I'm clueless about these), but their local IT claims there are no issues with it. Could it be something in 2003 Server that is causing internal slowdowns, but not affecting web access? It is just too weird!
Any one got any ideas?
If it ain't broke don't try to fix it! But, hell if you can tweak that bastard just a little bit more....hehehe.