I have had the pleasure of recieving a free copy of Windows Vista Business thanks to my university’s MSDN AA program. Last weekend I thought I would take the plunge and install the thing, alongside XP so I could still dual boot and use XP when needed.
Most things seem to be running quite smoothly in Vista, albeit slightly differently to XP. I have a few shared folders in XP which serve as place for family members to share and swap files over our network. With Windows XP users have never had any trouble connecting to my machine. This has all changed with Windows Vista however. When I first created the same shares in Windows Vista the other XP machines were unable to connect to the Vista shares. Each time it was asking for a user name and password. This was quite frustrating as when you install Vista it never asks you to setup any user accounts with passwords.
The final solution to the problem is to create a new user on the Vista machine. The user does not need to have administrative privileges but must have a password. Once this is done your XP machines should be able to connect to the Vista shares using the user name and password that you just created. This could become frustrating but thankfully you are able to save the user name and password in XP so each time you connect to the share in Vista from then on you no longer need to put in these details.
I hope you find this information useful and that it saves you a few headaches. I know I spent a few hours trying to find away around this problem. I take it the requirements for a password is part of Microsoft’s attempt to up security in Windows Vista.
2 thoughts to “Mixed Windows XP and Windows Vista Network”
stumbled onto this blog, i had the same problem when i hit vista ultimate 32bit, went to network and sharing centre and set
network discovery – on
file sharing – on
public folder sharing – on
printer sharing – off
password protected sharing – off
media sharing – off
then when you share a folder, make “everyone” have owner or read only access and all my xp machines can see it 🙂
No need to create extraneous users, just set the ACL’s correctly (on the share(s) and the filesystem). Or just use the built in public share which is setup correctly already.