I have just finished building a new XP setup on my home network. I have ran into a slight problem when I try to map the drives on my Server (Linux Samba), I get an error message saying that I cannot map a the drive because it is already connected under the same name.
If I reboot the computer and go directly to the mapping option, without clicking on Network Neighbourhood or Browse Netork, I am able to map them through Windows Explorer and select reconnect at logon.
However, on rebooting the machine, I almost always get an error message that XP couldn't connect to the mapped drives. The only way to get around this is to type in the password again.. and all is well. If for some reason I dont do that right away, and go hunting around the computer , I eventually wind up with the same error message about not being about to map a drive that is already connected in use.
I know it is something to do with the configuration of this particular install, but I can't figure out what it is!!
Baffled
NeDDoG :disgust:
If I reboot the computer and go directly to the mapping option, without clicking on Network Neighbourhood or Browse Netork, I am able to map them through Windows Explorer and select reconnect at logon.
However, on rebooting the machine, I almost always get an error message that XP couldn't connect to the mapped drives. The only way to get around this is to type in the password again.. and all is well. If for some reason I dont do that right away, and go hunting around the computer , I eventually wind up with the same error message about not being about to map a drive that is already connected in use.
I know it is something to do with the configuration of this particular install, but I can't figure out what it is!!
Baffled
NeDDoG :disgust: