You need to start by verifying computer & Workgroup names:
-click "My Computer", "Properties", then click on the "Computer Name" tab
-check the 1. computer name (must be unique across your network), 2. Workgroup (must be identical for all computers). *FYI the computer name and Workgroup are case sensitive*. If you need to change either of these, click "Change" to make the adjustments then a restart is required before the changes take affect.
Part 2.
Now you need to verify the network connections (im going to assume that all of the computers/printer are on a single subnet)
-Go to the control panel, click on "Network Connections". Now you should be able to see the network adapters. Right click on the one in use (either LAN or Wireless) and check the following properties: Verify items under "used by the connection" are there and the box is checked: 1. Client for Microsoft Networks 2. File and Printer Sharing for Microsoft Networks 3. Internet Protocol (TCP/IP). Now check to make sure NetBIOS is enabled by clicking on "Internet Protocol (TCP/IP) ---> "Properties". Click the "General" tab then "Advanced". Click on the "WINS" tab. Under NetBIOS setting, click "Enable NetBIOS over TCP/IP". Now you can close the dialog boxes.
Now you need to verify the subnet
-Click Start--->Run, cmd and press "ok". now type this in: ipconfig /all (there must be a space between ipconfig and /all) and check the subnet mask of each adapter
Next step is to verify the services needed to allow printer sharing
-Start->Run enter services.msc Scroll through service list to find then check
=> Computer Browser
=> TCP/IP NetBIOS Helper Service
=> Event Log
 |
To set a service’s Startup Type
=> Rt click on service then Properties
=> Set Startup Type = Automatic
After that's all finished, restart the computer(s) again and check for visibility.
source : https://answers.yahoo.com/question/index?qid=20090202150709AAG0t5m
.......................................................................................................................................................
TCP/IP stack repair options for use with Windows XP with SP2.
Start, Run, CMD to open a command prompt:
Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reboot the machine.
If that doesn't work, let's see this.
Start, Run, CMD to open a command prompt:
Type the following two commands:
nbtstat -n
ipconfig /all
Right click in the command window and choose Select All, then hit Enter.
Paste the results in a message here.
If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.
-----------------------------------------------------------------
I assume you mean that NetBIOS is enabled in the WINS part of the TCP/IP properties for the wireless connection, because the nbtstat and ipconfig are sure saying the opposite. Be sure the setting is 'enabled' and not 'default.'
By the way, while not part of the problem, your ipconfigs are indicating that your "very simple and cheap HUB" is actually a router. With a hub you'd be getting APIPA (169.254.x.y) or manually assigning IP addresses.
While I ponder this some more, try these repairs on PC1 to see if the NetBIOS thing gets squared around. If we get NetBOIS working your problems will likely go away.
(From a JohnWill post)
TCP/IP stack repair options for use with Windows XP with SP2.
Start, Run, CMD, OK to open a command prompt.
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log
Reboot the machine.
