Member Avatar for geomalak1980

I am haveing problems seeing computers in a workgroup. I am able to ping fine, but not able to see computers whenever I go under networks

  • 4 Contributors
  • 4 Replies
  • 185 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by stevedaniel

Dani AI

Generated

If machines respond to ping but Explorer’s Network view is empty, the problem is almost always discovery/browsing (not basic IP). Windows lists peers only when discovery services are running and the firewall allows discovery/SMB traffic; when those pieces are blocked or stopped, peers won’t appear even though ICMP works. (learn.microsoft.com)

Checklist (run on every affected PC): set the network profile to Home/Work (Private) rather than Public; enable Network Discovery and Turn on File and Printer Sharing in Control Panel → Network and Sharing Center → Advanced sharing settings; and make sure the discovery and sharing services are running (DNS Client, Function Discovery Resource Publication, Function Discovery Provider Host, SSDP Discovery, UPnP Device Host — and the Server/Workstation services so shares are advertised). These are the documented dependencies for Windows network discovery and file sharing. (support.microsoft.com)

Do not permanently disable the firewall. Instead allow the built‑in discovery/sharing rules (or re‑enable the “Network Discovery” firewall group). If the Network Discovery toggle immediately reverts, re‑enable the appropriate firewall rule group (many admins use the documented netsh approach) and then restart the discovery services. Example command (run as admin): 

netsh advfirewall firewall set rule group="Network Discovery" new enable=Yes

These steps are commonly used when the toggle won’t stick. (learn.microsoft.com)

If ping-by-IP works but names don’t resolve or machines still don’t show, test access directly with \\192.168.x.x or \\computername. Check NetBIOS/Computer Browser behavior and that all machines share the same workgroup and subnet — browser lists and NetBIOS name resolution still affect what Explorer displays on mixed/legacy networks. (support.microsoft.com)

Notes on earlier replies: ’s IPX/SPX suggestion only helps if the environment is using Novell NetWare (NWLink/NWLink IPX/SPX is legacy for NetWare); it won’t fix normal Windows SMB discovery. ’s proxy/IE advice is unlikely to help — network discovery uses WSD/UPnP/NetBIOS/SMB, not an HTTP proxy. If problems persist after the checklist, look for third‑party security suites, Group Policy, or a router isolation setting; restarting the Function Discovery services and the routers/switches often makes the Network view repopulate. (manualzilla.com)

Recommended Answers

All 4 Replies

Member Avatar for rch1231

Hello,

If this is a windows XP systems you have to add the IPS/SPX protocol to the network device under properties. Also check the windows firewall and temporarally turn it off till after you connect to the other system the first time it will see them after that.

Member Avatar for alone88

hello
If this is a windows XP you use aa proxy and internet Explorer security and add ip adres then u lock the all web browser.
and you made user name and pasword.
everything in your heands GOD BLESS you

Member Avatar for alone88

Sorry CC PROXY you use bro

Member Avatar for stevedaniel

Thanks Alone88
for providing information

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.