No Network Path Provided

[Guest]

I have a Windows XP (home edition & Pro edtion, both have Service Pack 2, on
a workgroup - every computer is on the same subnet) machines on my network.
They are the only two computers that cannot browser to other computer shares
using the \\computername\c$ or My Network Places.

I can ping both computers using their IP address, but not their computer
name. I can ping from their computer to others, but only via IP, not
computer name.

I've ran "SFC /scannow" on both and that was fine.
I uninstalled and reinstalled File and Print sharing
I reinstalled TCP/IP
I did a "ipconfig /flushdns" on both computers
The hosts files only have one entry - the 127.0.0.1

For the life of me, I can't get those computers to use DNS. They can surf
the web, but they can't browse network shares, printers or even get their
email from outlook since our exchange box uses a FQDM.

Any suggestions on a fix for this?? Thanks all.

STEVE

 

[Chuck]

I have a Windows XP (home edition & Pro edtion, both have Service Pack 2, on
a workgroup - every computer is on the same subnet) machines on my network.
They are the only two computers that cannot browser to other computer shares
using the \\computername\c$ or My Network Places.

I can ping both computers using their IP address, but not their computer
name. I can ping from their computer to others, but only via IP, not
computer name.

I've ran "SFC /scannow" on both and that was fine.
I uninstalled and reinstalled File and Print sharing
I reinstalled TCP/IP
I did a "ipconfig /flushdns" on both computers
The hosts files only have one entry - the 127.0.0.1

For the life of me, I can't get those computers to use DNS. They can surf
the web, but they can't browse network shares, printers or even get their
email from outlook since our exchange box uses a FQDM.

Any suggestions on a fix for this?? Thanks all.

STEVE

Steve,

Are you saying that you can't access other computers using "\\computername\c$"
from these 2 computers, or that you can't access these 2 computers using
"\\computername\c$" from other computers?

With Simple File Sharing and Guest authentication, the "\\computername\c$" share
is going to be inaccessible. Are you running Simple File Sharing on the XP Pro
computer too, by any chance?
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Simple>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Simple

If the problem is with accessing other computers from these, we'll have to do
more analysis. Let's look at "browstat status" and "ipconfig /all" from each
computer, so we can 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

 

[Chuck]

i think computer browser service on them has either failed or is disabled

Harjeet

Harry / Harjeet,

What time zone and clock setting do you have on your computer? You appear to be
posting 8 hours into the future.

 

[Harry]

i think computer browser service on them has either failed or is disabled

Harjeet

 

[Guest]

I found a fix for it, from Chuck's website, which lead me to Microsoft's
website (THANK YOU Chuck)

When I did ipconfig /all - I saw the node type was peer-to-peer. Well, I
don't use a WINS server on my network here at work, so I followed the
instructions in this article:

http://support.microsoft.com/default.aspx/kb/903267

Deleted one value in a registry key, rebooted, and now it works fine.

Thanks again

 

[Chuck]

I found a fix for it, from Chuck's website, which lead me to Microsoft's
website (THANK YOU Chuck)

When I did ipconfig /all - I saw the node type was peer-to-peer. Well, I
don't use a WINS server on my network here at work, so I followed the
instructions in this article:

http://support.microsoft.com/default.aspx/kb/903267

Deleted one value in a registry key, rebooted, and now it works fine.

Thanks again

Thanks for the update, Steve. Glad I was able to help.