RDP not working outside of network

I am having issues with RDP not working outside the network.
1. I am able to gain access to the network via VPN however when I try to RDP to the DC1, I am getting an error that the RDP failed.  This same connection was working yesterday not it does not work.  
2. I am getting no response when trying to log into another system through a browser.  

Please help if you can.
Van JohnsonChief Technology OfficerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Schnell SolutionsSystems Infrastructure EngineerCommented:
In order to connect to remote desktop throw the VPN you need to accomplish the following requirements:

1. The VPN is routable until your RDP server. (There is a routable communication with the Network/IP from your VPN client and the RDP server). i.e. Having the correct routes or gateways within your RDP server.

2. The communication allows that your VPN client connects to the RDP server by TCP protocol port 3389.
Michael MachieIT SupervisorCommented:
Since your web browsing is also failing I would start by checking for a DNS issue.

1) Attempt the RDP via IP address rather than server name. If it succeeds it is a possible DNS issue, especially if #2 and #3 below is also the case.

2) Launch a command prompt. Ping the internal Server name - you should get a response. If it times out, try pinging the actual IP of the server. If this responds appropriately it is a possible DNS issue.

3) Open the web browser. Attempt to "log into the other system" via IP address of that system. Success by IP and not by name is a possible DNS issue.

4) Go to google.com, or any other very stable site, and if all is good it should load. If it does not load you will need to try to ping the same website via a command prompt. If it fails to ping then it is a possible DNS issue. If you get a reply with  the IP address then it could be a routing issue because DNS would have resolved the name and returned an IP.


Start there, let us know.
Van JohnsonChief Technology OfficerAuthor Commented:
Since your web browsing is also failing I would start by checking for a DNS issue.
I am sorry if I misled you on the second part of the question.  What I meant was, I can normally connect to some appliances through a browser(using an IP address, firewall etc.,) but now I cannot.  


1) Attempt the RDP via IP address rather than server name. If it succeeds it is a possible DNS issue, especially if #2 and #3 below is also the case.
That is all I am using at this point is the IP address not the name of the computer.

2) Launch a command prompt. Ping the internal Server name - you should get a response. If it times out, try pinging the actual IP of the server. If this responds appropriately it is a possible DNS issue.

I am getting no ping from either the name of the computer or the IP Address.

3) Open the web browser. Attempt to "log into the other system" via IP address of that system. Success by IP and not by name is a possible DNS issue.

Again no response from IP Address or computer name

4) Go to google.com, or any other very stable site, and if all is good it should load. If it does not load you will need to try to ping the same website via a command prompt. If it fails to ping then it is a possible DNS issue. If you get a reply with  the IP address then it could be a routing issue because DNS would have resolved the name and returned an IP.

When connected by VPN I am able to ping http://www.google.com.
Mick FinleyNetwork EngineerCommented:
When connecting to a VPN, one of the first things to happen is static routes are set on your workstation. With Windows, UAC will not allow this to happen at times.  Try this, when you connect to your VPN, goto command line and use 'route print' to verify there is a route to the network your trying to connect to.
Michael MachieIT SupervisorCommented:
Sorry for the delayed response. EE just now notified me of your comment.

If pinging the IP and name fails then you have a routing issue or traffic is blocked. Are you using vLans? Perhaps a config change is now blocking vlan-to-vlan communication.
Are you using split-tunneling on your vpn? If so, that could explain why you can ping google while connected but cannot access any internal IPs.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VPN

From novice to tech pro — start learning today.