The windows cannot find other PC's classic

%3CLINGO-SUB%20id%3D%22lingo-sub-2513486%22%20slang%3D%22en-US%22%3EThe%20windows%20cannot%20find%20other%20PC's%20classic%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2513486%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22western%22%3EWith%20a%20twist%20and%20hope%20someone%20can%20help.%3C%2FP%3E%3CP%20class%3D%22western%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22western%22%3ESo%20I%20have%20three%20PC's%20with%20Intel%20NIC%20with%20VLANs%20and%20untagged%20network%20192.168.255.48%2F28%3C%2FP%3E%3CP%20class%3D%22western%22%3EHTPC%20192.168.255.53%3C%2FP%3E%3CP%20class%3D%22western%22%3Emain%20PC%20192.168.255.55%3C%2FP%3E%3CP%20class%3D%22western%22%3EDNS%20192.168.255.62%3C%2FP%3E%3CP%20class%3D%22western%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22western%22%3EThey%20all%20have%20file%20sharing%20on%20with%20network%20discovery%20on%20but%20none%20see%20each%20other...until%20I%20leave%20the%20network%20window%20open%20for%20HTPC%20and%20DNS%20go%20to%20main%20PC%20run%20services%20and%20stop%20then%20start%20%22Function%20Discovery%20Resource%20Publication%22%20and%20both%20PC's%20show%20main%20PC%20in%20the%20network%20windows!...but%20this%20does%20not%20solve%20the%20problem%20as%20a%20refresh%20for%20the%20windows%20make%20the%20main%20PC%20disappear%20from%20the%20list.%3C%2FP%3E%3CP%20class%3D%22western%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22western%22%3ETested%20this%20on%20all%20other%20PC's%20and%20same%20thing.%3C%2FP%3E%3CP%20class%3D%22western%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22western%22%3ECould%20it%20be%20that%20I%20run%20VLAN's%20on%20the%20intel%20NIC's%3F%3C%2FP%3E%3CP%20class%3D%22western%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22western%22%3EI%20can%20still%20access%20PC's%20by%20IP%20fine%20its%20just%20the%20discovery%20thats%20the%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2513753%22%20slang%3D%22en-US%22%3ERe%3A%20The%20windows%20cannot%20find%20other%20PC's%20classic%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2513753%22%20slang%3D%22en-US%22%3EFound%20the%20problem%20but%20first%20when%20you%20stop%20then%20start%20%22Function%20Discovery%20Resource%20Publication%22%20it%20bypasses%20the%20firewall%20rules!%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20what%20was%20needed%20was%20a%20firewall%20rule%20for%20outbound%20for%20UDP%20local%20port%203702%20and%20remote%20port%20all.%3C%2FLINGO-BODY%3E
Occasional Contributor

With a twist and hope someone can help.

 

So I have three PC's with Intel NIC with VLANs and untagged network 192.168.255.48/28

HTPC 192.168.255.53

main PC 192.168.255.55

DNS 192.168.255.62

 

They all have file sharing on with network discovery on but none see each other...until I leave the network window open for HTPC and DNS go to main PC run services and stop then start "Function Discovery Resource Publication" and both PC's show main PC in the network windows!...but this does not solve the problem as a refresh for the windows make the main PC disappear from the list.

 

Tested this on all other PC's and same thing.

 

Could it be that I run VLAN's on the intel NIC's?

 

I can still access PC's by IP fine its just the discovery thats the problem.

1 Reply
Found the problem but first when you stop then start "Function Discovery Resource Publication" it bypasses the firewall rules!

So what was needed was a firewall rule for outbound for UDP local port 3702 and remote port all.