Users Mapped Drives deny access after inactivity

[d1onysus]

I have a AD domain with about 40 users on it. I had to wipe a Win 98 machine and install XP Pro on it. Joined the PC to the domain with no issue. User signs in and gets access to her mapped drives fine.

The next day, either if the PC is logged out or shut down, the user logs into the domain, gets her mapped drives, But when she trys to access the network drives she gets the error "cannot connect to the Drives, device name already in use". If I log in as another user, I get the same error when trying to access that persons network drives. If I log in as Domain administrator, there is no login script mappings when admin logs in, but if I browse to the AD/File server, It prompts me for my admin credentials again before letting me on the server.

The only workaround is to join the computer back to a workgroup, and then join it back to the domain. This process has to be done daily for the user to get the share drives.
Any Ideas?

 

[d1onysus]

I'm bumping this once to see if anyone has input on this issue....Thanks.

 

[Davetoo]

Do not bump posts. It's poor manners and not appreciated on this site.

If someone can help, they will. If not, sorry.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[rpiver]

From the sounds of things, it sounds like there were some existing drives mapped without a login script. Then the login script executes and "apparently" maps some more drives with a different login name to the same server(I'm assuming this because of your statement about getting prompted for credentials again)

This is what I would try.

Login as the User to the domain

Document the drive mappings

Disconnect all the mapped drives manually at the XP computer

Map one of the documented drives manually. Does it prompt you for credentials?

If it does prompt you, then for some reason, either that server, where you are mapping the drives too,is not synchronized with the rest of the domain or it is not part of the domain and the users password is not the same on the server where the mapped folder is. Or it could be that that user does not have access to those particular folders.

If you have a trust setup it could be that the trust needs to be synchronized or re-setup.

Try the above steps and let me know.

Some General Questions and possible pointers
Is the server or device to which the drives are being mapped to part of the domain

Is there something in the login script that requires the user to have elevated permissions. You could also try granting the Domain user administrator privileges on the LOCAL computer and seeing if that helps.

Does the computer show up in Active Directory Users and Computers?

Are there any GPO's setup?

It could be that the users profile is corrupted. Do you use Roaming profiles?


Hope some of this is helpful

Rad Piver

http://www.globalstrata.com

 

[d1onysus]

I figured it out, apparently the last "IT" guy had no dhcp working on the AD servers, and had every one aquire a address from the linksys router they had for the outside. Then he would put a static DNS address in the PC's otherwise they would get the outside dns numbers. I didn't see it on the WIN98 PC that I upgraded, but on the XP machine I saw error 1053 and error 1054. Since these are DNS related issues, I then realized what I was missing. I'm not totaly sure how they were getting to the server at all.