We help IT Professionals succeed at work.

One user only being ask for username for mapped drive in dos window

jasonbournecia
on
Stumped!
Most users have a start up script which maps 3 network drives. Two are to normal folders and one is to a Sharepoint folder.
All three have the same layout in sysvol:
net use g: \\192.168.1.110\depts
net use m: \\192.168.1.110\apps
net use y: \\192.168.1.110\public
Y drive being the Sharepoint.
Okay, when she logs onto her machine, Win7, a dos window is left open which asks for her user name for the Y drive.
In My computer she can get to g and m, but Y is not shown.
I tried getting her to log onto another Win 7 PC and same problem.
But, when she tried it on a XP machine, it works fine!!!!!!!!!!
Any ideas? She is a department admininstrator and uses the Y drive constantly.
BTW, I changed the scripts to IP addresses because sometimes, other users lost connectivity; possibly DNS but that's another story.
Cheers
John
Comment
Watch Question

Distinguished Expert 2018

Commented:
Actually your DNS issues may not be another story at all. DNS is a significant player in finding AD services, and AD is respnsible for authentication. For Single Sign On (SSO) to work properly, your network must be running smoothly. Since apparently typing in a username and password in the dos prompt still works, I'm guessing that this is simply a matter of SSO failing, which would point to an infrastructure/lookup problem. Exactly what I'd expect to see if DNS is not working properly, or if SBS is not the DHCP server (as an example of what can cause DNS to not work properly.)
Alan HardistyCo-Owner
Top Expert 2011

Commented:
From her machine, please do the following from a command prompt:
net use y: /delete
net use y: \\192.168.1.110\public /user:domain\username password /persistent:yes
Change the following items in the above command to reflect your environment:
domain
username
password
Once done, please log the user out and then back in again and see the the mappings take happily.

Author

Commented:
Before I try any of the suggestions, don't forget that she logged onto another Win 7 machine and had the same problem, but the normal user of that machine has no problem.

Author

Commented:
Re your comment alanhardisty, the only problem there is when her password changes, you'd have to go through this each time.
Alan HardistyCo-Owner
Top Expert 2011

Commented:
This is usually down to the password being remembered by the machine.
Forcing the current password will make the cached password change, so they will be fine until the next password change!
Try it and see - it should be fine.  Then change her password and see if the problem resurfaces.

Author

Commented:
No, didn't work.
I made the changes in net use, drive appeared in my computer, but when you went to open a document, it asked for credentials, so I logged off and on, but still got dos box asking for username and a cross against y drive
Alan HardistyCo-Owner
Top Expert 2011

Commented:
Okay - that's not helpful!
Can you open up Windows Explorer (Windows Button and E)
From there, click on Map Network Drive, Pick your drive letter, then choose the Folder to map to and then tick the Conenct using different credentials check box.
Click on finish and fill in the users credentials and click OK.
Then logout and log back in again.  Is the drive mapped properly?
Distinguished Expert 2018

Commented:
Just as a reminder, I'm sticking with the assertion that this is related to your DNS issue. I suspect that if you concentrate on that, this other issue will resolve itself.
Alan HardistyCo-Owner
Top Expert 2011

Commented:
DNS should not be an issue if you are specifying IP addresses in a mapped drive.
Distinguished Expert 2018
Commented:
DNS hosts SRV records that windows uses in the background to implement and support single sign on. A DNS issue can, in fact, cause credential issues in OSes that support kerberos. Remember that it isn't complaining that the share can't be found, but that it is requesting a password. So the IP address *is* avoiding the DNS issue for finding the share. But then authentication is failing, which can certainly be caused by a DNS issue in various AD related functions relating to authentication.

Author

Commented:
Okay cqaliher, wayyyyyy out of my comfort zone now.
In layman's terms, where would I look? This is only affecting one user, but in the past, it has affected more. Might be co-incidence as I only put IP addresses last week, but everyone appears fine.
One thing I was unhappy about, but this was last year, is when we had our data server swapped, which also housed SQL and Sharepoint, was that the support company used a script. So as the data was being copied to the new server, let's call it Server2, Server2 was on at the same time as Server1; the old one.
So now for the last year, most people still reference the Server1 name, which through DNS point to Server2 name. I was assured this is fine, but in my limited knowledge, we are just adding an extra record for dns to go through.
We only have two servers, SBS2008 and the data server mentioned above.
But going back to the original problem, how do I resolve it?
Cheers
If DNS is the cause of the issue you would most likely be seeing more instances of errors/problems.  As you are only having a problem with one user then investigate that user.

So if I understand correctly this one user has the problem on a win7 pc.  If she logs onto another win7 machine she has the same problem.  however the user of the 2nd win7 machine does not have the same problem?

Again if DNS were an issue, it would affect both users and not just the one.  Have you checked that users account vs the other win7 user who doesn't have this problem?

DNS could still be a part of the problem but given the info it is highly unlikely that DNS is your issue.

Author

Commented:
Yes kruger monkey, problem on different Win 7 PCs for the same user, however, when she logged onto an XP machine, no problem. She is pointing to the same log on script, I'm not sure where to look next.
I'm reluctant to start creating new reg entries. I'm not averse to it, but she has the problem on another machine makes me pause before modifying the registry

Commented:
If you want to verify that your DNS is setup correctly see http://support.microsoft.com/kb/321045
I would first unjoin the computer from the domain and then rejoin it to see if that resolves the issue (Possible trust relationship issue)

If that does not work look at the permissions on the share.....Probably some setting in sharepoint!!

Author

Commented:
I've just remembered something, don't kill me but it might help.
This user had a problem with some mapped drives before the above problem, so what I did a week or so ago, was create another script just for her.
net use g: \\192.168.1.110\depts
net use m: \\192.168.1.110\apps
net use y: \\192.168.1.110\public
net use s: \\192.168.1.110\select
So, as you can see, more or less the same as the original except for last line.
She logged on, got error messages about connectivity, could not see 's' drive.
So, I logged her off, deleted the script, put her back on the original script and since then, she has had the above problem.
But don't forget, this happens on more than one machine and I flushed her DNS
In the meantime, 5q, I'll have a look at the link you've sent.
Alan HardistyCo-Owner
Top Expert 2011

Commented:
If you stop her scripts from running and manually map the drives through DOS on her machine using the proper name of the server, what happens.

Can you run from a command prompt:

Net view \\server

Do you see the Select share?
Alan HardistyCo-Owner
Top Expert 2011

Commented:
Also, check the permissions on the share for her to make sure she has privileges.

Author

Commented:
Hi alanhardisty.
I'm sat on her machine.
I logged on as administrator
I logged onto the server and removed script from her profile tab
Logged on as her and still had mapped drives with the error.
I then net use deleted drives on her machine
net use created drives and it worked beautifully!!!!!
So, with the exception of net use plus persistent specifically for her, what's the best next step?
Co-Owner
Top Expert 2011
Commented:
Okay - that sounds like progress.
Can you add the following to the beginning of the script for her:
net use * /delete /y
Then log make sure she runs the script on logon and see if it errors.

Author

Commented:
Thanks alanhardisty. Problem cured, but if this doesn't seem rude, it's a fix but doesn't find the problem.
I hope you don't mind, but I gave 50 points to cqaliher because, even though lack of knowledge, someting about DNS niggles.
BTW I forgot to change it to server name initially in the script and left IP address in and it asked for password again.
Changed it to server name and it worked!
I also put 3 lines of net use delete in, becasue net use * caused her mapped home drive (Z) to disappear.
All good now, can't work out why IP address did not give her access. She has no different permissions on that server.
Thanks again and your help has been truly appreciated.
John
Alan HardistyCo-Owner
Top Expert 2011

Commented:
A fix is a fix!  It may have been DNS issues, but mapping to an IP address should work every time.  Perhaps it is a new 'feature' in Windows 7 I have yet to discover!
They are your points - you distribute them how you like : )  I am just glad the problem is solved, if not fully understood.  In time someone may add to the question with a reason and we can all go Aha!
Best wishes
Alan
Distinguished Expert 2018

Commented:
I actually have been paying attention to this thread, but since y'all were chasing another avenue, I felt I didn't have much to contribute. (thanks for the points by the way)
But alanhardisty, if you are curious about why this happens, it isn't a new feature to Win7. This is actually caused by the integration of IE into Windows core.
IE->Internet Options->Security Tab->"Local Intranet" Zone->Sites button
You will see a variety of checkboxes that are designed to help IE figure out what is considered local to the intranet (including UNCs) and what isn't. While an IP address will *usually* get detected as local, sometimes, depending on the IPv4 configuration, firewall settings blocking or allowing netbios, the computer browser service...and on and on....that detection can fail. If IE decides a UNC path, even by IP, is not on the local intranet, you get an authentication prompt.
Which brings me back to my original DNS comment. When DNS is working properly and AD is actually responding, local intranet detection is far more reliable and you don't hit this edge case.
Anyways, that is just the FYI behind what causes the behavior y'all are seeing.  Glad you have a working solution and you can tuck that bit away for a rainy day in case you ever see something similar in the future.  :)

Author

Commented:
What bothers me, is how to progress with knowledge. We have an outside support company who have configured our new SBS2008 server and our SonicWall TZ190. I'll be honest, I haven't the foggiest idea how to configure the SonicWall, it is the brand they recommend and I had to trust their judgement. But I'm still unhappy with a script running which directs all name references of the old server, binned a years ago, to the new data server.
Not to tread on anyone's toes, but if either of you were local to East Sussex, I'd love to pay for an hour of your time to look at our DNS and say aha.....
I have a 'working' network, so not keen on just trying settings, but I just feel that the system is made to work, not made to work most efficiently.
I look after approx 22 local users and 9 remote, two servers and a phone system. I was taken on as much for my ability to get on with everyone as well as 6 years hardware and end user support. But, for myself, I want to take it further. People talk about different apps for checking network traffic and fault finding, but I find it hard getting of the support plateau.
Thanks again for your support.

Author

Commented:
Didn't realise, sorry to cause offence Alan.
I'll get off now :)
John
Alan HardistyCo-Owner
Top Expert 2011

Commented:
No offence caused - just a friendly reminder of the rules (which I fell foul of before someone pointed them out to me) : )