![]() I had a few reasons, the main was that if my existing Airport Extreme failed I had a replacement on hand. I did consider replacing the Airport Express with the new 802.11n Airport Express, but having had two Expresses go on me, I decided to stump the extra cash and get an Airport Extreme. It got to the point where the Airport Express was failing on a daily basis and needed to be unplugged and plugged back in again. My main challenge was with my wireless Canon printer which was 802.11g and not been able to print was very annoying. As a result my 802.11g devices (such as the iPhone) wouldn’t be able to connect to the network and wouldn’t be able to stream video or download stuff. My old Airport Express, configured for legacy 802.11g devices, would often “disappear” from the network and even though it was still broadcasting, the Airport Express wouldn’t accept connections, nor could it be found via the Airport Admin Utility. Since I installed it, it has remained up and broadcasting (and accessible) without any problems. I am pleased with my new Airport Extreme which I recently installed to replace an unreliable old Airport Express. The issue with the DHCP is I think a separate but connected issue.Īs a result I am thinking about getting a new ADSL Modem/Router, so do you have any suggestions? With hindsight this was probably a mistake!Īfter blaming ADSL for my lost connections I am now basically convinced that the fault is not with ADSL, but may well be with the Modem/Router. So I went out and bought a Netgear ADSL Modem/Router from my local PCWorld. I did have one in the loft that I got out, but I think it was fried or just too old because I couldn’t get it to work or even configure it. When I moved back to ADSL I needed to get a new ADSL Modem/Router that supported PPPoA. When I had FTTC, as it uses PPPoE I was able to use my Apple Airport base station as the main router for the home network. ![]() The main problem I was having with the Airport base stations was that they couldn’t get an IP address from the router through DHCP and when I gave them a static IP address, the DNS didn’t work as expected. After reconfiguring the base stations and failing, I did a software reboot of the Netgear Router through the admin screen (as opposed to turning the thing off and back on again) and this time the Airport wireless base stations did sort themselves out. When we’ve had a power cut (or as I did the other day turn off the power to do some electrical work) it seems to be really problematic to get the three Apple Airport base stations I have back up and running. This is reinforced with the second thing I have noticed. Now this could be the connection, but I am slightly suspicious that the fault lies with the Netgear ADSL Modem/Router I am using rather than an issue with the connection itself. What I have noticed is two things, firstly, the connection goes down a lot more than it ever did on FTTC. My connection is certainly better than the one I had just before I moved onto FTTC. As a result I was booted back down to an ADSL internet connection. The exchange was upgraded for FTTC, but the cabinet I was connected to wasn’t part of the upgrade plan. I moved house in June and as a result my phone line was linked to a different cabinet, even though it was the same exchange. I have now been back on ADSL for six months and it’s not been a smooth ride. I have no idea why the ethernet port stopped working on the Airport Extreme. In the end I changed the ethernet port it was connected to on the Airport Extreme and guess what? Yes it all started working! So there was nothing wrong with the Airport Express, it was something else the ethernet port on the Airport Extreme. The reason is that there wasn’t a spare ethernet port on the router when I added the Airport Express to the network. The Airport Express isn’t directly connected to the router, it’s connected to an Airport Extreme which in turn is connected to the router. So it wasn’t getting an IP address from the router, so I rebooted the router. I was using a static IP address with the Airport Express, so I changed that to dynamic and the Airport Express ended up with a 169 IP address, a self-assigned address. So I did try and reboot the router and that didn’t work either. It was still broadcasting the SSID, so I first checked the wireless, devices connected to the Airport Express fine, however they got no internet access.įirst did a hard reboot of the Airport Express, that didn’t work. What I couldn’t fathom out was why it had stopped working, as I hadn’t done anything, I hadn’t done any updating, no re-configuration or changed any wires. ![]() Actually what happened was my TV which was connected to the Airport Express by wire couldn’t access the internet (so no BBC iPlayer for me then).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |