"Quite the opposite. In fact, most cross OS sharing issues are due to the user not setting up the network or local accounts properly. If the drives are shared, the PCs are in the same workgroup, you use the same user account and passwords on each system, and file sharing is enabled, you'll have no problem
connecting by UNC path, aka \\computername\sharename
. People usually skip one of those steps."
Sorry to say that this is not my experience. I have a mixed home network: Windows 7 main system, XP laptop, Vista laptop, all in the same workgroup. As the "administrator" I shared disks, used the same account name (mine) on all systems, with admin privileges with no password, had file sharing enabled, and set "passwords not required".
The Win 7 pc was able to access shared folders and drives on XP and Vista systems (though only after considerable additional work on the Vista system), the Vista system could access the XP's shared folders and drives, but neither Vista nor XP could access shared folders and drives on the Win 7 system. (XP couldn't access Vista either).
..until I read chev65's post earlier - which fixed the problem -- though the system went through a process of "setting security information" (unknown) on files in my Win 7 C: drive !?
But anyway, a million thanks go to chev65 !
My issue with all this is basic: we non-professional users should not have to struggle with complex, fragmented, convoluted, and ultimately, "undocumented" procedures to set up our simple home networks. Microsoft's help information does not actually
help lead us through all the unknown paths, nooks and crannies of different layers of security.
Whatever happened to "plug-n-play"?
I can't believe that the geniuses at Microsoft couldn't give us a simple-to-use software tool to simply configure a new PC into an existing network.
.. or did they, but I missed it?