I'm not sure that does this go here, or the networking-forum. But this forum seems to have more posts regarding Airports.
I live in a pretty big house, and I have an Airport Extreme creating a WLAN. Unfortunately it's located in one extreme end of my house, and the signal does not carry to the other end of the house. Well, I have GigE running through the house, so I decided to use my old Airport Express (first-gen 802.11N, model no. A1264) on the opposite end of the house to extend the WLAN. The Airport Extreme is also connected to my GigE-network. So I plugged in the Express, and connected it's ethernet-jack to ethernet-port on the wall. And my network seemed to blow up.
I tried to configure the Express using Airport Utility, but it couldn't find the AP reliably. Neither could it find the Airport Extreme. And when it did, it asked for a password so it could read their config. Usually entering the password accomplished nothing, it would just ask for the password over and over again. Internet worked sometimes, but usually it did not.
At this point I also noticed that I could not connect to my server at all. Even if I connected via Ethernet.
I resetted the Express to factory settings, and Airport Utility found it, and guided me through the wizard. I set it to extend my existing network, I assigned a name to it, set it in bridge mode, and it then rebooted with the new settings... And same thing. No reliable network anymore.
I tried working on it a bit longer, but no luck. So I unplugged it, and my network went back to normal instantly. Huh?
One thing is that the Express has an old firmware, but I was unable to update it, since it would not download the new firmware.
Am I missing something here? Since the distance between the two APs is quite big, could the problem be that they do not have WLAN-connection to each other? They do have wired connection though (through my GigE-switch, to which my server and DSL-router is connected to). Do I need the latest Airport Express with the WAN port for this to work properly?
I live in a pretty big house, and I have an Airport Extreme creating a WLAN. Unfortunately it's located in one extreme end of my house, and the signal does not carry to the other end of the house. Well, I have GigE running through the house, so I decided to use my old Airport Express (first-gen 802.11N, model no. A1264) on the opposite end of the house to extend the WLAN. The Airport Extreme is also connected to my GigE-network. So I plugged in the Express, and connected it's ethernet-jack to ethernet-port on the wall. And my network seemed to blow up.
I tried to configure the Express using Airport Utility, but it couldn't find the AP reliably. Neither could it find the Airport Extreme. And when it did, it asked for a password so it could read their config. Usually entering the password accomplished nothing, it would just ask for the password over and over again. Internet worked sometimes, but usually it did not.
At this point I also noticed that I could not connect to my server at all. Even if I connected via Ethernet.
I resetted the Express to factory settings, and Airport Utility found it, and guided me through the wizard. I set it to extend my existing network, I assigned a name to it, set it in bridge mode, and it then rebooted with the new settings... And same thing. No reliable network anymore.
I tried working on it a bit longer, but no luck. So I unplugged it, and my network went back to normal instantly. Huh?
One thing is that the Express has an old firmware, but I was unable to update it, since it would not download the new firmware.
Am I missing something here? Since the distance between the two APs is quite big, could the problem be that they do not have WLAN-connection to each other? They do have wired connection though (through my GigE-switch, to which my server and DSL-router is connected to). Do I need the latest Airport Express with the WAN port for this to work properly?