Windows Forum

Ask something
Discussion Locked

New Windows 2K Server Problem

0 helpful
6 replies

by natecasp

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have recently installed our first Win2K server into our production environment. It is a new file server that has replaced an existing NT 4.0 server. We transferred all the data over to it and it seems to work good for all our internal employees. However our employees that are coming in on the WAN through our frame relay circuit are having a lot of network problems. These include not being able to access our their Lotus Notes config id file and also having problems accessing MS Access databases. It has been diagnosed be the new server and the problem looks like the clients are timing out. Lotus Notes is especially sensative to timeouts and so are Access databases so this is why I think it is the problem. We are only running TCP/IP on theserver and I have already tried moving the server to a different Ethernet switch without any success. Does anybody know why this server is not performing for our WAN clients.

6 replies

by shmaltz

If the users access the files thru regular windows file sharing (not FTP or HTTP) there should not be any time out problems because windows will not time you out. It rather looks like a network problem at one of your routers that are making the problems.

by natecasp

I know it is not one of the routers because I have tried mapping the users drive back to the old NT 4.0 server and all the problems go away. This isolates the problem to the W2K server. Both the old server and the new server are plugged into the same Ethernet switch and using the network infrastructure are identical.

by shmaltz

Can you ping the 2k server form the other network? If yes can you ping the other network fromt the 2k server?
If the answer is no to any of the 2 questions then the problems is in the IP routing. Maybe the old server are setup with some static routes?

by shanghai sam

Pings make it thorugh. In fact, sometimes the Notes and databases work but not often and it is very sparatic. It looks just like a timeout problem. That is why I am shocked to find out that W2K has no timeout. I really can't believe that. Does that mean that if you request something from the server and the server does not respond in time the client will wait forever? Maybe the clients are timing out. However why would they only timeout on the W2K server and work find with the old server?

This discussion is closed to new replies.