been messing with two MS MN-500 wireless router/ap's for a few days. everything works well with one exception:
if the mn500 configed as an AP (in bridge mode) is the only available, or strongest available signal the wireless pc/laptop wont get a useable ip address from the routers DHCP range (cable modem > wireless router > crossover to wireless router as WAP)
the ms user guide is slightly more than useless, for instance, it makes a good coaster for multiple glasses
how can i fix my problem? unpower the WAP and everything in range of the wireless router works without a hitch.
ive checked JackMDS links (great page by the way but am stumped on this IP thing.
ive thought about disabling SSID broadcasting on the WAP, which may solve the problem of just selecting the routers wireless network to get an ip, but thatll only work in range of the router and i need the extended range of an access point.
wireless router IP: 192.168.2.10
DHCP range: 192.168.2.100 - 192.168.2.150
WAP IP: 192.168.2.20
(in bridge mode the firewall, dhcp, and several other features are disabled)
like i said, if the router is the only/nearest wireless point, i get an ip fine, plug in the other WAP and can roam in its range without a problem.
WAP nearest/only signal, no IP or some default IP is used (i forget what it is, 167.x.x.x or something)
if i configure the WAP stuff manually (not just IP but DNS, gateway and the like) will that fix it? manual ips on the wireless enabled computers? should i just disable wireless access on the router (since, excepting rare cases, the WAP should provide sufficient wireless access)? i would think id get the same ip problem if i did this tho
i wont get to mess with it anymore til wednesday night some time, id appreciate any suggestions anyone could give on how i could get this little problem solved
thanks
if the mn500 configed as an AP (in bridge mode) is the only available, or strongest available signal the wireless pc/laptop wont get a useable ip address from the routers DHCP range (cable modem > wireless router > crossover to wireless router as WAP)
the ms user guide is slightly more than useless, for instance, it makes a good coaster for multiple glasses
how can i fix my problem? unpower the WAP and everything in range of the wireless router works without a hitch.
ive checked JackMDS links (great page by the way
but am stumped on this IP thing. ive thought about disabling SSID broadcasting on the WAP, which may solve the problem of just selecting the routers wireless network to get an ip, but thatll only work in range of the router and i need the extended range of an access point.
wireless router IP: 192.168.2.10
DHCP range: 192.168.2.100 - 192.168.2.150
WAP IP: 192.168.2.20
(in bridge mode the firewall, dhcp, and several other features are disabled)
like i said, if the router is the only/nearest wireless point, i get an ip fine, plug in the other WAP and can roam in its range without a problem.
WAP nearest/only signal, no IP or some default IP is used (i forget what it is, 167.x.x.x or something)
if i configure the WAP stuff manually (not just IP but DNS, gateway and the like) will that fix it? manual ips on the wireless enabled computers? should i just disable wireless access on the router (since, excepting rare cases, the WAP should provide sufficient wireless access)? i would think id get the same ip problem if i did this tho
i wont get to mess with it anymore til wednesday night some time, id appreciate any suggestions anyone could give on how i could get this little problem solved
thanks
Facebook
Twitter