Unable to RDP whilst connected to VPN

Hi All,

I'm a little perplexed at the moment, i have setup a server running Hyper V with 2 VM's sitting on it. One SBS 2011 and one Server 2008 R2 with Terminal Services.

I have setup the VPN on the SBS 2011 and have successfully connected to the internal environment, but for some reason i cannot RDP to the Server 2008 R2 server.

I can:

- Ping both DNS name & IP Address
- Browse Shares
- RDP to the SBS 2011 server
- RDP to the SBS 2011 server then RDP to the Term Server.

I can't:

- Telnet to 3389 on the Term Server or RDP to the Term Server.

There is no AV or Firewall on the server...

Where can i look next?
trentmdawsonAsked:
Who is Participating?
 
trentmdawsonConnect With a Mentor Author Commented:
Problem solved....

SEP was blocking RRAS connections to other machines via RDP!
0
 
Andrew DavisManagerCommented:
sounds like the Termserver is connected to an incorrect virtual switch.


see http://technet.microsoft.com/en-us/library/hh831823.aspx

We would need to know the details of the switch. And the hyper-v host. 2008 , or 2012. Any VLan's etc..

Cheers
Andrew
0
 
Andrew DavisManagerCommented:
Just checked on my working system, and telnet to port 3389 does not respond, so that may be a red herring.

what if you try to connect to it with /admin switch?

Cheers
Andrew
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

 
trentmdawsonAuthor Commented:
Thanks for the response.

Your right it definitely could be my Hyper V setup. First time setting up a hyper v network.. To be brutally honest it could be completely wrong.

It's a real basic setup, currently i have 3 Physical NIC's plugged in.

1 for Hyper V server
1 for vSwitch to attach both SBS & TS servers.

It shouldn't respond, should just flash the cursor. It will only bring up a message if its not working :)
PNetwork.PNG
VNetwork.PNG
0
 
Andrew DavisManagerCommented:
Everything there seems fine.

What happens when you try to RDP? do you get anything? does it reject immediately or is it timing out?

My setup here is exactly the same (Except that i have 2012 Terminal server), the one big difference is that i am not using VPN. Is it possible to exclude the VPN as the issue by testing from another machine that is local to the LAN.

Cheers
Andrew
0
 
trentmdawsonAuthor Commented:
Yeah on the local network it works fine. Its only on the VPN where it is an issue..

Yeah it eventually times out and says cannot connect to remote server. Takes about 10 seconds to fail
0
 
Andrew DavisManagerCommented:
But on the VPN you can ping the same machine without an issue?

is that correct?

Cheers
0
 
Andrew DavisManagerCommented:
have a look at http://social.technet.microsoft.com/Forums/windows/en-US/0fc219bf-d147-4579-bea4-014fe5e65967/rdp-tunneling-via-vpn-not-working
certainly one of the most confusing write-ups i have seen, but it may provide some insight.

Personally i never use the VPN built into exchange, and instead use VPN from the router. But i understand your router may not have the ability to host the VPN. You could get Tricky and create another VM and install untangle https://www.untangle.com/ as a gateway device (it can go onto a Hyper-V, i am playing with it at the moment), then you could allow it to control the VPN.


Cheers
Andrew
0
 
trentmdawsonAuthor Commented:
Yep sure can ping the machine no problem. Both DNS names and IP.. Yeah me either but the client requested this.. May have to see if I can setup VPN on router
0
 
trentmdawsonAuthor Commented:
Solved my own issue.
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.

All Courses

From novice to tech pro — start learning today.