Network Name Cannot Be Found between 2 XP Pro computers. Just stopped working
I have a computer network that has successfully worked for several years and is all of a sudden stopped. The only thing that I can think of that has changed is that I installed the "critical updates" that windows recommended I install. I don't know that this was the problem as I didn't test the network for several days before or after that installation, but it may be an important cluemy network appears to still be intact as I can ping and access any computer manually via IP address ( \\192.168.1.x ), however I cannot access or ping them anymore by name ( \\computer_1 ). All of my shared drives and printers reference computer names for their ports. None of the networked computers show up in the network neighborhood with the exception of the computer that I am working on.Thinking it was simply a virus protection/firewall issue, I disabled all of this on both of the xp computers, but it made no difference. The kicker is that the Mac computers can still access the shared printer via computer name. The problem seems to be between the two xp computers.All of the obvious print and file sharing settings have been verified to be correct. I even went as far as to setup the network again, which made no difference.Both of the xp computers showed FALSE when I verified which was the master browser, so I changed the Desktop Computer to TRUE to show that as the master browser.On my network I have 2 MAC OSx 10.5, and 2 windows xp pro SP3. Macs can still access shared printers, XP computers can't.....Here are the results for nbtstat -n and ipconfig /all:WINDOWS XP DESKTOP COMPUTER CONNECTED VIA ETHERNET CABLE:C:\Documents and Settings\Drew>nbtstat -nLocal Area Connection:Node IpAddress: [192.168.1.7] Scope Id: [] NetBIOS Local Name Table Name Type Status --------------------------------------------- DREW_DESKTOP <00> UNIQUE Registered MSHOME <00> GROUP Registered DREW_DESKTOP <20> UNIQUE Registered MSHOME <1E> GROUP Registered C:\Documents and Settings\Drew>ipconfig /allWindows IP Configuration Host Name . . . . . . . . . . . . : DREW_DESKTOP Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : NoEthernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : 3Com EtherLink 10/100 PCI TX NIC (3C905B-TX) Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.1.7 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.1 Lease Obtained. . . . . . . . . . : Tuesday, December 28, 2010 10:55:34AM Lease Expires . . . . . . . . . . : Wednesday, December 29, 2010 10:55:34 AM WINDOWS XP LAPTOP CONNECTED VIA WAN:C:\Documents and Settings\Drew>nbtstat -nWireless Network Connection:Node IpAddress: [192.168.1.3] Scope Id: [] NetBIOS Local Name Table Name Type Status --------------------------------------------- DREW_MACBOOK <00> UNIQUE Registered MSHOME <00> GROUP Registered DREW_MACBOOK <20> UNIQUE Registered MSHOME <1E> GROUP Registered MSHOME <1D> UNIQUE Registered ..__MSBROWSE__.<01> GROUP RegisteredLocal Area Connection:Node IpAddress: [0.0.0.0] Scope Id: [] No names in cachePdaNet Broadband Connection:Node IpAddress: [0.0.0.0] Scope Id: [] No names in cacheBluetooth Network Connection:Node IpAddress: [0.0.0.0] Scope Id: [] No names in cacheC:\Documents and Settings\Drew>ipconfig /allWindows IP Configuration Host Name . . . . . . . . . . . . : DREW_MACBOOK Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Peer-Peer IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : NoEthernet adapter Wireless Network Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Atheros AR5008 Wireless Network Adapter Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.1.3 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.1 Lease Obtained. . . . . . . . . . : Tuesday, December 28, 2010 8:24:41 AM Lease Expires . . . . . . . . . . : Wednesday, December 29, 2010 8:24:41 AMEthernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Description . . . . . . . . . . . : Marvell Yukon 88E8058 PCI-E GigabitEthernet Controller Ethernet adapter PdaNet Broadband Connection: Media State . . . . . . . . . . . : Media disconnected Description . . . . . . . . . . . : PdaNet Broadband Adapter Ethernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) Thank you in advance for your help.1 person needs an answerI do too
December 28th, 2010 2:16pm

HiIf the firewall AV are 3rd party suit Disable them can still block the LAN traffic.Try on each computer the following.WinSock and TCP/IP Refresh. Type Cmd in the Start Search text box.Press Ctrl-Shift-Enter keyboard shortcut to run a Command Prompt as an Administrator. Allow elevation.Type netsh winsock reset in the Command Prompt , and then press the Enter key.Do the same processes for refreshing the TCP/IP just replace the typed command with.netsh int reset press Enteripconfig /flushdns press EnterRestart your Computer. Jack-MVP Windows Networking. WWW.EZLAN.NET
Free Windows Admin Tool Kit Click here and download it now
December 28th, 2010 6:06pm

The problem is in your WINDOWS XP LAPTOP CONNECTED VIA WAN.Note that the "Node Type" is "Peer-Peer". When the node type is set to Peer-Peer, broadcasting is disabled and computers can't find themselves except and unless a WINS server is present. Usually a computer gets set this way by connecting to another network where the DHCP server sets this Node Type. Once set, it is not easily un-set. The following Microsoft KB article gives instructions on how to remedy this problem:"You cannot view other workgroup computers on the network on a Windows XP-based computer" < http://support.microsoft.com/kb/903267 >HTH, JW
December 29th, 2010 12:43am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics