Windows Home Server - Remote Access is working!

re: Windows Home Server - Remote Access is working!

Darien Allen — Thu, 15 Mar 2007 22:47:51 GMT

I had this enabled with my beta of WHS, but I've turned it off because I have security concerns. Until I can find out a bit more about what if any security features are enabled I think I'll continue to use products like LogMeIn to remote access my home machines.

re: Windows Home Server - Remote Access is working!

Norman Diamond — Mon, 19 Feb 2007 06:40:32 GMT

Oh no. My wife has been jealous because our cat likes to sit in my lap and get in the way of me using my computer, but doesn't like to sit in her lap and get in the way of her using her computer. So now she's going to demand a puppy.

But if I did an RDP connection to her computer, she would notice it when she gets logged off, right? (I haven't actually done an RDP connection to an ordinary PC. I started to once, but quit because of the warning that the local user on the target PC would get logged off.)

re: Windows Home Server - Remote Access is working!

Mike Dimmick — Sun, 18 Feb 2007 03:27:59 GMT

WHS probably needs UPnP to be enabled on your router in order to perform the port mappings itself. This may be hard to find in the router configuration, of course!

re: Windows Home Server - Remote Access is working!

Nick Hodge — Sun, 18 Feb 2007 02:09:23 GMT

If your puppy wasn't impressed, it's time to get a new puppy.

On a more serious note, thanks for the inspiration!

re: Windows Home Server - Remote Access is working!

Ziv Caspi — Sun, 18 Feb 2007 01:43:15 GMT

You need the ISA Firewall Client to access Internet resources from the Microsoft Corpnet because the Internet is not routable from Corpnet (the routers deployed do not have the routing entries that point to the Internet; they only have the entries for internal routing). The ISA Firewall Client gets around this by sending all Internet-bound traffic to the ISA Server machines on the edge of Corpnet, where the Internet _is_ routable.