Again, apologies if you already know this...revisiting the basics... And, I agree that it is odd that everything worked until you shut it all down, then powered it all back up. One very hard lesson I learned a long time ago was to take notes about the set up, including passwords, when piecing a network together. Otherwise you've either got to be a detective or have a very very good memory.
As someone else already said, any subnet can only have ONE DHCP server, unless you want some very interesting and unfun problems. But, generally, for a wireless access point to serve its purpose on the network, the network MUST have at least one DHCP server functioning. (That is unless you also manually set the IP on each wireless device that connects to the WAP, which would work fine, but be a hassle.) That's why my first question was whether you're using static IPs or a DHCP server. Alternatively, you can set each device's IP statically (manually) being careful to a) not use the same IP twice b) use the same subnet on each (the first three octets of the IP) c) use the same subnet mask on each device (and, of course, the correct gateway IP and valid DNS server addresses) You can mix static IP devices on a subnet with DHCP-dependents (non-static IP), as long as the DHCP server is serving up IPs and subnet masks that match the static IP device's settings (assuming you want everything to see and talk to each other.) As for WAPs, as long as the WAP is happy with the gateway (same subnet, same subnet mask) then the WAP will be able to accept connections and route to the Internet. If (a big jump of logic) your WAPs have reset to factory defaults, is it possible that you had been using them in repeater mode and not as separate WAPs? A repeater acts like a WAP, but it just accepts data and then passes it on to another WAP that, ultimately, is connected by hardwire to a switch/hub and ultimately a gateway device (DSL/cable modem.) I've seen multiple WAPs set up both ways, one or more devices in repeater mode with one WAP, or multiple WAPs each connected to the gateway. Many WAPs are able to serve as DHCP servers and assign an IP to the wireless device that connects to it. But, again, you only want one DHCP server for your entire subnet (if a WAP gets a request for connection and needs an IP for the wireless device connecting, it will get the IP from the DHCP server and pass it through to the wireless device.) I think you're on the right track...get one device to work (power the other WAPs off) then connect each new device and deal with it as if it were brand new out of the box...reset it to factory defaults. What brand and model of WAPs are you using? Mike -------- Original Message -------- Subject: Re: [NF] Wireless network SYSFU From: Ken Kixmoeller (ProFox) <[email protected]> To: [email protected] Date: 2/8/2012 10:52 PM Thanks, Mike --- -- For one of the devices, the working WAP, the default IP is 192.168.0.227. I kept this one as the default. The test computer's IP is 192.168.0.104. The subnet mask for both is 255.255.255.0 -- At this point, I'd just like to see the Admin screen for any wireless device, just to affirm my sanity. As a reminder: 2 weeks ago, this all worked. I have successfully connected to and configured all of these devices, and they have been in-service a varying amount of time, the least of which was about 1 year. I just unplugged the router and a nearby switch. An hour later, I plugged them all back in. Chaos ensued. Ken On Wed, Feb 8, 2012 at 10:18 PM, Mike Copeland<[email protected]> wrote: > Don't forget that if you are connecting directly from a computer to the > WAP that you'll need to make sure both devices are on the same subnet. > > If your laptop (just a WAG what you're using for a computer to connect > to the WAP with) is set to get an IP and subnet mask from a DHCP server, > then you aren't getting anything from the WAP that would provide that. > You'll have to set the IP and subnet mask manually on the computer to > the same subnet, but a different IP, and the same subnet mask. > > (Apologies if you already know all this...) > > WAP defaults to: 192.168.1.1 (very common) with a subnet mask of > 255.255.255.0 > You need your laptop to be 192.168.1.2 or 192.168.1.3 (or anything other > than .1 but matching the 192.168.1. part) with a subnet mask of > 255.255.255.0 also. > > Then, if your WAP has crossover detection, you can use any network > cable...most newer WAPs do. If, though, your WAP does not detect and > adjust for crossover, then you'll need a cross over cable between the > two devices...or better, just any old cheap switch box. > > Mike > > -------- Original Message -------- > Subject: Re: [NF] Wireless network SYSFU > From: Ken Kixmoeller (ProFox)<[email protected]> > To: [email protected] > Date: 2/8/2012 10:08 PM > > Oh, how I hate hardware. Hate it, hate it, HATE it!! > > OK, got that out of my system. (Actually not, but let's proceed anyway.) > > Testing my theory that the WAPs have been reset and are operating with > the same IP addresses. Well, I can't test it. > > I hook up a computer directly to the WAP. Put in turn the default IP > and the IP I assigned into a browser (actually 2: FF& Chrome). > Nothing. Try to ping both IPs. Nothing ("Host is down"). Try another > device. This does not work even for the WAP that is f'ing *working*! > How many times have I done this before? Dozens? > > For the last 2 hours, I have been trying to communicate with 2 of > these devices. I can't even get them to acknowledge my existence. > (Yes, Ted, I tried a couple of different cables, too.) > > I hate computers. Hate them, hate them, hate them..... > > I'm going to take the dogs for a walk. That may save me from taking > these stupid devices and smashing them, stomping on them, and spitting > on them... > > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
