GoodRevrnd
Diamond Member
The setup (sorry for the bad diagram):
DSL -> Sonicwall SOHO2 -> Switch -> Desktop Computers
....................................................... |_> Linksys WAP45G -> Wireless Laptops
The Sonicwall SOHO2 is configured to hand out IP addresses by DHCP on the range 10.160.68.111-.120. A static entry has been made with the Linksys WAP45G's LAN MAC address at 10.160.68.125.
The Linksys WAP45G has a default IP address of 192.168.1.245. We use the setup disk to reconfigure the IP to 10.160.68.125. From this point we can log into it with the web browser and configure the WAP's LAN gateway from the default 192.168.1.1 to 10.160.68.100 (the Sonicwall). This should ideally have the WAP at a static IP so we always know where to log in to it in case any changes ever need to be made and it just makes more sense for server type stuff to have static addresses.
Problem:
As soon as the gateway is changed the WAP goes haywire. The laptop has no access to the internet and receives a bizzare IP address. Neither the laptop nor a computer below the Sonicwall is able to ping or log into the WAP. The configuration utility also cannot detect the WAP. What is the problem?
Semi-unrelated Question:
The laptops sometimes have a tendency to want to connect to a neighbor's WAP. Is there a way in the windows wireless detector to block out that specific WAP or do I just need to add ours to the preferred list and hope the other one doesn't get assigned accidentally?
DSL -> Sonicwall SOHO2 -> Switch -> Desktop Computers
....................................................... |_> Linksys WAP45G -> Wireless Laptops
The Sonicwall SOHO2 is configured to hand out IP addresses by DHCP on the range 10.160.68.111-.120. A static entry has been made with the Linksys WAP45G's LAN MAC address at 10.160.68.125.
The Linksys WAP45G has a default IP address of 192.168.1.245. We use the setup disk to reconfigure the IP to 10.160.68.125. From this point we can log into it with the web browser and configure the WAP's LAN gateway from the default 192.168.1.1 to 10.160.68.100 (the Sonicwall). This should ideally have the WAP at a static IP so we always know where to log in to it in case any changes ever need to be made and it just makes more sense for server type stuff to have static addresses.
Problem:
As soon as the gateway is changed the WAP goes haywire. The laptop has no access to the internet and receives a bizzare IP address. Neither the laptop nor a computer below the Sonicwall is able to ping or log into the WAP. The configuration utility also cannot detect the WAP. What is the problem?
Semi-unrelated Question:
The laptops sometimes have a tendency to want to connect to a neighbor's WAP. Is there a way in the windows wireless detector to block out that specific WAP or do I just need to add ours to the preferred list and hope the other one doesn't get assigned accidentally?
