"steve" <(E-Mail Removed)> wrote in message
news:ba270b75-9f83-4a14-a0be-(E-Mail Removed)...
>>> I have seen similar problems when multiple routers were set for the same
>>> address. If say the more than one router is using the IP address of
>>> 192.168.1.1 then more than one might be trying to respond to your LAN
>>> connection request causing what appears to be colisions.
>>> Verify each wireless router is set for different subnets like
>>> 192.168.1.xxx, 192.168.2.xxx, etc.
>>>Well they are all different IP's eg different host numbers, but not
>>>subnets. 1.200 , 1.201 , 1.203
>While it would be an intersting test to change the subnet, It should
>work with the same subnet. I also am not sure if I change the subnet
>Im not sure I will be able to connect to the router web page from say
>192.168.1.10 to 192.168.0.200.
I agree that being all on the same subnet should not cause a problem as long
as the only one router is supplying ALL DHCP IP's.
You have most likely already done this, if not then verify the DHCP IP
address of the wireless PC you are testing from. First verify that the
reported problem is occurring from the PC under test. Then change the IP
address of that PC (temporarily) from DHCP to a fixed IP in the range
assigned to but not being used by your routers (having first pinged the
fixed IP you want to use to verify nothing responds. True not all devices
will or can respond to a ping but it's a start). Then from that PC try
pinging it's old DHCP address and see if something responds, provided your
PC's and any firewalls are not set to block pings. If you did get a ping
response then more than one router is assigning DHCP values or you have a
mixture of fixed IP and DHCP devices trying to use the same IP range. We
had one lab that would constantly program their stuff using the "ping test
for an unused IP value", then assign a fixed address to the device being
tested. We finally had to stick that lab on it's own subnet. One hopes for
no response to the old address but verify by trying to ping one of the other
wireless PC's elsewhere at the plant to verify the firewalls are not just
blocking pings. It might also help if you do your testing when the most
PC's are using the network. More PC powered on would mean more DHCH values
in play.
Some routers are factory set to issue DHCP values on the wireless side even
if the wired side has it disabled. If more than one PC connected wireless
using the same IP address on a different wireless router you might see what
you are describing. The better routers let you assign a range if DHCP
values on the wireless side from a common pool. Like router 1 can use
xx.xx.xx.1-25, router 2 is set for xx.xx.xx.26-51, etc until you run out of
values or routers.
As for the connecting from various subnet'd routers, you would most likely
need to load a few static route entries in the main router allowing traffic
to go from one subnet to another. If the slave routers are daisy chained to
each other then individual routers would also need a few static routes added
to them so they would know where it's possible to send data to.
One last thought, are all of the wireless routers are set to use the same
channel number? Depending on how close the wireless routers are to each
other they need to be set to individual channel numbers so as to not cause
interference.
|
Similar Threads
Linear Mode
