systemstech wrote: » Do you have a VPN connection? If not, you can open up port 3389 on your home router (not recommended though because of security). Once you do that, you can RDP into your home box. Again, I wouldn't recommend it.
Dojiscalper wrote: » I've had that same type of problem and found that some unmentioned firewall rules are complicating things. Use the command something like get-netfirewallrule -display name "remote" to take a look at them and set those remote ones to enable.
nascar_paul wrote: » Have you tried TeamViewer? There's a free version that I've used for years that will accomplish what you're looking to do nicely w/o the additional setup or expense of remote connection appliances.
techfiend wrote: » You could try adding or changing RDP port on your home lab. It's much safer and might get around the blockage.
ed_003 wrote: » I always change the default RDP port and even then i still get get on.. from within i can remote to it tho
OctalDump wrote: » You'll ideally need bare metal box to install and configure Hyper-V which is a bigger part of the certification. It can be done in a VM with some trickery (I think VMWare workstation has a HyperV mode), but it is nicer to do on bare metal.
Mike7 wrote: » Check the firewall settings. By default, RDP is enabled for "private" but not "public" networks. Enable for "public".
OctalDump wrote: » If they are blocking RDP, it's probably just port 3389 that they are blocking. You can use another high number port, say 63389, and that would like be fine. If you router supports port remapping, that'd be the easiest way. Otherwise you can change the port of RDP on your server. But just use Azure or some online lab if that is the problem you are trying to solve. Learning Azure is only going to help you in the long run.