networking XP and Vista

B

Bill H.

Can't get it to work.

I've installed that little file on the XP computer to enable vista
discovery, shared the root of vista C with permissions set to all.
Configured vista to the same workgroup as the XP. Also turned off the
password requirements in vista.

I can see the XP in the vista full network map, but can't map a drive to the
XP. And in XP, I can see the vista, but can't access the drive "... not
accessible. The network path was not found."

Also, in win2k (on the same network), I can see the vista computer, but
trying to open it says "... not accessible. The network path was not found."
 
C

Chuck [MVP]

Can't get it to work.

I've installed that little file on the XP computer to enable vista
discovery, shared the root of vista C with permissions set to all.
Configured vista to the same workgroup as the XP. Also turned off the
password requirements in vista.

I can see the XP in the vista full network map, but can't map a drive to the
XP. And in XP, I can see the vista, but can't access the drive "... not
accessible. The network path was not found."

Also, in win2k (on the same network), I can see the vista computer, but
trying to open it says "... not accessible. The network path was not found."

The "... network path was not found." aka Error 53 is generally caused by an
inconsistent NetBT setting, or a personal firewall.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

A recent update to Internet Explorer is also causing some odd problems in
Windows Networking.
<http://nitecruzr.blogspot.com/2007/09/changes-in-internet-explorer-security.html>
http://nitecruzr.blogspot.com/2007/09/changes-in-internet-explorer-security.html

And with Windows Vista, there are numerous challenges not present in older
operating systems.
<http://nitecruzr.blogspot.com/2006/12/windows-xp-and-vista-on-lan-together.html>
http://nitecruzr.blogspot.com/2006/12/windows-xp-and-vista-on-lan-together.html

We could look at logs from "browstat status", "ipconfig /all", "net config
server", and "net config workstation", from each computer, and maybe diagnose
the problem. Read this article, and linked articles, and follow instructions
precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top