We have a small group (3) of 2000 Pro workstations which are not members of
our domain. Our network file server is a 2003 R2 server.
We recently migrated from Novell to Windows for file and print services, for
two weeks after the conversion everything seemed to work fine. A week ago we
began having trouble from a the 2000 Pro workstations I mentioned earlier.
On these workstations I can map a drive to the file server and everything
works fine. As soon as one of the other workstations access the same drive
mapping the other two disconnect. If we open Explorer, we see a red X on the
drive, clicking on the drive reconnects kicking out anyone else accessing
(within this small group of computers).
We are accessing the server on another LAN segment, and the problem occurs
when accessing any of the 2003 servers. It does not happen when we place the
files on a Suse SAMBA server.
I have made adjustments to the auto-disconnect settings on the servers and
the workstations, tried using UNC paths instead of drive mappings, and made
changes to Symantec Client Security. These were all the KB articles I could
find which seemed to have the same symptoms.
|