We help IT Professionals succeed at work.

Windows network share: asks credentials when trying to access (on some workstations)

2,980 Views
Last Modified: 2017-04-14
Hi,

I have a situation where some of our users are required to re-enter their username and password when accessing a shared drive. Once they re-enter it, everything works.

If I map the drive using 'net use s: \\servername\sharedfolder' they have that problem (but not everyone)
If i map the drive using 'net use s:\\serveripaddress\sharedfolder' then the problem doesn't seem to occur (yet).

If I do a nslookup servername I don't have any problems, ping servername works as well (on the affected laptops), so it doesn't seem to be a dns problem (but I'm no expert on dns matters...)

This happens on Windows 7 and Windows 10 laptops.

On Windows 10 (which I am testing now) I get the following error message:
"An error occured while reconnecting S: to \\servername\foldername  Microsoft Windows Network: A device attached to the system is not functioning. This connection has not been restored."
Ping servername: no problem
nslookup servername: no problem
reconnecting network drive using 'net use'  with the ip adres:  no problem
reconnecting network drive using 'net use' with the server name on the cmd prompt: "The password is invalid for \\servername\folder. Enter the username for...".

If I enter the command "set user" on the command prompt, the USERDOMAIN is correct, the USERNAME is correct, everything look alright.

Does anyone have any idea what could cause this?

best regards,
Andy
Comment
Watch Question

Fethi ABASSIWindows system administrator
CERTIFIED EXPERT

Commented:
Check if the services of Network Discovery runnings correctly:
DNS Client
Function Discovery Resource Publication
SSDP Discovery
UPnP Device Host

https://pattersonsupport.custhelp.com/app/answers/detail/a_id/19189/~/enabling-network-discovery-in-windows

Author

Commented:
Hi Fethi,

thanks for you fast response.

I have checked the four services you suggested: UPnP Device Host was not running on the client. I've started it and waited for a bit before retrying access to the shared folder, but the problem remains the same.
SSDP Discovery and UPnP Device Host were not running on the server. I've started them as well, rebooted the client, but the problem is still the same
Fethi ABASSIWindows system administrator
CERTIFIED EXPERT

Commented:
Are you trying to change the IP adress on Laptops have problem  ?
Or reset the ipconfiguration with command:  Ipconfig /release and Ipconfig /renew
Check if you have any app like firewall or anti-virus can block certain network flow

Author

Commented:
Hi,

ipconfig /release & /renew -> no change
ipconfig /flushdns -> no change
firewall completely disabled -> no change
Fethi ABASSIWindows system administrator
CERTIFIED EXPERT

Commented:
are you try with another ip adress Static not DHCP
Can you open with command line the Key manager: rundll32.exe keymgr.dll, KRShowKeyMgr and reset the saved configuration
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
Are you using Persistence?  Probably, that is default.

On a problem computer, delete all the shares. Open cmd.exe  and then:

NET USE T; /Delete for all drives T:

Now restart the computer and connect shares as follows:

NET USE W: /Delete
NET USE W: \\server\folder.

Now the connections will be reliable during a working session.
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Maybe there is a delay in when the computers are connecting to the network? Are you using wired or wireless connections?

Author

Commented:
@fethi abassi: thanks for the suggestion, I didn't know that command. Unfortunately it didn't solve the problem (I removed what was stored and rebooted)

@John Hurst: the network drives were persisted. I did remove the shares, rebooted, and reconnected the shares without the /persistence, but that didn't work.

@masnrock: wired connection.

@all:

on the same computer I can make a connection
"net use K: \\10.14.14.10\datashare" which will work without any problems
but I can't make a connection to
"net use L: \\server1\datashare"

which at first made me assume it was a DNS problem, but:
"nslookup server1" gives me the 10.14.14.10 ip address
and "ping server1" will also work.

logging in with the same user on another computer and trying the "net use L: \\server1\datashare" command does not give me the same problem, so it probably is not user related. And I would be surprised if the problem is with the server (seeing as it works with another laptop).

Author

Commented:
I have just tried the following:

In Windows Explorer (on Windows 10), I typed "\\server1" on the address bar and I got another error:

a popup window "Enter Network Credentials" where I can enter my username and my password, but at the bottom there is an error message in red "The system cannot contact a domain controller to service the authentication request. Please try again later."

However: when I enter my username and password, from then on everything works... even my "net use \\server1\datashare" command on the command line.

I can ping the domain controller by name and by ip address without any problems.
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Try mapping "\\10.14.14.10\datashare" instead of "\\server1\datashare" for that one user on that one machine and see if you get the same problem.
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
If you have Network Discovery and File and Print Sharing both ON (Advanced Network Properties) and your NIC is connected to Domain;

And, then if turning Persistence OFF (or deleting the share prior to mapping);

And, then if this is affecting a number of computers:

Then you do need to consider a Server cause. How many (what number of) machines do not work?
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Have you had any network issues recently? Like slowness? It might be that you need to check for a cause of congestion. The only other common point is the server. Speaking of which, how many DCs does the network have?

Author

Commented:
@masnrock: mapping a network drive using ip address instead of the servername is no problem.
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
Also try uninstalling your Anti Virus temporarily. Rely on Windows Defender in the interim.

When you reinstall your A/V, make sure Defender is fully off.
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
mapping a network drive using ip address instead of the servername is no problem.

Could still be A/V  and also restart your DNS services on the Server.

Author

Commented:
We have 1 domain controller, and 22 workstations.
The problem occurs on 3 workstations, the others work fine.
The problem also occurs on those 3 workstations if not all 22 workstations are in use (today we're only with 8 people - rest of the employees are on vacation - and the same problem occurs on the same workstations as when all 22 are busy working). So I don't think it can be related to network performance or congestion.

Just in case this matters: the fileshare is not on the domain controller.

I do find it very weird that everything works flawless when using ip address and the problem only occurs when using the servername. Especially since nslookup and ping don't report any problems.

Does anybody know a (preferably free, or open source) tool which I can run on the client to check if everything is OK with Active directory, domain, dns, etc...  ?

I will try taking one of the troubled laptops out of the domain and rejoin to see if this changes anything.
CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
Take one of the problem Windows 10 machines and do a Windows 10 Repair Install. Nothing need be lost

Use the Microsoft Media Creation Link to repair Windows 10.
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
On the DC itself, I'd run DCDiag.

Author

Commented:
thanks masnrock: there were 2 dns servers sent to  workstations via dhcp.

How I was able to nslookup and ping and not use Windows Explorer to access the same server I don't know (apparently command prompt and gui used different dns servers), but I removed one dns server from my client and now it seems to work.

I'll do some further testing, but I'll close this question now.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.