|
User #238809 3 posts
Participant
|
My mate has an AAPT ADSL1 account currently working with the default package modem. He has now purchased a Billion Wireless-G ADSL2 modem from another mate. I went round last night to set it up for him, getting settings from his old modem and AAPT support. We were told by support to use PPPoE but this didn't work. His old modem was PPPoA and this worked. So, by the end of the night I was stumped (and im in IT by the way.) We had all his account settings in the modem/router and were getting "connected" status for the ADSL connection We also had a connection to the router via Ethernet and/or wireless (which I also secured). No firewall settings have been put into the router so that shouldn't be an issue. BUT..... we couldn't connect to, or even ping anything last the modem. like i said, connection status is "connected" as far as the ADSL connection is concerened. So the PC's can talk to the router/modem...... The Modem can talk to the ISP....... But the traffic from the PC to the ISP is blocked at the modem ? ideas? (I did a tractrt to www.google.com and the modem is the ONLY ip address that returned data) |
posted 2008-Jul-22, 2pm AEST
edited 2008-Jul-22, 2pm AEST
|
|
User #179594 1008 posts
In the penalty box
|
I'd ring AAPT and check if you're logged in to their network... "Connected to ADSL" on some modems only means that there is ADSL sync... Make sure you have the @aapt.net.au on the end of your username... |
posted 2008-Jul-22, 4pm AEST
|
|
User #238809 3 posts
Participant
|
Thanks mate. Will try that too. We did have the wrong password for a while and it was giving us "auth_fail" on the modem config page and forcing a disconnect when we got the username and password right, that seemed to fix it BUT we had also changed other things as well knowing we get sync... I might force a bad password and see what it does. Got late last night... you know how it is ;) |
posted 2008-Jul-22, 4pm AEST
|
|
User #238809 3 posts
Participant
|
WEnt round to mates house again tonight and FIXED the problem. It is a model 7300G btw Did a firmware update and this fixed the issue Interestingly there were 2 updates. A and B A installed, but B failed But still, it works after update A so dont care about B ;) |
posted 2008-Jul-26, 11pm AEST
|