Sign in with
Sign up | Sign in
Your question
Solved

RDP and Internet Access

Tags:
  • Internet Access
  • Firewalls
  • Business Computing
  • Servers
Last response: in Business Computing
Share
August 18, 2014 12:20:24 PM

OK I have a weird one that has stumped all of us. I have a 2012 Hyper-V server I was RDPing to using a pin hole through the firewall. I lost connection to my RDP and I have team viewer install on my VM server 2008 which was showing offline. Now I did my troubleshooting and the building still has internet access, I was able to RDP into the server at their remote office, I could ping the Hyper-V server but still can't RDP. I was able to RDP into the 2003 VM server and from the 2003 server I can RDP into the Hyper-V. I pointed my pinhole on the firewall to the 2003 server and was able to RDP into that. Both my 2012 Hyper-V and 2008 VM show internet access in the taskbar but I can't ping any website by name or IP. I can ping the firewall no problem. My 2003 VM has internet access, as does everyone at the office. I also checked and the firewalls are off on both servers.

Both the 2003 and 2008 VM run on the 2012 Hyper-V

I would like to not have to reboot the servers.

Any Ideas??

More about : rdp internet access

August 21, 2014 10:55:14 AM

It was a little hard to determine which step was to test what.

If I read correctly, you have a single 2012 Hyper-V server (bare Hyper-V or Win2012 w/Hyper-V - can't tell) which is running a 2003 virtual machine guest and a 2008 VM guest. You can no longer access the main 2012 Hyper-V server through your firewall hole which was previously working.

You tested:

1) You can RDP to the 2003 VM guest through the firewall hole.
2) From the 2003 VM, you can RDP to the 2012 H/V host.
3) You can ping the 2012 H/V host but can't RDP to it.

My suggestions for you to check:

1) It is possible a recent security update from MS for Windows 2012 Server was applied that affected your remote access to only the 2012 H/V server. It may need a reboot.
2) See if someone has changed the NAT rules on your firewall. It is possible they meant to change one protocol but perhaps knocked out RDP to that server. Also check access rules. Perhaps someone was "cleaning" up rules & didn't think a network object was being used anymore. Also look for invalid static routes.
3) Check the internal firewall on the H/V server. It can have multiple profiles, so see if it's off for one profile but on for another.
4) Check for simple things like a static DNS name, but the IP address changed recently for the 2012 H/V host. So perhaps ping works because you are pinging *a* machine, but it might not be the H/V host.
5) Check the H/V host for virtual switch changes, and look at network adapter bondings. Make sure you still have an adapter available for the management of the H/V host.
m
0
l

Best solution

August 25, 2014 5:09:37 AM

I found the answer, I had the same issue happen again a few days ago, but this time random people in the company started losing internet, and some of the VOIP phones went down. It turns out it was the switch. Power cycled the thing and everything came back up.
Share
Related resources
August 25, 2014 11:40:48 AM

Sounds like that switch likely needs a firmware update as well!
m
0
l
August 25, 2014 11:51:28 AM

Good point I will have to add that to my todo list.
m
0
l
!