Domain help

J

Jeffman

Gawd
Joined
Jul 23, 2008
Messages
917
Hey guys/gals,

I'm lost and think I need some advice.

At work, we're replacing a few computers. Going from Windows 7 to Windows 10.

2 of the computers, the primary users aren't having one of the drives mapped automatically. There are 3 mapped drives, all on the same server, all mapped by Group Policy. 2 of those map fine, the other one fails. Net Use show's it's mapped, but when we try to pull it up and enter their credentials, it says "Access Denied".

I can log into these computers as the domain admin, and have no problem accessing the drives.

I can log in as another user, and have no problem assessing the drives.

Permissions never changed. It worked fine on their old Windows 7 computers.

I know the computer can access the server and drives fine. I know that these users can access the drives from non-Windows 10 computers.

Am I going insane? What am I missing here?

Any help is appreciated. Thanks a ton!
 
I would blow away the user profile and kill it from the registry. Have the user relogin and see if it maps right. I would also look at the event logs for gpo failures etc... Also what version of smb is enabled on the file server? If only lower versions are turned on then is can also cause issues
 
^Is that necessary when it's a new computer and a new account for them already?

I'm not sure on SMB versions...I'll see if I can check. Would that matter if other users can access the drives from the same computer?

Sorry if these are stupid questions...I'm not great with domains...I know enough to do most of my job without trouble.
 
Jeffman said:
^Is that necessary when it's a new computer and a new account for them already?

I'm not sure on SMB versions...I'll see if I can check. Would that matter if other users can access the drives from the same computer?

Sorry if these are stupid questions...I'm not great with domains...I know enough to do most of my job without trouble.
Click to expand...
your other machines are windows 7 which has lower versions of smb enabled. On windows 10 it could be different. I am more of infrastructure/server guy but I have done my share of desktop support. Just trying to give you some ideas.
 
^It's working on other Windows 10 machines with no problem. Same group memberships too. It's something with the user, not the computer. But other users in the same groups on the same computer have no problem...and the user doesn't have anything that would *restrict* them set in permissions anywhere.

That's why I'm so confused. I don't see a single reason or point where it failed. It just denies the access to them, but there's no reason I can see.
 
I should add, in Net Use - the drive is mapped. But this user just can't access it.
 
Maybe kill all sessions on the file server. If this user logs into another 10 machine does the issue follow them?
 
^No. I just remoted into another Windows 10 computer using their account, and it worked as it should. Same network, same subnet, same user, just a different computer.

I can log into the computer in question as another user in the same group (not myself as the domain admin), and it will work. But for this user it won't.

I have this problem with 2 users and their new computers.



No roaming profiles.
 
Are they local admins?

I agree with the post above, something's wrong with the user profile if the same user account works on one but not the other.

Try unjoining and then rejoining the machine on the domain.

.
 
They are local admins on their computers.

On the first machine I tried a disjoin and rejoin on the domain. No go.
 
Wow...it works if I leave out the drive letter I'm mapping and just add in the server name and folder.

Which is weird because this is what Group Policy is set to do. The Net Use drive mapping was correct. I always add the drive letter when I manually map it.

I don't get it. I'll have to try a few reboots and see if it stays.
 
Try turning off hidden empty drives.

Example: You are trying to map "H" drive but the machine has a multi-card reader with a hidden empty "H" drive already.

.
 
Did you test the machine with GPResult? It will tell you why a GPO failed to apply.
 
Biznatch said:
Did you test the machine with GPResult? It will tell you why a GPO failed to apply.
Click to expand...

I didn't. I think the GPO applied as it should have, it just claimed the user didn't have rights to the drive, when they really did.

It kept working all through last night with the mapping leaving out the drive letter. I'll test it more today and see how it reacts...but I think it's solved. I still don't understand why it broke in the first place.
 
See post #12 above - I left out the drive letter when mapping. Instead of mapping \\server\drive\folder I just mapped \\server\folder and it worked.
 
You must log in or register to reply here.
Back
Top