SBS 2003 intermittant slow network
I recently impleneted a SBS2003 new server, replacing an old Dell WIN2000 server. Mysteriously users are complaining that QBooks and Excel spreadsheets are taking forever to open. Workstations are freezing waiting, etc. Old server was ABC.com as the domain, and I changed it to ABC.local and had all the workstations properly transitioned over. Seems to happen between 8:50 and 9:30AM then it gets "better" for the rest of the day. There are NO scheduled tasks happening in that window. Basically nothing has changed except the new much more powerful server.
The only thing I can admit to that I've read here is that I have the IP's hardcoded. Including the workstation level DNS with the server first, and a public DNS second.
They are complaining that the old server allowed them to do everything fine, and the problems started after the new much faster server.
Where to start looking? MANY thanks in advance.
The only thing I can admit to that I've read here is that I have the IP's hardcoded. Including the workstation level DNS with the server first, and a public DNS second.
They are complaining that the old server allowed them to do everything fine, and the problems started after the new much faster server.
Where to start looking? MANY thanks in advance.
Does your server have 1 or two nics. How are they Set?
ASKER
Server has 2 nics. Only 1 is used. I read here that using 2 is really for protection against failure of one of the nics.
Would using 2 help? The old server had 1 nic.
Would using 2 help? The old server had 1 nic.
You could re run the wizard just to check your settings ips dns etc
Can you confirm only one dhcp on the lan
In the past I have always setup sbs 2003 with two nic config
One nic for Lan and the other for WLan. I use the wizard to do this making sure i have Ip's and Service providers DNS to hand.
Can you confirm only one dhcp on the lan
In the past I have always setup sbs 2003 with two nic config
One nic for Lan and the other for WLan. I use the wizard to do this making sure i have Ip's and Service providers DNS to hand.
ASKER
Good advice, but how would that explain the intermittent nature of the problem. And the old server only used one old crappy nic.
You mentioned problem happens in the morning. Is this when everyone is starting up Nic in the sbs server could be faulty causing slowness due to load of users starting/Logging in.
You could try the nic from the old server if its not on board atleast you have a known good variable with the old nic.
You could try the nic from the old server if its not on board atleast you have a known good variable with the old nic.
ASKER
I appreciate the path you are on, but that wouldn't be it. They all get in at different times.
ANy other suggested areas?
ANy other suggested areas?
forgot to mention you could disable current nic and enable spare in sbs2003 box
if you get the same problem then there could be a dns routing issue. are you getting any DNS events?
ASKER
I have workstations all with primary DNS as server and secondary as public ISP DNS.
I have server with itself as primary and Public DNS as secondary.
Only DNS error is the "update its own A rec" thing. It happens rarely.
I have server with itself as primary and Public DNS as secondary.
Only DNS error is the "update its own A rec" thing. It happens rarely.
IF you accept there have been no changes to clients to cause this slow network then the common denominator is the new sbs 2003. swap nics and see if fix or same. If problem remains I would check router/switch and DNS in SBS 2003. Failing this I would get network analyser to look for network traffic
I have had faulty client nics and bad ports in switchesw cause network problems so I do not assume unless tested as ok
I have had faulty client nics and bad ports in switchesw cause network problems so I do not assume unless tested as ok
ASKER
Ok, I will do that. I'll get back to you. Thanks for your great responsiveness on this. I appreciate it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I wonder why the QB app was not causing this problem on the old server? Glad you got it sorted.
ASKER
The QB documentation says all you have to load is the database server for the QB database. But you actually have to load the QB program AND the database server because you have to use the program to set up the multi-user host profile on the server. Then you never run the program again. I didn't have the program loaded until I dug that little fact up.
QB is a royal pain. Thanks again.
QB is a royal pain. Thanks again.
ASKER
The QB documentation says all you have to load is the database server for the QB database. But you actually have to load the QB program AND the database server because you have to use the program to set up the multi-user host profile on the server. Then you never run the program again. I didn't have the program loaded until I dug that little fact up.
QB is a royal pain. Thanks again.
QB is a royal pain. Thanks again.
Thanks for the update.
ASKER
Off topic, but where are you located? It's 2:57AM here in Arizona.
London UK 11.00am
ASKER
I should mention only 8 workstations on network.