Accessing a Windows domain file share while logged in as a local user

14,712

Solution 1

I've had similar issues, here's what I usually do:

  1. open a command prompt from the workstation you are using to connect to the server.

  2. run the net use command to see if a connection for that share already exists, if it does, delete it.

  3. manually run the net use command to connect to the server, i.e net use \\server\share /user:domainname\username

  4. This should prompt for the appropriate credentials which you can enter at that time

In cases I've had this seems to do the trick, it never hurts to try.

Solution 2

Two things come to mind:

1 - Make sure when it prompts that you are using DOMAIN\username and not simply username.

2 - Make sure there aren't any existing connections to that server with different credentials (although typically the error is different when this is the case). You can verify this at a command prompt by typing net use and looking at the connections. If there are existing connections with different credentials (either direct or through mapped drives), you'll need to remove them first.

Share:
14,712

Related videos on Youtube

jjlin
Author by

jjlin

Updated on September 18, 2022

Comments

  • jjlin
    jjlin almost 2 years

    At work, I have a Windows computer on a domain, but it's generally logged in with a shared local user account, since the administrators don't want to make shared domain accounts. The problem is I seem to be unable to access file shares (that require domain user credentials). If I navigate to \\SERVER\SHARE, I'm prompted for my username and password, which appear to be accepted, but then a dialog box pops up with the message

    \\SERVER\SHARE is not accessible. You might not have permission to use this
    network resource. Contact the administrator of this server to find out if
    you have access permissions.
    
    Logon failure: unknown user name or bad password.
    

    A few notes:

    • The file share works fine if I'm logged into the computer under my domain account instead of the local user account.
    • This computer was previously taken off the domain, and during that time, the file share worked fine as well (it would request my domain account credentials as usual, but then actually show the files instead of the error message).
    • If I "run as different user" a Cygwin terminal under my domain credentials, I can cd //server/share and access files that way.

    Any ideas on how I can access this file share without taking the computer off the domain?

    • mfinni
      mfinni about 11 years
      Your admins should really be working with you for this.
    • voretaq7
      voretaq7 about 11 years
      Based on your question you do not appear to be the domain or network administrator. Server Fault is a site for system and network administrators - end-user troubleshooting is the job of your in-house IT department. If in fact you are the administrator you can help us help you by including information from your event logs, and more details on what you've tried to resolve this issue (See meta.serverfault.com/questions/3608 for some tips)
  • jjlin
    jjlin about 11 years
    Yep, it's not either of those problems, but thanks anyway.
  • jjlin
    jjlin about 11 years
    Thanks for the response. It prompts for my password, and then gives "System error 1232 has occurred."
  • Miguel
    Miguel about 11 years
    according to Microsoft that means ERROR_HOST_UNREACHABLE1232 (0x4D0) The network location cannot be reached. Does that help you any?
  • kralyk
    kralyk about 11 years
    If it's a normal Windows/CIFS/SMB share and there aren't any existing connections in "net use" then browsing to the share and putting DOMAIN\username and your password would be the same as all 3 of your "notes"...unless I'm missing some details somewhere.
  • jjlin
    jjlin about 11 years
    Yeah, I don't see why it should be different, which is why this situation is puzzling.
  • Greg Bray
    Greg Bray about 11 years
    Try the FQDN or IP address instead of just the servername. May be a DNS issue.
  • Nate
    Nate over 9 years
    This answer worked for me. Thanks! +1