XP Home Edition computer unable to connect to shared files

22 Dec 2005 4:30 PM

Ron

Have a small problem with a peer to peer network. Both machines are running
XP Home Edition with SP2. The network contains 3 machines. Machine A is the
server. Machine B is one client and Machine C is other client.

Machine B can connect no problem all is good.

Machine C cannot connect. Get no error messages at all. When I run the net
view command I get the following error:

System error 6118 has occured
The list of servers for this workgroup is not currently available.

I have verified that all machines have unique system names and the workgroup
for all machines is MSHOME. If I try to the command

net view \\machinea

I get an error 53 returned.

Problem occurs with firewall turned on and firewall turned off. There are
no third party firewall programs running.

Long term plan is to upgrade to XP Pro and get away from all this, but
currently due to time constraints, not an option.

Any ideas what the issue could be? It sounds like there is a problem with
the workgroup name on Machine C buy I'm not sure.

Thanks,
Ron

22 Dec 2005 7:03 PM

Chuck

On Thu, 22 Dec 2005 08:30:06 -0800, Ron <R**@discussions.microsoft.com> wrote:

Show quoteHide quote

>Have a small problem with a peer to peer network. Both machines are running
>XP Home Edition with SP2. The network contains 3 machines. Machine A is the
>server. Machine B is one client and Machine C is other client.
>
>Machine B can connect no problem all is good.
>
>Machine C cannot connect. Get no error messages at all. When I run the net
>view command I get the following error:
>
>System error 6118 has occured
>The list of servers for this workgroup is not currently available.
>
>I have verified that all machines have unique system names and the workgroup
>for all machines is MSHOME. If I try to the command
>
>net view \\machinea
>
>I get an error 53 returned.
>
>Problem occurs with firewall turned on and firewall turned off. There are
>no third party firewall programs running.
>
>Long term plan is to upgrade to XP Pro and get away from all this, but
>currently due to time constraints, not an option.
>
>Any ideas what the issue could be? It sounds like there is a problem with
>the workgroup name on Machine C buy I'm not sure.
>
>Thanks,
>Ron

Ron,

If you're absolutely certain that there's no firewall problem, then look for an
anonymous access restriction, and for LSP / Winsock / TCP/IP corruption.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

If no help yet, provide "browstat status" and "ipconfig /all" from each
computer, so we can diagnose the problem. Read this article, and linked
articles, and follow instructions precisely:
<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 [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.