You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Airport Extreme And Dsl 300t
- Thread starter Dermody
- Start date
We don't like Ads much either, but they do help cover the costs of running the site. Please consider turning off your ad blocker. Thank you.
I'm betting you have an Airport Expess Basestation with the 6.2 firmware. Yes? If so then downgrade the firmware to 6.1.1. This should resolve your issue. Other users of the 300T in conjunction with an Airport Expess Basestation have also had this problem. Hopefully it will be resolved with a future update of the firmware (I have heard that 6.2 has a number of other issues as well). For now just stick with 6.1.1. You can get it from Apple's website here:
http://www.apple.com/support/downloads/airportexpressfirmware611formacosx.html
http://www.apple.com/support/downloads/airportexpressfirmware611formacosx.html
hank29europe
Registered
i noticed the advice given was for airpot express and you have extreme.
use v5.5.1 of firmware only on extreme.
go to www.zensupport.co.uk/knowledgebase/article.aspx?id=10156
this article explains explains how to set up the airport with the dsl 300t
use v5.5.1 of firmware only on extreme.
go to www.zensupport.co.uk/knowledgebase/article.aspx?id=10156
this article explains explains how to set up the airport with the dsl 300t
Tried a lot of combinations, and finally found the right solution, I think.
First dlink and airport wanted to be both dhcp and conflicts were welcome.
Then I deactivated the one of dlink, given the airport 192.168.1.2, but when distributing Ip(dhcp&nat) it wasn't possible with static ip's so other option range: 192.168.1.3-.1.200. But deconnections found place and I still don't understand why. Then tried to dlink dhcp and airport not. But the airport cannot act as a bridge, he WANTS an Ip, so again sometimes internet, sometimes not. meanwhile, the computers had a manual adress using dhcp. then tried dlink to give a range from .1.1 to .1.2 and airport .1.3 to .1.200 worked fine for half a day(DHCP only). Tried last with DHCP&NAT but the airport takes ip 192.168.1.1 and conflict with modem.
Last one I tried, and I had to do it first. The dsl act as a bridge and the airport enters login information to the modem to connect and dhcp/nat. for the moment, It works fine for a week already, but still waiting...
And their, the dsl acts as a real bridge, it asks no ip, nothing, so that was the best solution.
Hope it helped
If it can help my belgian friends, its for the full adsl connection
First dlink and airport wanted to be both dhcp and conflicts were welcome.
Then I deactivated the one of dlink, given the airport 192.168.1.2, but when distributing Ip(dhcp&nat) it wasn't possible with static ip's so other option range: 192.168.1.3-.1.200. But deconnections found place and I still don't understand why. Then tried to dlink dhcp and airport not. But the airport cannot act as a bridge, he WANTS an Ip, so again sometimes internet, sometimes not. meanwhile, the computers had a manual adress using dhcp. then tried dlink to give a range from .1.1 to .1.2 and airport .1.3 to .1.200 worked fine for half a day(DHCP only). Tried last with DHCP&NAT but the airport takes ip 192.168.1.1 and conflict with modem.
Last one I tried, and I had to do it first. The dsl act as a bridge and the airport enters login information to the modem to connect and dhcp/nat. for the moment, It works fine for a week already, but still waiting...
And their, the dsl acts as a real bridge, it asks no ip, nothing, so that was the best solution.
Hope it helped
If it can help my belgian friends, its for the full adsl connection