Network Discovery Issue...I think

Hey all,

Just changed from a Linksys WRT160N to a Belkin Play F7D4302UK and everything has gone smoothly apart from one thing. For some reason using the Belkin I don't think my PCs and devices (I have a Popcorn A110 too) are able to broadcast their presence to eachother anymore.

I can directly access them using their IP addresses but other than that even though they are all on the same Workgroup they can no longer find eachother to browse, also Homegroups can't be created anymore as they don't recognise another PC on the network setup for it. I can only assume that the Belkin is blocking some form of broadcast packet but I can't work out what one and if so how to open the port, the only options are port forwarding but whatever port it is that needs to be opened needs to open globally open, not just forwarded to one IP address.

Can anyone help?

Thanks

Russ

roakes said:

Hey all,

Just changed from a Linksys WRT160N to a Belkin Play F7D4302UK and everything has gone smoothly apart from one thing. For some reason using the Belkin I don't think my PCs and devices (I have a Popcorn A110 too) are able to broadcast their presence to eachother anymore.

I can directly access them using their IP addresses but other than that even though they are all on the same Workgroup they can no longer find eachother to browse, also Homegroups can't be created anymore as they don't recognise another PC on the network setup for it. I can only assume that the Belkin is blocking some form of broadcast packet but I can't work out what one and if so how to open the port, the only options are port forwarding but whatever port it is that needs to be opened needs to open globally open, not just forwarded to one IP address.

Can anyone help?

Thanks

Russ

Russ

Can you type cmd in search>right click then run as admin>
then ipconfig /all>then upload a screenshot of the output?

I suspect the router change changed you from IPv4 to IPv6 and may have contributed to the broadcast problem

Ken

I'm at work at the moment so no can do but it's definitely assigning IPv4 addresses to attached devices.

I can still send it later though if need be?

Just found a forum post elsewhere with a quote from Belkin support saying that the latest range of routers (mine being one) don't support IPv6 at all.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Russ>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Russ-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Belkin

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E Gigabit Ether
net Controller
Physical Address. . . . . . . . . : 00-16-E6-87-98-FC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::70c2:a1e0:6842:15e5%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 18 August 2010 16:46:27
Lease Expires . . . . . . . . . . : 24 September 2146 23:15:33
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DHCPv6 IAID . . . . . . . . . . . : 234886886
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-CD-67-C8-00-16-E6-87-98-FC

DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.Belkin:

Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.2.2%13(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:1890:30aa:a152:6d94(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::1890:30aa:a152:6d94%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

I have disabled IPv6 on my network adapters and also assigned Static IP addresses (so hopefully circumventing anything the routers DHCP may be doing) but still got the same problem.