So basically I have a Linksys WRT310N set to be 192.168.1.1 and DHCPing over the 192.168.1.100~192.168.1.199 range with Subnet Mask 255.255.255.0
Then I have a wired connection to a Linksys WRT160N in the basement that is Static ARP'd by the above router to 192.168.1.2 which is outside of the DHCP range.
The WAN mode is set to "Disabled" and WAN is bridged to the LAN, with the router set to 192.168.1.2 with a default gateway of 192.168.1.1. The routing mode is also set to "Router" instead of "Gateway"
Then I have a wired connection to a Linksys WRT150N as well which is located in the garage which is Static ARP'd by the Linksys WRT310N to 192.168.1.3.
With the WAN also "Disabled", WAN is bridged to the LAN, and the router is set to 192.168.1.3 with the default gateway set to 192.168.1.1. The routing mode is also set to "Router" instead of "Gateway"
Now the issue here-in lies with the fact that connecting to the WRT160N or WRT150N's wireless networks will take forever because it'll connect to the appropriate router, then take give or take sit for about 30 seconds while Windows decides that there is "Limited or No Connectivity". The error then sticks around for about 30 seconds before you get DHCP'd by the main router and things will work as normal.
However, it takes forever to get DHCP'd and what ends up happening is Wireless Clients tend to jump ship when they shouldn't be jumping ship. DHCP is also slow on a wired connection as well, but there generally is no reconnecting required as the users wired are generally always connected.
Any ideas as to why DHCPing takes a while? Everything else works fine as intended such as Web Browsing, Skype, etc. QoS, and Bandwidth Limiter is setup on the 192.168.1.1 router which works fine as it's the default gateway of everything.