Removing share disconnects user from entire server and other shares
Posted on 2006-11-28
I have a Win 2000 Server. The server is set up with the following directory structure:
d:\ (security with everyone & authenticated users full control - not shared)
d:\login (security & shared with everyone & authenticated users full control)
d:\shared (security & shared with everyone & authenticated users full control - security on sub folders)
d:\users (security with everyone & authenticated users full control - propegates down - not shared)
d:\users\username (each users is shared as username$ with permission on the share for that user, security is inherited)
The login script is run from \\server2k\login. The login script maps each user's X drive to \\server2k\shared folder and each user's U drive to \\server2k\username$.
This works fine and has for some time.
I've recently added a Windows 2003 server and am moving the "U drives" (the users personal directory space) to the new server. To do this, one by one, I've had the users close their mail (address book and pst files on U drive) and any network files. I copy their username directory from server2k to server2003. I remove the share on server2k and rename the folder username-moved. On the server2003 I set up the share to usersname$ and set the permissions as before. When the login script runs it runs off server2k and then maps the U drive to server2003 since that is where it finds the share.
This has worked for about 40 users. Howerver, I have 2 users with an unusual problem. I'm not sure what else to try. On these two users, the second I unshare the \\server2k\username$ share they get a pop up that they are disconnected from \\server2k. I'd expect the disconnect from the "U drive" which is mapped to the username$ share, but it also disconnects them from the X drive which is mapped to \\server2k\shared (with everyone and authenticated users full control) and they can no longer access the \\server2k\login share - so they can't run the login script. I can ping server2k fine from the machine when it is "disconnected". I can reboot the client machine (XP) and/or reboot the server and cannot attach to \\server2k for these 2 users. I can log in on the client machine with my account and connect to the server just fine (which tells me it is account related). If I put the share back on the \\server2k\username$ folder they immediately have access to all the shares on \\server2k.
WHY does removing one share disconnect them completely from all shares on that server and not let them connect to them at all even after a reboot?? Why is this only happening for 2 of my users.
The user accounts are NT accounts. We are doing all this moving in preparation tomove the users into Active Directory accounts, but for now I need the NT domain accounts to continue working. I could try explicitely adding these users to the shares I need them to access, but it shouldn't be necessary since everyone else works fine.
Any suggestions would be greatly appreciated.