I have a wired ADSL router with 2 computers connected through it. Both systems can access the internet and can otherwise act independently without any problems. The only thing that we can't seem to figure out is how to connect directly from one PC to the other for the purposes of filesharing and such. Here is everything I can think of that's relevant:

1. PC #1: Windows XP Media Centre
2. PC #2: Windows XP Professional
3. The Workgroup name is the same for both systems
4. "Use Simple Filesharing" has been unchecked in both systems' Folder Options
5. A static IP address has been assigned to each system for the purposes of port forwarding
6. Our desired folders have been shared, with full permissions granted
7. When PC #1 attempts to connection to PC #2 there is a login prompt, the sign in details for which no one can figure out
8. When PC #2 attempts to connect to PC #1 the following error message appears:

\\[Computer Name] is not accessible.  You might not have permission to use this network resource.  Contact the administrator of this service to find out if you have access permissions.

The network path was not found.

9. Both computers show up in Network Places (albeit they are inaccessible)
10. "File and Printer Sharing for Microsoft Networks" is enabled on both systems' network connections
11. The firewall on each system has had our network added to its "Trusted Networks" zone

That's about all I can think of :)

Any help would be greatly appreciated!

Thanks.

Dani AI

Generated

Helpful follow-ups and targeted checks to narrow this down (builds on ' firewall suggestion and 's observations).

Start by isolating name-resolution, SMB reachability and authentication with these quick tests (replace IP/share as needed):

ping 192.168.1.10
nbtstat -A 192.168.1.10
net view \\192.168.1.10
net use * \\192.168.1.10\ShareName /user:REMOTEPC\username password
  • If ping fails: basic IP/route problem or wrong netmask/gateway.
  • If ping works but nbtstat shows no NetBIOS names, name resolution (NetBIOS/WINS) is the issue.
  • If net view fails while ping works, SMB ports or the Server service are the usual culprits.

Confirm Windows services and bindings without repeating previous checks: open Services (services.msc) and verify Server, Workstation, Computer Browser and TCP/IP NetBIOS Helper are running and set to Automatic. In the NIC properties confirm both Client for Microsoft Networks and File and Printer Sharing are installed and bound. Ensure NetBIOS over TCP/IP is enabled in the IPv4 -> Advanced -> WINS tab if name resolution is flaky.

Firewall/router and authentication hints: third-party security suites frequently block SMB even when the Windows firewall is set. If disabling firewalls helped, add explicit exceptions for TCP/UDP 137–139 and TCP 445 and re-enable. Consumer routers can sometimes block LAN-to-LAN traffic (client/isolation features) — try a direct connection (switch or crossover cable) to rule the router out. For credential prompts, either create matching user accounts+passwords on both machines or temporarily enable Simple File Sharing / permit Guest/Everyone on the share to test access; revert to least privilege once resolved.

If problems persist, capture Event Viewer entries on the target machine and run a TCP port scan (confirm 139/445 listening). These traces usually point directly to either a service/permission mismatch or a device-level block.

Paddy,

Can you try disabling the firewalls on both clients for me, then attempt connecting. Also try connecting via \\<internal ip address>\

If you are protected by hardware firewall (your router) running ICF (windows firewall) on both machines can be counterproductive and unnecessary.

Give that a whirl and let me know how it works out.

Jon

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.