Networks

Ask something
Discussion Locked

Slow access after server replaced

0 helpful
7 replies

by lmayeda

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a small lan of about 24 users with NT, W2K and XP operating systems. The NT4 server was replaced with a W2K (Sp4) server and shared files were moved from the old server to the new one. Of all of the users, 2 in particular (one XP and one W2K pro) are super slow in retrieving any files ... shared network files AND files on their C: drives. These 2 happen to be laptops with docking stations. Other desktops have not problem accessing the same shared files. I tried undocking one of the laptops and connected it directly to the network but it was till slow. When the laptop is not connected to the lan, it can pull up files on the C: instantly. I have disabled the group policy (Digitally Sign Client Communications) on the server and rebooted both the laptops and the server but the response is still slow. Any ideas?

7 replies

by sgt_shultz

hmmm. anything in the event logs on the problem pcs? nice test, taking it off the network. wonder if you need to test problem computers for viruii and spyware. and put on all the security patches. in case slowness is due to worm generated traffic. sounds like could be name resolution problems maybe. do you have dns and gateway settings correct on problem pcs. i would say try another nic but you did when you undocked, correct?. also try locking the nic's media type down to 10mb half duplex or up to 100mb full duplex. could be browse issues. you on a domain or workgroup? see if you can get a hold of the browsstat tool on nt resource kit or download from ms website. the whole 2003 server resource kit is available there and might have interesting tools for this (they will probably work fine on your os versions). maybe browse master war or corrupt list that is taking forever to get refreshed. how long ago did this server replacement take place?....another thing i would try is removing all unnecessary protocols, like ipx and netbeui if they are installed. keep netbios over tcpip enabled. also ditch unused network services. did you ever have a netware server on your network?

by lmayeda

Thanks for responding, too bad there is not an option to "keep talking". The new server went in a week ago (everything should have replicated by now) and the slowdown was an immediate response after the installation. I also think it is authentication issue because when I tried to logon to the laptop as a different network user, it could not find the domain. DNS and gateway settings look correct. If browse master war wouldn't the other PCs on the network experience the same slowdowns?
The Event Viewer on the new server has messages for several of the network PCs (not all) that it has lost the SID, including the 2 laptops in question. In spite of these messages some of the PCs (with lost SIDS) have no problem accessing shared files. I will try to unjoin one of the laptops from the domain and rejoin ... in hopes that the SLOWNESS issue can thus be resolved.

by pctech

Hi

I would look to see that the laptops do not haved mapped shares that no longer exist or the computer(s) they are mapped to are not down. I have seen this cause this issue. I would also check the network drops and hubs/switches/routers that these laptops connect to the network with.

I hope this helps

by lmayeda

Got rid of all old mapped shares. Don't think it's the hardware because the problem appears only after the server was switched out.

by omie

You didn't mention whether you upgraded the NT 4 server to win 2k or you kept the old server as a backup domain.

To tell you the truth I frown on upgrades. It creates a lot of problem. I would rather go for clean install especially you mentioned that you have only 24 users.
If you kept the old server as a back up server there is a chances that you are having a problem in the replication in terms of the old policy carried over to win2k server.

For the user it is also nice to check the active directory and make sure that the user name is also in the win2k domain not only in the pre win2k domain. If they are not there is chances that when the user log on .. it is looking for win nt server.

Another issue is that you are sharing files in their C: drives.. I think it is better to put all shares in the server for there is a chances that the workstation won't allow access on the C: drive specially when it has something to do with the user profiles. a good example is the "my documents"

Again review the security policy that was inherited by the win2k from winnt because win2k is more restrictive compared to win nt.

good luck

by lmayeda

Thanks for the answer. Server was a new one and the old PDC was removed from the network.

Actually ... I accidentally found the answer while "dickering" around on the laptop. There is a parameter on the mapped drive to allow Indexing Service. I unchecked it ran the test (still slow) then reenabled it and VOILA! Access to all files w/n the mapped drive is fast again. I don't understand exactly what Indexing Services but it makes sense that if the data was moved from one server to another, the indices would have all changed. Thanks for the effort everyone.

This discussion is closed to new replies.