• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 940
  • Last Modified:

Workstations (not on domain and never will be) cannot access a shared folder on Windows Server 2008 R2

Recently, our Server 2008 R2 server stopped allowing none domain computer or VPN users to access the shared folders.  It used to prompted us for a user name and password and we would use our domain logins to access the shares on the server.  We receive the error code as shown in the picture I have attached.  "The trust relationship between this and the primary domain failed."  How can I get the server to prompt the user name and password again so non domain PC's can access it again.  All of our other servers are working perfect and they are Server 2008 R2 and Server 2003.  Thank you!

Jeff Error code for accessing the server
0
jokert
Asked:
jokert
  • 4
  • 4
  • 2
  • +1
2 Solutions
 
msincorpCommented:
Two things you might try.

1) Check and see what the preferred DNS server settings are in the TCP/IP settings on the workstation, and make sure it is set to the ip address of the 2008 server.

2) Check your firewall settings on the server.  Temporarily shut down the firewall and try to connect.  If you can then we can look at the rules and see which one is causing the problem.  If not, resart the firewall and we can try somthing else.

Good luck!

Chris
0
 
Darius GhassemCommented:
Have you tried mapping the drive  through the Network Mapping feature you can enter your username and password at this location
0
 
jokertAuthor Commented:
Thank you for the quick replies,  here is what I came up with.

1. Double checked all the DNS settings on the server and it has the correct primary DNS information just like the other servers.  Still no luck though.

2. Turned off the firewall and still couldn't make it.  Even flushed the DNS just to make sure and it still didn't work.

3. I was able to map a drive by selecting "Connect using different credentials.  Short term fix but i am still puzzled why this server only is having this problem.  I am really stumped on this.  Not one of the other servers is doing this.  :(  
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
jokertAuthor Commented:
One more update.  Logging on to the VPN doesn't allow the map network drive.  The user name and password just keep popping up.  Tried with both the DNS name and directly to the IP address but didn't work.
0
 
msincorpCommented:
When you checked the preferred DNS server, did you confirm the workstations as well?  Are they pointing to the proper mail server?  It also might be worth a shot to enter the ip address into the local host file.

You mentioned that if you were able to login with different credentials and map a drive.  That suggests a "rights" issue.  Is there a way for you to create a group, assign domain admin rights to the group, add the user that cannot map a drive directly to that group, and see if you can then map a drive.  If you can we need to look at rights as well as connectivity.

Have a good one!

Chris  
0
 
Darius GhassemCommented:
Are you using the domain\username
0
 
Rob WilliamsCommented:
You mention the primary DNS server points to your server but do you have a secondary pointing to an alternate server outside of the domain, such as an ISP or a router? This can cause name resolution issues.
0
 
jokertAuthor Commented:
The workstation and the server have the proper Primary DNS and our Secondary DNS.  We did try to also just use the direct IP and it still will not pop up the User name and password.  Active Directory sees the server so I am not sure what is going on still.  I think we are getting closer.  :P
0
 
msincorpCommented:
This KB Article looks promising - http://support.microsoft.com/kb/162797.

Might be as easy as creating a computer account on the DC with the same name as the computer.  Seems like the computer needs to authenticate if if the user does not.

Hope it helps.
0
 
Rob WilliamsCommented:
That will not resolve the problem for VPN users even if it should work on the LAN.
0
 
jokertAuthor Commented:
I should of tried this a long time ago but figured there was more to it but I removed the Server from the domain and re-joined it back and now everything seems to be fixed.  Seems to be a random problem around the network but a simple yet annoying two reboot fix.  Thank you everyone for all the help!
0
 
msincorpCommented:
Well.. seems that the computer account that needed to be created was the server!!!

Glad you found your answer!

Chris
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 4
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now