PC is not detected in network

1

One of my windows XP PCs cannot be accessed from any other PC in the network.The network is configured by using Workgroup. If I access PC by using pcname from Run such as \\pcname\, an error comes like Network path not found. If I try the same with the PC I have a problem with then the location opens. (I mean opening \\PC123\ in PC123 itself) . But from another PC it does not work.

I have already tried troubleshooting it.

1. I have tried disabling firewall, antivirus, etc.
2. I have also checked accessing from different OSs PC. But nothing works.
3. I have checked Workgroup and the Workgroup name is proper.
4. I tried running nbtstat -a PC123 and it worked properly and output was:

Local Area Connection 2:
Node IpAddress: [192.168.1.132] Scope Id: []

       NetBIOS Remote Machine Name Table

   Name               Type         Status
---------------------------------------------
PC123           <00>  UNIQUE      Registered 
CA              <00>  GROUP       Registered 
PC123           <20>  UNIQUE      Registered 
CA              <1E>  GROUP       Registered 

MAC Address = E0-69-95-35-FC-30

5. I tried net use * \\PC123\d where d is sharename. I got the following error:

System error 53 has occurred.
The network path was not found.

6. I tried a simple ping command like ping pc123 and the ping command was successful.
7. I have checked the Enable NetBIOS over TCP/IP setting and the checkbox is checked.
8. I tried enabling the guest account, but I am getting the same error after enabling it also.
9. I tried running \\<IP address of PC123>\ and it does not work and I get the following error message: The network path was not found.

10.But we can access the PC using windows remote desktop(RDP)

After trying all this, the error was not solved, so please help me on this.

IT researcher

Posted 2013-12-11T07:12:04.593

Reputation: 783

Does \<IP address of PC123>\ work ? – Lawrence – 2013-12-11T07:14:32.310

@Lawrence. No. Please see updated question – IT researcher – 2013-12-11T07:21:05.643

have you checked the cable and link status? perhaps changed the port the cable plugs into on the switch? I had a switch port burn out after power surge a few months ago, and it took me a few minutes to diagnose. most unexpected. – Frank Thomas – 2013-12-11T13:38:31.070

@FrankThomas That is proper. From the PC which has this problem i can connect to all other pc in network. – IT researcher – 2013-12-12T07:48:07.407

Sounds very much like it could have to do with Windows Firewall, probably on the XP machine, but could be on the other as well. Have you tried this with temporarily disabling windows (or other software firewalls as well - if you have them enabled) firewall? – r0berts – 2013-12-12T19:08:32.963

@r0berts I have already mentioned in my question that i have disabled firewall,antivirus etc – IT researcher – 2013-12-13T05:09:28.943

OK and I understand that all the rest of it you have tried with all firewalls and antivirus disabled. Have you got Client for Microsoft Networks installed and running on both machines. It should be listed as part of network adapter's properties. – r0berts – 2013-12-13T07:26:03.577

@r0berts we have setup all pc in same network and same workgroup.Also Client for Microsoft Networks already installed in both pc. – IT researcher – 2013-12-14T07:28:06.827

>

  • Could you please try to add a share on the pc123, access it and give us feedback if that works? (Instead of connecting to the \pc123 root) 2. On the network adapters settings, please try to remove the 'windows file and printer sharing' protocoll and readd it. 3. Please elaborate on what you did with "I tried to disable firewall and antivirus" as in my experience 99% things like this happen, it's caused by a firewall. What product do you use? Have you tried uninstalling it just to be 100% sure?
  • < – Langhard – 2013-12-14T07:50:42.130

    Couldn't agree more - this problem in my experience also has been caused by software firewalls. Except when there was a tiny error in misspelling names which I had overlooked. – r0berts – 2013-12-17T11:16:28.097

    @r0berts If i set firewall to OFF in control panel does it turn off firewall completely? OR i have to do something else? – IT researcher – 2013-12-18T05:54:12.323

    Researcher, if it doesn't turn off with control panel then the system is seriously messed up isn't it ;) If we think along this line, it can also be that a service is not running - not listening on the port. You can use netcat for testing. Two ways - 1. connect to the port on the machine that works, see results and compare them with results you get from the non-working machine. 2. - on the non-working machine use one netcat as a server, connect to it with netcat from the other machine and see if connection works (e.g. type in one machine appears on the other). If it does - firewall isn't on. – r0berts – 2013-12-18T12:40:08.970

    Answers

    0

    Anyway it sounds like firewall on PC123 is blocking connect. try to disable firewall through command line on PC123:

    netsh firewall set opmode disable

    and to enable it back if it doesn't work:

    netsh firewall set opmode enable

    Gena Gordeev

    Posted 2013-12-11T07:12:04.593

    Reputation: 51

    Yeah, I also think firewall type problems might be the issue. Also the output of nbtstat is different as to how I am used to diagnose problems with smbclient. What you potentially could do is boot a laptop from knoppix or NST live cd, configure it to be part of your workgroup (by the way - are you in domain or workgroup environment?) and query both of your PCs from there. – r0berts – 2013-12-14T11:32:54.247

    @r0berts I am using workgroup. I have already mentioned it in my question too. – IT researcher – 2013-12-16T05:55:07.440

    Researcher, I doubt heavily that a simple solution exists. The problem is a confusing one as you will see searching through microsoft. I only started to be clearer on how workgroups work only when I read on samba. I'd boot a live linux distro, configure it to be part of your workgroup and use samba troubleshooting strategies to find your answer. Good starting points are: http://www.samba.org/samba/docs/using_samba/ch12.html http://www.samba.org/samba/docs/using_samba/ch07.html Or you can resort to solutions that have worked on ms technet - such as changing your network interface card. G-luck

    – r0berts – 2013-12-17T10:44:09.910