LAN users not listed over wifi

Question

I recently created a small office network with 10+ computers. 9 of them are desktop computers so I used Ethernet cable to connect them.. The computers are connected to a switch via a patch panel and to a wifi router for internet access. All of these computers are connected to the same work group and sharing public files are enables. all sharing functions are enabled and every one can see each others computers over the network.

But the issue is with the one laptop that is connected over wifi to the network. The laptop lists some of the desktop computers that are in the LAN but not all. I used run command and gave the path to a non listed computer and it shows up very well. but the thing is, I need to list all the computer in the network places.

what should I do to this issue.

Laptop OS : windows 7 wifi router : dlink

stock settings with wifi password.

Solution

If I understand your question correctly it sounds like you are having an issue with Windows Network Discovery.

First things first, can you confirm that you can connect to shared resources such as a file share or print share of the non-listed computers via a UNC path from the laptop and then back from the non-listed computer to the laptop.

I'm assuming you are not on a Windows Domain and are using Workgroups.

• Make sure all the machines are in the same Workgroup.
• Make sure Network Discovery is turned on and the firewall is configured appropriately on the computers that are not be enumerated by the laptop.
• Be patient, Microsoft says that it can take up to 15 minutes for shared resources to be detected via Network Discovery.
• Ensure that your D-Link All-In-One-Device is not filtering or otherwise blocking connections between the wired and wireless segment in such a way as to prevent Network Discovery from working properly (without knowing your subnetting or firewall setup I can't be more specific)
• Verify that whatever name resolution service you are using for your Workgroup is functioning appropriately.
• Verify that the, DNS Client, Function Discovery Resource Publication, SSDP Discovery and UPnP Device Host services are running on both the unlisted machines and the laptop.
• Make sure all your machines are using the appropriate network profile (Public, Private, Work).

Comments

[Zdenek]

Windows can break the discovery feature easily, so first make sure the same laptop works fine over ethernet. Next, make sure AP Isolation is off in the router, the radio is bridged to the LAN, rather than routed and that it is not a guest network (which has restrictions). Make sure there are no multiple IPs configured manually in the laptop; this breaks name resolution.

[BatchyX]

Come on ... MAC filtering is useless, and broadcasting blank SSID actually reduces security, because the client will broadcast probe requests with the SSID in plain text everywhere just to be able to detect the AP. This opens the possibility for hackers to actually bruteforce the passphrase used by the client, wherever it is. And otherwise, it is as useless as MAC filtering anyway.

[Imesh Chandrasiri]

@lasith : I have enabled all the sharing options in the laptop as well as all the desktop PCs in the LAN. The desktop PCs have a perfect network map and they can access all of the shared folders perfectly. The issue is with the laptop.. And the Wifi is PW protected. I meant all the other options by default. A third party firewall can be the culprit cus, kaspersky is running. Can you state any ports and protocols I should allow from the firewalls.

[Lasith]

Additionally, ports can be found by looking and Windows Firewall. There are several ports that you need to pay attention. You can disable the security system and check to confirm that the issue is caused by the Kaspersky suit.

[BatchyX]

@Lasith: I have took RSN/WPA2 into account. Still, someone seeing these probe requests can mount a fake AP and can hope to retrieve a EAPOL 3/4 from the client, which is what a normal AP uses to check the password. The fake AP can fetch it and bruteforce it offline (except when SAE is used, but who knows SAE ?), hoping to break medium/weak passphrases. But anyway, adding useless security to already strong security is even more useless, it adds more trouble for absolutely nothing.

[Lasith]

I do not think you are taking it to account. WPA2-PSK what you are mentioning while I am not. It is not recommended to use PSK in an enterprise. I m completely aware of that WPA2-Px has vulnerabilities and also the SSID probing. With a pass phrase less than 21 keys can be vital. There are issues with ssid broadcast and mac filtering (can be spoofed easily). In a properly configured ent. it is quite difficult to hijack as an outsider. Even for insiders. Just wpa won't do, of course. Its advisory to follow security in depth with layered approach. Good conv. though it won't help Dimal anyway.