Win 8 Can't Connect to Terminal Server

Have a terminal server, been in production 3 years
Running W2K8 R2 SP1
Have Win 7 Pro users, can connect via RDP and via Browser using gateway.

Have new Win 8 user, cannot connect, says server is not there or is unavailable.

Have had the user try both by IP and by url - NO JOY
Have had the user try to use a browser navigate to the gateway, he gets there, but after that, same message.

I thought there was a hotfix for this, but now I am not so sure.

Any thoughts are welcome.
Who is Participating?
ZabagaRConnect With a Mentor Commented:
No, there's no RDP update for the server, W2K8 R2 SP1. I was asking if you could update the client to Windows 8.1 - or at least make sure all recent Win8 updates have been ran.
ZabagaRConnect With a Mentor Commented:
Can you go to a command prompt on the win8 pc and telnet to port 3389 on the term server?
You'd type:  telnet <server-ip-here> 3389

If connectivity is OK, the screen should clear and you'll have a blinking cursor.
You need to add telnet client in win8 beause it's not there by default.
Do this to add:

What are your telnet results?

How about making sure you have Windows 8.1 (most recent version)
tech911Author Commented:
User that is having this issue is on a mountain skiing... apparently this wasn't as important as he made it sound.

I will try the telnet test.

Honestly, I think the connection request is getting to the server, but then because its the newer version of RDP, when the server responds using the older (not 8.0) version of RDP it gives the "No Connection" error.

Can I update the RDP connection at the server.  Do I want to?  Will it blow all my Win7 users out?

Finally we also use a two factor authentication system, but it does not figure into the equation until after you are presented with the TServer login screen.  I don't want to break that either.

As a precaution, since this is a VM, I shut it down and made a complete image of it in case we totally blow it up.

Will advise when he gets back to me.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

rindiConnect With a Mentor Commented:
Check the firewall on the w8 box. It could be blocking RDP.
tech911Author Commented:
ZabagaR - I understood what you were asking, very clear.

When I was researching this issue, I copied a link to my desktop that said it was a hotfix for Windows 8 not being able to access a terminal server,  and would fix this issue, but now I can't locate it, so I'm wondering if I really did see it or if I was working on something else?

Anyhow, I will advise, once he gets back to me.

If you find my missing hotfix, advise,

Thanks for the help
Have you already tried disabling the firewall? Such issues are usually caused by firewalls...
I haven't seen a hotfix but the only other time I ran into this problem, it was fixed when the end user ran windows update to take their workstation from windows 8 to windows 8.1
I would also do the telnet test, first.
I can also add that there is no problem connecting 8/8.1 to 2008 R2 RDP - no patch or whatever needed.
tech911Author Commented:
OK - I will be working with the user to see if I can test this out.

tech911Author Commented:

User did not put in Domain\username, instead they were putting Domain/Username, which will not work.
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.

All Courses

From novice to tech pro — start learning today.