Link to home
Start Free TrialLog in
Avatar of BladeValant546
BladeValant546

asked on

Can't UNC or RDP into a Windows 2008 R2 Server

Got an odd one here that I've never encountered before...

We have a terminal services server (Win2008 R2) that our users log into when they are off-site.

This server has mapped drives to many other locations on the network, but there is one particular server that it cannot map a drive to, UNC to, or even RDP to.

Pretty much every other machine on the network can UNC and RDP to the server in question, and the TS server can UNC and RDP to just about every other server on the network as well. It's like there's a specific relationship between these two servers that prevents UNC/RDP access and I can't seem to figure out why. Any thoughts?

Thanks!
Avatar of sbrozinick
sbrozinick

Is the server that cannot be connected to via UNC or RDP a member of the domain?  If not, make it so it is.  

Can you RDP or UNC via the IP address instead of by name?  If not, you should also make sure that is listed in DNS with the correct IP address and that RDP is enabled.  For RDP trouble shooting check out the following:
http://technet.microsoft.com/en-us/library/ff404143(v=ws.10).aspx
Avatar of Mohammed Khawaja
Ensure you can ping the IP and the name.  Ensure the computer is part of the domain and see if you can logon locally on the server.  When you try to RDP do you get any errors or is it that the server name cannot be resolved.
Avatar of BladeValant546

ASKER

Yes, the computer I'm trying to RDP is a member of the domain (in fact, it's a domain controller)
Yes, I can ping it.
No, I can't RDP/UNC to it by IP either.
Yes, I can log on locally to the server and
Yes, Remote settings are enabled (not to mention that every other computer on the domain can RDP to this server, just not this TS server for some reason).

Any other ideas? I went through pretty much the same process you guys have listed out here, so you can probably see now why I was at a loss! :)

-Thanks
Haven't heard back from anyone on this - I'm at a loss, anyone else out there with an idea as to why this is happening?

I can give whatever information you guys might need to know to help solve this one.

-Thanks
One possibility is a time sync issue.  If the TS/RDS and the DC have a time difference of greater than 5 minutes, then the kerberos negotiations will fail, and it will be in accessible.

Coralon
I was hoping that that was the case, since I hadn't thought of it, but unfortunately no, we aren't that lucky today... :/

Time is identical on both servers.

-Thanks
SOLUTION
Avatar of Rodney Barnhardt
Rodney Barnhardt
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Sorry for the delayed response back.  Check to make sure that this 2008 server has the four services for Terminal Services started.

1) Terminal Services
2) Terminal Services Configuration
3) Terminal Services Gateway
4) Terminal Services UserMode Port Redirector (if you are doing redirection)

smckeown777's check for telnet did work as a test on the server that I got the 4 terminal services services.  I did not know that telnet was a tool to check for this thanks smckeown777!
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
There was no possible way that someone unfamiliar with the intimate details and recent history of our network could've been able to guess that the issue was a triangular route based on the way our connection between sites is configured. However, I am thankful that someone jogged my memory by saying the right words to get this one resolved.