Windows Forum

Ask something
Discussion Locked

Cannot connect by Computer Name

0 helpful
7 replies

by mr. origami

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
One of those things that worked fine, then all of a sudden it stopped working. I have 3 XP Pro machines in a workgroup (all have same workgroup name). I used to be able to connect with \\CompName but no longer can. I must connect by IP address now, \\192.168.0.10. This is intermittent too. Sometimes I can connect by name, but most of the time not. As there are no "servers", I don't know how to check for something similar to a DNS or WINS database. Help?

7 replies

by qballrail

If connecting by either method proves inadequate, I would suggest checking hardware and protocols. In order for XP to talk to other XP boxes in the same workgroup without DNS or WINS servers, (Gateway), IPX/SPX must be installed. From your Control Panel, click on Network Connections. Then Right-Click on Local Area Connection and select Properties from the drop down menu. there you will see a list of protocols. If IPX/SPX is not installed, click Install just below that list.
Then select Protocol, click Add. In that list, you will see NWLINK IPX/SPX/NetBIOS compatible protocol. Select this and add. If this is not done on all machines, they will not talk to each other. The Network Setup Wizard in XP is not very relable, so you will have to manually set this up, if not already. A reboot may be required, but I do just so the drivers can load properly.

If all XP boxes are configured identically for the network except computer name, also check your NIC and connections. It is possible your NIC may have gone bad. However, before making any drastic moves, check your network cable, ensure there is a good connection. It is possible the cable is bad, swap it out for a known good one. Also check your hub, ensure all connectionsare secure.

Good luck and hope this helps!

by mr. origami

I appreciate your time and effort in trying to help, but I don't believe IPX/SPX must be installed for XP machines to communicate. TCP/IP is all that's required. IPX/SPX would make it work - probably - but it's a workaround which involves installing an additional protocol, additional overhead, and does not FIX the problem. Thanks anyway.

by spn

Hi ,

I would check for the latest drivers and install them . If you already have the latest drivers re-install them.

Since it was working , check if anything has changed ? ( New software / Hardware / Configuration ).

Check the settings of the NIC , specifily the TCP/IP settings.Enable NetBIOS over TCP/IP .Also check LMHost is enabled.

Does this happen from 1 computers ? ie If computer A needs to connect to B with \\192.168.0.10 is this the same if you try connect to C , and then this happen is it the same from the other computers?

Check for the Firewall to see if its enabled and if yes , which computers and why.

Thats all I can suggest for now , if that does not help could you please supply : NIC make and model , XP or XP+SP1 , Are you using internet sharing.

by mr. origami

Okay - after more extensive testing, here's the deal:
1] Latest drivers installed
2] NIC settings are fine (NetBIOS over TCP/IP and LMHOST)
3] Does not occur on each computer - only from CompA to CompB. CompA can connect to CompC fine, and CompBand CompC can connect to everything. It's just going from CompA to CompB. Also - it's intermittent. I can do start>run> and type \\CompB\c$ and get "network path not found" a few times, then all of a sudden it works. If I use \\\c$ it connects every time.

CompA in this case is a Dell Inspiron 8000 laptop with an integrated 3com 10/100 NIC and WinXP Pro SP1. CompB is a Micron desktop, XP Pro SP1, 3com 3c905btx 10/100 NIC.

by ilkopaunov

exchange the network cards between the B and C. Now if you can access B, exchange the cables. If you still can access B, buy a good network card.
;-)

by mr. origami

Well - the other guy never got back to me. Turned out to be both a bad NIC in desktop and corrupt drivers in laptop. Works fine now.

This discussion is closed to new replies.