Just wanted to help you with a task list from one of the options from ShineOn's answer (which is accurate, but IMHO too techie for your problem).
1. Choose properties on your Local Area Connection
2. Delete all the services and protocols you find there (unless you know that TCP/IP is configured properly, in that case leave it and skip step 3c).
3. Install the following
a. Client - Client for Microsoft Networks
b. Service - File and Print Sharing for Microsoft Networks
c. Protocol - NetBEUI Protocol
4. Make sure there are check marks on all three (What ShineOn referred as BOUND).
5. If, as you stated, both computer names are identical - "Computer", change them to Computer1 and Computer2.
Restart and you should be able to "see" both computers.
Share a folder on both computers.
Main Topics
Browse All Topics





by: ShineOnPosted on 2006-06-07 at 14:49:30ID: 16856957
If you're trying to do a peer-to-peer Windows to Windows connection, then NetWare has nothing to do with it.
transport, or NetBEUI doesn't matter when you're crossover-cable-connecting , it still needs the "Microsoft networks" client.
You want to look in "entire network" and then "Microsoft Windows Network" and then "Workgroup" in order to find the other Windows PC.
While it is true that IPX is actually a better transport for NetBIOS than IP is, that's just a protocol, and doesn't mean you're using NetWare. You only "need" the crapware(tm) Client Service for NetWare if you are connecting to a NetWare server over IPX and are afraid for some reason to use the more-appropriate Novell Client32.
The "network" in "my network places" you need to look at, regardless of the protocol you're using, is Windows. In order to "see" that network, you need to have the "Client for Microsoft Networks" installed, and you need to have a protocol bound to that client that handles NetBIOS, and whether you use NetBT (NetBIOS over TCP/IP), NWLink IPX/SPX/NetBIOS-compatible