Conflict between multiple routers

[MarkST3]

Hi,

I've got a bit of an intermediate setup which probably isn't going to be long-term but I can't think of a logical reason why it shouldn't work so I'd like to solve it... after all, how do you learn about things if you don't give it a go :-)

I have combined DSL modem & wireless router providing internet access "wirelessly" to multiple PCs at home. I also have a wired router, connected to our main PC, also connected to a NAS HD which I use to back-up music and photos- this wired router has no other connection inc internet. (For info, the NAS HD used to be connected to the wireless router but the bandwidth wasn't high enough to support the large volume of data when I was backing up, particularly when our laptop was being used to go online).

So in summary- the subject PC is connected by wires to a NAS HD via a wired router, but accesses the internet via a wireless router/modem.

My problem is that there seems to be a conflict between the 2 arrangements- I'm a novice when it comes to setting up networks so I may well have missed something obvious! I have ensured the routers have different IPs (wireless 192.168.0.1 and wired 192.168.1.1) but other than that are left with basic/automatic settings. There was a short time when all seemed to be working in harmony, but shortly afterwards only one set of network connections will work at a time i.e. disable the wired network adapter and the wireless connection to the internet works fine; disable the wireless adapter and the wired connection to the NAS works fine.

I've plugged all known IPs into my software firewall, and even disabled the firewall and it has no effect.

I've seen in other places there are some system states that can help diagnose so I've included them below- from them I notice that:
1) 2 "tunnel adapter local area connections" seem to share the same physical address.
2) The IPv6 DUIDs for both network adapters are the same.

Could they be what's causing the problem here?

Cheers,

Mark

ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Mark
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Ralink RT61 Turbo Wireless LAN Card
Physical Address. . . . . . . . . : 00-0E-2E-D7-F9-12
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d908:8d50:6649:1e5d%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 11 July 2010 01:14:44
Lease Expires . . . . . . . . . . : 14 July 2010 01:14:43
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 234884654
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0F-AC-0D-11-00-1D-09-82-69-5D

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82562V-2 10/100 Network Connection
Physical Address. . . . . . . . . : 00-1D-09-82-69-5D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ac0d:a0e2:ccfe:6a3%9(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.136(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 11 July 2010 00:39:08
Lease Expires . . . . . . . . . . : 18 July 2010 01:15:21
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 201334025
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0F-AC-0D-11-00-1D-09-82-69-5D

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

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{stuff!}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

route print

Interface List
10 ...00 0e 2e d7 f9 12 ...... Ralink RT61 Turbo Wireless LAN Card
9 ...00 1d 09 82 69 5d ...... Intel(R) 82562V-2 10/100 Network Connection
1 ........................... Software Loopback Interface 1
8 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
25 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
13 ...00 00 00 00 00 00 00 e0 isatap.{stuff!}
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.136 20
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.3 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.0.0 255.255.255.0 On-link 192.168.0.3 281
192.168.0.3 255.255.255.255 On-link 192.168.0.3 281
192.168.0.255 255.255.255.255 On-link 192.168.0.3 281
192.168.1.0 255.255.255.0 On-link 192.168.1.136 276
192.168.1.136 255.255.255.255 On-link 192.168.1.136 276
192.168.1.255 255.255.255.255 On-link 192.168.1.136 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.136 276
224.0.0.0 240.0.0.0 On-link 192.168.0.3 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.136 276
255.255.255.255 255.255.255.255 On-link 192.168.0.3 281
===========================================================================
Persistent Routes:
None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
9 276 fe80::/64 On-link
10 281 fe80::/64 On-link
9 276 fe80::ac0d:a0e2:ccfe:6a3/128
On-link
10 281 fe80::d908:8d50:6649:1e5d/128
On-link
1 306 ff00::/8 On-link
9 276 ff00::/8 On-link
10 281 ff00::/8 On-link
===========================================================================
Persistent Routes:
None

 

[ZeroG]

Sorry for the zombie post, but I was running into the same issue and this thread was the only thing I could find that was similar to the issue I was experiencing with duplicate DUIDs. I just wanted to post a solution here so other people could discover the fix via google as I hoped to.

In my case, I obtained duplicate DUIDs from imaging a Windows 7 machine on Altiris and applying that image to another computer. If you used any back-up system to quickly get two machines up and running (Ghost, Altiris, LANDesk), there is a chance that the registry values that cause this issue were merely copied.

After doing some searches through the registry, I found the following values:

HKLM\System\ControlSet001\services\TCPIP6\Parameters\Dhcpv6DUID
HKLM\System\ControlSet002\services\TCPIP6\Parameters\Dhcpv6DUID

Those strings should contain that computer's DUID. Change the DUID so it matches the correct hardware address. Once you have changed the strings, restart. It should then give the new DUID you assigned it. Hopefully, this works for you.

 

[niemiro]

I am not exactly sure, and am really not an expert in this area, I belive that the commonest problem is not disabling DHCP on the second router. Does this ring a bell with anyone?