Hello everyone. I'm having some problems with a wireless network that's setup in a auditorium. Our layout is as follows: Internet Connection [Wired connection to] Wired Ethernet Router - 192.168.0.1 (Static IP to 10.xx.xx.xx) (Manually configured DNS) (Cloned MAC address) [Wired connection to] Wireless Access Point...............Computer (192.168.1.252)....................(10.xx.xx.xx) [Wireless connection to] Laptop............Laptop..........Laptop(far away) (192.168.0.xx)....(192.168.0.xx)..(192.168.0.xx) (Forgive the layout... Computing.net doesn't like excessive white space which makes the ASCII diagram I had set up all messed up) We have about 20 people or so try to connect to an access point. However, each person gets one of three problems: 1. They get "Limited or no connectivity" 2. They get connected, but immediately gets disconnected 3. They get connected for a period of time but sometimes are unable to connect to a page the first time around (like a person would go to Google, get a 404, go to Goggle again and it would pop up). I should note that these people are within range of the AP and are getting at least three bars according to Windows. We also had to change the channel the AP was broadcasting on. Apparently there is another network in the auditorium and our guess is there was some interference with that. The third error I think is just having too many people on the AP at one time trying to access something. As for the other two, I don't know. At one point this was all working. But now I'm getting calls about these problems. Interesting side note: I tried connecting and manually put in my IP and the DNS and was able to connect just fine with no dropouts. My guess might be that the laptops that are too far away are not getting a strong enough (or long enough) signal to get an IP from the router. But that wouldn't explain why people on stage would not be getting it... (I don't know if they are... I'm usually in the back where all the problems are cropping up) We just bought a range extender to possibly remedy this (one of our guys works inside a steel cage inside a concrete room). I've also suggested to these people to put in a manual IP and the proper DNS addresses when using this network. But then why wouldn't the router give out IP's? Or could it be the AP just not doing a good enough job? Finally, I should note that the only things we have adjusted on the devices is the MAC, IP, and DNS on the router (so it will actually connect to the internet properly) and the security and channel settings on the AP. If you have any possible information on this, or know of a forum topic that addressed this before, let me know soon! I keep getting called up for this and I hate going there without any possible fixes. Thanks again, Nick. P.s. If you need any additional information on the layout, I'll try my best. Keep in mind that I don't have quick access to the devices unless I go down there which takes a couple of hours.

Wired Ethernet Router - 192.168.0.1 (Static IP to 10.xx.xx.xx) I have one question. Where does the 10.x.x.x. come from if the subnet is 192.168.0.x ?

I should have gotten into that a little better... The Internet connection gives out IPs based on MAC addresses. All of them are 10.xx.xx.xx. So instead of having a computer plugged in, we set it up as follows: Internet Connection [Set up so that the router is 10.xx.xx.xx based on it having a specific MAC address (and a static IP to make sure we get the right one)] Wired Router [Using default IP for this side of 192.168.0.xx (router has an IP of 192.168.0.1)] Wired/Wireless Network Although thinking back on it... I don't remember if that other computer that's wired to the router was given a 10.xx.xx.xx or a 192.168.0.xx IP. I thought I saw it as 10.xx.xx.xx when I was down there troubleshooting. It could be that I'm remembering it when I was connected directly to the line (the line coming in and the router are in close proximity to each other but all have the same cables and go everywhere). It probably was 192.168.0.xx now that I think of it. Either that or the ISP has this weird thing with wired routers...

You issue appears to be ip addressing. 10.x.x.x can only be that of the wan port ip. No other pc or device should get a ip in that range except for the wan port on the router. "Wireless Access Point (192.168.1.252) This is also incorrect. I shoulod be in the 192.168.0.x subnet not the x.x.1.x subnet. Router's gateway for example would be 192.168.0.1 and the AP would be statically assigned also at x.x.x.2 The router would provide dhcp which will flow thru the AP. Imagine the power of knowing how to internet search http://www.lib.berkeley.edu/Teachin...

So instead of setting up two smaller networks, make it one big one. I think I see where that is going. Like I said, I did a lot of this out of the box. I only did some basic configuration and it looked like it worked (in fact it did for a while). I think I set the router IP stuff okay though. It's seen as 192.168.0.1 if you are on the network but it's able to access the internet properly (other IP's/MAC's don't allow access online). I just think I remember it wrong (a lot of this is coming from memory when I was there a few days ago and moved a lot of stuff around). I guess I'll head down there tomorrow and try it out and double check the router. Thanks a lot! Oh! If anyone else has a thought or idea (or just want to confirm it), by all means do so! The more information I have before I get there, the better my chances are of not getting called about this again... until something blows up. Ha ha.