Can't Map Network Drive
I have a user with several mapped network drives that work correctly. I am trying to map another drive and I can't get it to work no matter what I've tried. The weirdest part is she had this drive mapped for a long time and it worked fine. It just started prompting for her to logon every time and then doesn't let her. So I disconnected from the network share and tried to re-create it and it just doesn't work.
I can ping the server by name and by IP successfully. She has full permissions on the folder to which I'm trying to map. Every time I try, it pops up the logon screen, which she completes correctly, but it automatically goes right back to the logon screen as if her password was incorrect. I've tried with and without the domain name in the logon user name field. I have even reset her password in AD and had her log off and back on again, with the same results.
I'm completely stumped on this one.
I can ping the server by name and by IP successfully. She has full permissions on the folder to which I'm trying to map. Every time I try, it pops up the logon screen, which she completes correctly, but it automatically goes right back to the logon screen as if her password was incorrect. I've tried with and without the domain name in the logon user name field. I have even reset her password in AD and had her log off and back on again, with the same results.
I'm completely stumped on this one.
Can she connect to other shares on that server?
Can she connect just to the server itself \\servername at run
Does the server show anything in the security log.
Can she connect just to the server itself \\servername at run
Does the server show anything in the security log.
Does her share security match her NTFS security?
There are times when the share security is set, but the NTFS security is set differently.
There are times when the share security is set, but the NTFS security is set differently.
ASKER
NxJNY - yes, I've tried both ways, domain name/ip address, with and without domain.
remmett70 - There are no other shares on that server. It's only one folder per user. It is our ERP server and she can connect via the ERP application itself with no problems.
JWong007 - I have no idea. I am a database admin and this just got thrown in my lap because I'm also the ERP administrator. If you can tell me how to check that, I can do it as I am a domain admin.
remmett70 - There are no other shares on that server. It's only one folder per user. It is our ERP server and she can connect via the ERP application itself with no problems.
JWong007 - I have no idea. I am a database admin and this just got thrown in my lap because I'm also the ERP administrator. If you can tell me how to check that, I can do it as I am a domain admin.
What happens when you just connect to the server under her account from Run > \\servername >enter
It should display the shares available from the server.
It should display the shares available from the server.
ASKER
It shows the main shares, but the folder to which I'm mapping is not under one of these shares. It's drilled down from the root of the D drive and here is the path I'm using: \\sdwinerp01\d$\ross\users
check the d$ share. If she doesn't have access there, she won't be able to get further.
I would recommend changing the share point. Using the administrative share of drive isn't a good practice. I would create a new folder and move all the folders into that instead.
I would recommend changing the share point. Using the administrative share of drive isn't a good practice. I would create a new folder and move all the folders into that instead.
ASKER
I can't move the user folders because they have to be where they are in order for the ERP program to see them. This works for all other users who need it and it used to work for her. I just don't know why it quit working and therefore, I don't know how to fix it. None of the users have access to the root of the D drive - only for their own user folder.
have to step through the connection. She can get to the server, now go next step and connect to the d$ share. Again at the run window > \\servername\d$
If she can access there, move to the next folder step by step through the entire path until you find where the connection is being blocked.
Even if the files need to stay, I would create a new share at the Root of D specific for these connections and not use the D$
If she can access there, move to the next folder step by step through the entire path until you find where the connection is being blocked.
Even if the files need to stay, I would create a new share at the Root of D specific for these connections and not use the D$
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That was exactly the boost I needed. The share is set up as mbaer$ and when I mapped to \\sdwinerp01\mbaer$ instead of drilling down the folder it worked perfectly. I learn something new every day - thank you!!!
eg. 192.168.111.1\users
also in my setup the login is usually
mydomain\myusername