Client machines loosing netshare connection

Hi
I have a Windows NT domain. I have all flavours of windows connecting to my NT4 sp6a PDC. A few problems with logon scripts but that is my other post.
I have recently been experiencing several 95 clients seem to loose the path to a network shared folder.
The clients have a shortcut to \\emtec2\serverf\development on their desktop. After logon connection is working. After a non-specific period of time clicking the shortcut produces the message that the resource is not available contact sys admin.
When sys admin arives (yours truly) I navigate using network neighbourhood to \\emtec2\serverf and close the window. Hey presto all the shortcuts work.
Does anyone have any ideas why this could be happening??

Oh I had better just add that the file server emtec2 is a win2000 domain member.

Many thanks for your time,
Paul

 

At a guess the file server is sitting on an AD domain that is too feature rich for the 95 clients to deal with.

We ran into the same sort of thing and finally figured out that 95 - which was never really made to play on a large network - was just getting confused. Same sort of symptoms you are seeing at first and then it got worse until the 95 machines were taking forever to log on and acting strange once they made it.

They even choked on an NT4 domain when we got too many shares with long descriptions. Solved that by removing lots of descriptions and shortening others.

The only AD fix we ever found was to get rid of the 95 boxes since any OS from 98SE on up can play on larger networks pretty well although you will do better with 2K-Pro or XP-Pro workstations since those operating systems were written to deal with large networks.

 

Domain is NT4 and server is just a domain member - no AD running.
Clients are both 95 and 98.
Looking now to reduce the number of shares.
Thanks for the reply Newt.

Paul