Windows Forum

Ask something
Discussion Locked

Multiple share mappings on a Stand Alone

0 helpful
6 replies

by legj1 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I can map multiple shares on a stand alone win2k server, but when I logoff and log back on, the connections are not restored. I am prompted for PASSWORD for the share at logon, but it fails every time. However, if I map to one share on said stand alone, I can re-connect without fail after logoff. I f I connect to multiple shares using a a WInNT box, I have no problems. Also, if I remove my PC from the domain, I have no problems mapping shares. What domain security/password parameter could be causing this problem? Is there a configuration that will allow me to connect to multiple shares outside the domain to a stand alone server? All help is very appreciated! Thanks

6 replies

by joseph moore

Ok, so the Windows 2000 Server is a stand alone, not a member of your domain, and you are mapping drives that exist on your PC to the Win2K machine? That is the setup?
Ok. Since the Win2K server is NOT a domain member, then the account you are using to log into the Win2K box is, therefore, NOT a domian account. It is a local account that exist on the Win2K box only.
So, you log in locally, then manually map some drives to the remote PC that is a domain member. During the mapping process, you have to supply logon credentials that are acceptable to map drives. These credentials are, most likely, a domain account.
The reason you have to type in your password when you log back into the Win2K machine is that, eventhough you click the Reconnect at Logon box during the drive mapping step, the password you used is NOT saved on the Win2K box. What happens is the account you are logged in with (the local Win2K account) is passed along with the \\PC\SHARENAME drive mapping path. Well, since the \\PC\SHARENAME security permissions do NOT know your local Win2K account (again, it is not a domain-wide account so domain members don't know the account) the authentication to map the drive will fail.
You then get prompted to enter in the password.

by joseph moore

Part 2:
You have 3 options to prevent this. 1) make the Win2K box a member of your domain.
2) keep the PC in a Workgroup instead of being a domain member. (BTW, the reason the drive mappings work when your PC is NOT a domain member is that, I theorize, that both the PC and Win2K box are both members of a workgroup called WORKGROUP. And I am also theorizing that the account you are using to log into the Win2K box matches a local account that exist on the PC. This is a trick with Workgroups. If 2 machines that are both in a workgroup with the same name, and if they both have an account with the same logon name and password (say, Administrator with a blank password), then both machines see the security identifier (SID) as being the same. Therefore, both machines allow access from the other, since the security credentials match.)
3) When you do the drive mapping on the Win2K box, after you put in the \\PC\SHARENAME path, click the link that says "Connect Using a Different User Name".Choose this option, and put in a domain account that has rights to \\PC\SHARENAME.

Hope this helps.

by legj1

I appreciate your work and will award points accordingly. I was hoping #3 suggestion would work. However, it does not. I can point the share to use my domain ID and password, but after re-booting, the share wants to default to domain credentials...and the local (stand alone) crudentials will fail. My problem is the AS/400 because it cannot really join a domain. As you know, it is a mainframe that performs its own authentication and acts as a domain in itself. It is just very strange that a NT box on the domain can map multiple shares to a stand alone 2k server, but a 2000 client cannot. Something is very different w/ 2000 security on the domain level. Oh well! For such hard work, you get the points. If you have ANY other suggestions, please let me know. Thanks again!

by legj1

Somewhat helpful...but I already know this is a fix. My question was HOW to get around this prob. Thanks anyway though.

This discussion is closed to new replies.