I am having a problem accessing a windows xp shared folder on my network from my laptop (running windows media center). I cannot access the computer by \\computer-name or by \\ip-address. In fact, I cannot and never have been able to access any shared computer with this laptop (as far as I can remember). However, I CAN access a web server so long as I access it in the form of . I have tried uninstalling and installing File and printer sharing for MS windows along with the Windows Network Client service to no avail. Any help anybody could provide would be greatly appreciated.

Regards,

Tyler S. Breton

Dani AI

Generated

Quick summary and focused diagnostics that pick up where the thread left off: reports the Media Center laptop can ping hosts by IP and reach an HTTP server at , but cannot access SMB shares via \computer-name or \ip-address and cannot ping by name. No third‑party firewall and all machines are in the same workgroup. suggested LSP/Winsock issues; that is one possibility but name resolution, client bindings, and the SMB ports are the higher‑priority checks.

Checklist of targeted checks (ordered by how quickly they isolate the problem):

  • Verify the LAN adapter has the Microsoft networking components bound (Client for Microsoft Networks and File and Printer Sharing present and checked in the adapter Properties).
  • Confirm services: Workstation and TCP/IP NetBIOS Helper are started (Services.msc).
  • Confirm NetBIOS name resolution is enabled: adapter -> IPv4 Properties -> Advanced -> WINS -> “Enable NetBIOS over TCP/IP” (if the network relies on NetBIOS/WINS).
  • Check whether AP/client isolation or router rules block SMB even when HTTP works.
  • If the network stack or LSP was damaged, reset Winsock and IP stack (see commands below).

Useful command checks (run from a command prompt on the laptop):

ping 192.168.x.x
nbtstat -n
nbtstat -A 192.168.x.x
nbtstat -c
net view \\192.168.x.x
netsh winsock reset
netsh int ip reset
ipconfig /flushdns

What to read from results: nbtstat -A <ip> will show whether the remote machine answers NetBIOS queries. net view \\ip lists shares if SMB is reachable. If NetBIOS fails but IP-level pings succeed, enable NetBIOS over TCP/IP or add a hosts entry for a quick name workaround. If SMB ports 139/445 refuse connections while HTTP works, the remote machine or a router is blocking SMB. If Winsock/LSP corruption is suspected (per ), a Winsock reset plus reboot is safer than ad hoc LSP removers.

Caveat for later readers: older XP-era setups used NetBIOS/SMBv1. Modern systems often disable SMBv1 for security; when mixing old and new machines, verify which SMB versions each endpoint supports before re‑enabling legacy protocols.

Recommended Answers

All 8 Replies

are you administrator?

are you administrator?

Yes, I am the Admin on the machine.

has this always happened, or is it recent?

As far as I can remember it's happened. I havent really tried to use the feature until now.

well, i can't think of much other than your account is private, or network sharing is off.

can you ping the other computer by IP address?

what about by it's computer name?

do you have a firewall installed on the laptop like Norton Internet Security?

are all the computers on the same workgroup or domain?

I can ping by ip.

I cannot ping by computer name.

No firewall.

Same workgroup.

I have a feeling its a WINS issue.

Regards,

Tyler S. Breton

spyware probably took it out. This should fix it. I keep it on a flash drive...

LSP fix

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.