Originally Posted by Mfusick
basically screw homegroups- they reset permissions too crazy style.
LOL, notice your picture indicates that you are logged into a homegroup that at the time consisted of Home Server (server), HTPC, and Administrator (server)
Thanks for the help though, but it wasn't just mapping network drives (I was pretty fluent in that)
If I were to map a network drive or attempt to explore a networked machine, I would be prompted to login (Windows would rememeber login credentials, but I despise this requirement on my local network)
The other problem was even though I was running a W7 box that was previously a homegroup member, after starting a VPN client app, the same W7 box couldn't find a homegroup on the local network
And the problem was . . . .
The networked machine that started the homegroup wasn't the one I was using a VPN client app on, and it was turned off
It might not be the height of security, but as long as the Homegroup "Originator" machine was running I could start the VPN client and tell Windows that the newly joined network was a "Home" network and all of my shares continue as they worked before.
Thanks to WonHung for further clarifying Tunneling, Split-tunneling, and Hairpinning