Axel
Guest
|
 Posted:
Sat Sep 17, 2005 8:51 pm Post subject:
Strange failure, simple solution |
|
|
I ran into a strange situation that I'd like to pass on to add to your
general knowledge.
I have a small lan with an SBS2003 server and a Windows 2003 server. I
decided to put the user's home directory file share in DFS for enhanced
availability. As part of the changeover, I removed the User share on the
SBS2003 server and set logon to map the user shares using DFS. This worked
fine for all but one workstation. That workstation previously had two user
home directories mapped to two drive letters and three other drives mapped
to other shares on the SBS server.
Now that workstation only had one share mapped to a drive -- the second
User's directory. "Net view <server>" could not "see" the DSF shares and
could only see the old Users share on the SBS server even though the other
workstations could see all of the shares. I checked the networking and
couldn't find anything amiss. Ipconfig and Ping did show anything different
from the other workstations.
I finally zeroed in on the lone share the workstation could see. Since this
share no longer existed, I theorized that the workstation was showing a
remembered connection and that was somehow masking the other shares. I
disconnected this mapping and restarted the workstation.
The workstation came up normally with two drives mapped to DFS User's shares
and the other drives mapped to SBS shares. "Net view <server>" showed all
the shares as did the other workstations. For some reason I don't fully
understand the lone remembered connect to the old share was preventing the
recognition of any other shares.
Any technical explanation as to why this happned would be appreciated,
otherwise just tuck this into your memory bank for possible assistance is
solving your next odd problem.
--
Axel Larson,
Share What You Know,
Learn What You Don't |
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in