The good part is that a clueless noob was able to get Remote Access to his WHS box working - from behind a corporate firewall, yet... - just by setting a few port forwards on his router, setting a couple of other things on said router, and letting WHS's automatic setup do it's thing.
The truly amazing thing is that I can Remote Desktop (or something that looks/feels exactly the same) to at least one of the other PCs on my home LAN and once I figure out what settings on that PC allow it, I sb able to do the same thing with all the others. This is some *serious* functionality for Yours Truly.
I will follow up with details on the router model/settings later in the day once time permits, I'm able to get to the modem for the details, and I manage to nudge my IQ above room temperature.
The bad part is that, coincident with getting Remote Access running, Cisco's Clean Access Agent (required by the place I work in order to Remote Desktop into my PC there) has started to hang - both when automagically started by the VPN connection process and when started manually.
The interesting thing is that this happens on all three of my non-server PCs (none of which were touched when I set up Remote Access).
I have not tried Clean Access Agent on the WHS box and do not intend to.
Seems like there are two possibilities:
- Correlation is not causation. Something wierd started happening with Clean Access Agent around the same time as the Remote Access config, and there is no other connection.
.
- The modem settings (port forwarding, UPNP, and so-forth) on my router have created an environment that trips Clean Access Agent.
I tried backing out the modem changes, but the problem persisted. But that doesn't mean much to me bc I would assume there's a good chance that I only think I backed out all the changes and there's still something there that was not there beforehand.
Anybody been here?
