Member Avatar for billylondon

Background -- 3 computers all runnung Win XP, on the same workgroup, connected in a wireless network, as follow:
1. PC-A: Win XP Pro, workgroup--CK
2. laptop-B: Win XP Pro, workgroup--CK
3. netbook-C: Win XP, workgroup--CK

Symptom --
1. laptop-B and netbook-C can see each other on workgroup, but cannot see PC-A.
2. PC-A cannot see the workgroup or any computer, including itself.
3. PC-A get error msg refusing access to network due to lack of authority.

Solution --
Is there an easy solution for this problem?

Thank you for any advice

Bill

  • 2 Contributors
  • 1 Reply
  • 261 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by la1

Dani AI

Generated

Given 's description and 's observation about firewalls/credentials, this looks less like a router problem and more like a Windows‑host issue on PC‑A: common roots are incorrect IP/bindings, NetBIOS/browse services stopped, or share/authentication blocked at the OS level. The steps below are ordered to find the cause quickly and safely.

Run these checks on PC‑A from an elevated command prompt and note results:

ipconfig /all
ping <other-machine-IP>
nbtstat -n
net view

Expected signals: an IPv4 address on the same subnet as the other two machines (not an APIPA 169.254.x.x), successful ping by IP (shows basic connectivity), nbtstat -n should show the machine's NetBIOS name registered, and net view should list visible servers/shares. If ping by IP works but net view fails, the problem is name/NetBIOS or service-related rather than physical network.

Confirm Windows networking services and bindings: open Services (services.msc) and ensure Computer Browser, Server, Workstation and TCP/IP NetBIOS Helper are set to start automatically and are running. In Network Connections → adapter → Properties, verify that Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks are bound to the adapter. Disable any extra network adapters (e.g., wired + wireless) while testing to avoid routing confusion.

Firewall and permissions: third‑party firewalls commonly block SMB/NetBIOS — allow File and Printer Sharing or temporarily disable the firewall for testing, then reapply secure rules. Check share permissions and local user accounts; a quick test is creating a temporary local user with the same name/password on each machine or granting the Everyone group read access to a test share to isolate authentication problems. Review System/Application event logs for related error entries. After fixes, restart affected services or the PC and re-enable firewalls with appropriate exceptions.

Member Avatar for la1

Yes
1. make sure all firewalls are OFF, Till you get your network going.
2. make sure the workgroup name is the same on all PC's
3. static or dynamic ip ? I will assume dynamic (DHCP ENABLED)
4. I will assume you have a user id and password for each machine.
Since you do not have a server to validate user credentials...you have to log onto every computer with every account...so that is 9 times you have to log on...only have to do this once, althogh you can see why MS does not recommend worgroups larger than 10 machimes

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.