Member Avatar for noople

Hello,
My problem is I just recently set up a home network, and my desktop computer can access my laptop and and see it's files for file sharing, but when i try to acces my desktop computer from my laptop it says

"Home is not accessable. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

The network path was not found"

"Home" is my workgroup name that is configured on both computers. I set up each computer the same way.

Can anyone help?

Thanks,
Gregory

  • 2 Contributors
  • 2 Replies
  • 128 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by noople

Dani AI

Generated

A one-way access problem like this (desktop can reach laptop, laptop cannot reach desktop) often looks like a network-name, NetBIOS/SMB, or service-level issue rather than a simple permission slip. 's McAfee fix and 's comments about account-related permissions are useful context; the checklist below focuses on quick, non-destructive diagnostics that help pinpoint where the failure occurs.

Try these commands on each machine (replace <other-IP> and <other-name> as needed):

ipconfig /all
ping <other-IP>
ping <other-name>
nbtstat -A <other-IP>
net view \\<other-IP>
net view \\<other-name>
arp -a
telnet <other-IP> 139

How to read the results:

  • If ping by IP fails, the problem is basic connectivity (different subnets, wireless AP client/isolation, bad cable, duplicate IP).
  • If ping by IP succeeds but net view \\IP fails, name resolution or SMB/Server service is likely at fault — nbtstat -A shows whether NetBIOS names are present.
  • If net view \\IP works but net view \\name does not, DNS/NetBIOS name resolution needs attention (WINS/hosts or NetBIOS settings).
  • If ports 139/445 refuse connections (telnet times out), a software firewall, router rule, or the Server/Workstation service binding to the NIC may be blocking SMB traffic.

Additional checks: confirm the Windows Server service is running, that the NIC has the Microsoft "File and Printer Sharing for Microsoft Networks" bound, and scan the System/Application event logs for SMB or Service errors. On wireless networks, verify the access point does not enable “client isolation” (blocks client-to-client traffic). For modern OS combinations, be aware file-sharing defaults and SMB support have changed over time; consult the OS vendor docs if interoperability issues persist.

Member Avatar for extofer

If you have all computers under the same workgroup name, that should be looked at first. Then, make sure you are trying to log in under a username that's found in all computers. Also, that user should have access to the share files as well.... see what I do

using "extofer" as my username, I assure I have that user name under ALL computers, with the same password.
Then, under the sharing folders, I assure "extofer" is selected under the permissions or security.

Member Avatar for noople

If you have all computers under the same workgroup name, that should be looked at first. Then, make sure you are trying to log in under a username that's found in all computers. Also, that user should have access to the share files as well.... see what I do

using "extofer" as my username, I assure I have that user name under ALL computers, with the same password.
Then, under the sharing folders, I assure "extofer" is selected under the permissions or security.

thank you for replying,
I actually figured out my problem it was a stupid mistake on m part. I forgot to check my firewall settings in mcafee so i had to allow my computers access.

so for anyone elsewith this problem...CHECK your FIREWALL

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.