Networks

Ask something
Discussion Locked

Losing connection to File Server

0 helpful
7 replies

by william

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have several workstations that occasionally lose their connection to the Windows 2000 file server after they have been idle for awhile. Files on the server are no longer accessible. You have to reboot the workstation and you can log on again. (A simple log off/log on doesn't work.)The operating systems of the workstations range from Win 98 to Win ME, and have different brands of nics. Two different 2000 servers do this. Microsoft admits this is a problem with 2000, but won't give a solution online. All machines use NetBEUI protocol

7 replies

by frobo

Hi,

i would get rid of the netbeui protocol !
Take Tcp/ip and implement it at the Server and client side. Install DNS and Wins (Wins is alive !) for nameresolution. Implement DHCP for administration, it make your'e live easier. Take an private Ip-Range like 192.168.x.x (c-class) or 172.16 to 172.31 (b-class) etc. Plan your IP-design very well, and think about the future.
Update client OS from w98 to w2k Pro or what ever, make 1 standard Client OS, so you have to support only one Client-OS.

After this live of administrator much easier.

Frobo

by william

2 problems. One, I prefer not to get rid of NetBEUI. Plus since I have researched this problem some more that wouldn't help. Two, I know upgrading clients to Win2000 would get rid of this problem, but that is not a financial possibility. Plus Win2000 on a desktop causes more problems than solutions. Thanks for the help anyway.

by oliviu

I suppose you have a domain controler that authenticates the network login for your clients machines.
Define the same users using the same passwords on the file servers. This may solve the problem.
Also, are you able to see the file servers in thenetwork from the clients and the clients from the file servers?

by william

Thanks, but I have done the above and that didn't help. But I have found 2 things that have helped.

1) The WIN2K Server CD includes a file, DSCLIENT.EXE (in the \CLIENTS\WIN9X directory), that needs to be installed on every client machine that uses any OS lower than WIN2K. It allows the client to use KERBEROS authentication. 2) AUTODISCONNECT on the Server needs to be shut off. Do this from the Command Line... Net Config Server /autodisconnect:-1

I am not certain if these solutionsactually solve the problem. But after a week I have only been disconnected once, versus 1-2 times a day prior to that.

Microsoft online tech support DOES NOT tell you about #1, and admits #2 is not documented.

by gihan.jayasundera

Make sure you have the latest driver updates for your NIC Cards, on Win98 and ME. Win98 disconnection should be fixed after updating the drivers for the NIC. On the WinME computers there is an option on the IP Configuration screen. This is the option to detect new network media. If you uncheck this box, it should work like a charm.

Gihan

by william

Read Above... I found the answer myself as I previously responded. Answer # 2 turned out to be the correct solution. When you first install WIN 2000 Server, Autodisconnect is automatically set to 15 minutes! Therefore, idle workstations can lose their network connection. ONE problem though... whenever you reboot the server, the NET CONFIG SERVER command gets reset! The Autodisconnect time reverts to 18 hours instead of OFF. You have to re-enter Net Config Server /autodisconnect:-1 at the Command Line.

This discussion is closed to new replies.