G
Guest
Assume two PC, (both running Windows 2000) PC-A and PC-B are part of the same
domain at some stage. We have a user logon to PC-A as domainX/userX and it
setup a mapped drive (say M to access resource from PC-B. Assume the
resource is \\10.20.1.20\sharename (PC-A and PC-B still reachable from the
network)
Say from now on PC-B is no longer part of the domain. If we still need its
share be available, as M: drive in PC-A as before, I think it is still
possible. Can someone explain how it works now? I think we still map M: to
\\10.20.1.20\shareName.
PC-B is now not part of the domain. I can't remember if
a) its privous credentials, say domainX/userX to access the share has been
cached or
b) is simply rejected because it is now not part of the domain.
How does it compare when a user in PC-A is going to signon as
a) domainX/userX, or
b) local user in PC-A
Also how do we properly link the mapped drive in order we don't need to
re-connect the share everytime PC-A is rebooted?
domain at some stage. We have a user logon to PC-A as domainX/userX and it
setup a mapped drive (say M to access resource from PC-B. Assume the
resource is \\10.20.1.20\sharename (PC-A and PC-B still reachable from the
network)
Say from now on PC-B is no longer part of the domain. If we still need its
share be available, as M: drive in PC-A as before, I think it is still
possible. Can someone explain how it works now? I think we still map M: to
\\10.20.1.20\shareName.
PC-B is now not part of the domain. I can't remember if
a) its privous credentials, say domainX/userX to access the share has been
cached or
b) is simply rejected because it is now not part of the domain.
How does it compare when a user in PC-A is going to signon as
a) domainX/userX, or
b) local user in PC-A
Also how do we properly link the mapped drive in order we don't need to
re-connect the share everytime PC-A is rebooted?