I was perplexed by the fact that another laptop (it has XP) could see my non-public folder in my brand new Windows 7 machine, even though the XP machine had not joined anything (group or otherwise). This was all the more troubling because I network via WiFi in an apartment building setting. I thought the visibility was because of HomeGroup, so I followed How to Disable “HomeGroup” Feature in Windows 7? - Tweaking with Vishal
to disable HomeGroup. After all, here isn`t usually another machine on my WiFi network, so no need for HomeGroup.
However, the XP laptop could still see my folder. According to Why can another (XP) machine see my MyDocuments folder?
, this was because the XP machine was logged into an account with the same username and password as the login on my Windows 7 machine. Lord, I thought, so much about Windows networking presumed in the default configuration which is not suited for a standalone machine.
To try and fix this problem of too much transparent access, I embarked in a harrowing journey of education about Microsoft networking and sharing protocols. Then I saw a ray of sunlight peeking through the clouds: Homegroup Overview (Download details: HomeGroup Overview
). It launched me in the right direction, reading up about "Network Locations" (Home, Office, Public, Domain). It turns out that I had chosen Home network somewhere along the line when I first fired up the laptop. In my at-home environment, Public network would be far more appropriate. However, I realized that I had permanently disabled HomeGroup capabilities by my "fix".
I would like to use the Home/Office/Public/Domain options to control accessibility rather than diddling with the low-level controls such as HomeGroup-related services. That way, I can revert back to a fully functional Home network profile if needed. I know that I have to rejoin or recreate the HomeGroup at some point, but first I'd like to re-enable the HomeGroup Listener/Provider services. What is their default for Home network profile?