Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[j0hn]

Then it's pointless trying all the different WAN settings as none will work without sync.
Try getting sync 1st.
Have you specified the ADSL modulation type? What options are available on the DSL settings page?

[DaleLamar]

Are you actually syncing to the DSLAM? You mentioned in the 1st post that the ADSL light is flashing twice. I've no idea how that particular model works or shows sync, but without a successful sync you won't get any WAN connection.

No, it's not syncing to the DSLAM; that's the problem.

It does look like it's the DSL link that's not being established. I think the logs indicate it detects the DSLAM, but fails at some stage before fully establishing the DSL link.

That's right: the link is not being established. Hence, no sync to the DSLAM.

Yesterday, the A&A chap was monitoring as I was trying to connect to their test account. Afterwards, he said: "NO PPP attempts to us, odd."

[j0hn]

Yes changing any the WAN settings will make absolutely no difference till you get sync. Concentrate on the DSL settings.
What DSL modulation does your other modem use? ADSL/ADSL2/ADSL2+?

Try specifically setting this rather than choosing automatic. What other DSL settings are on that same page?

edit: it's under Network > DSL settings.
Try a specific modulation rather than Auto sync up.
Try unchecking SRA also.

[DaleLamar]

Yes changing any the WAN settings will make absolutely no difference till you get sync. Concentrate on the DSL settings.
What DSL modulation does your other modem use? ADSL/ADSL2/ADSL2+?

Try specifically setting this rather than choosing automatic. What other DSL settings are on that same page?

My other (Netgear DG834G v4) modem has the DSL modulation settings you mentioned; it is set to Auto.

I've tried all the DSL settings in the TP-Link router.

[j0hn]

When synced the Netgear should show you which modulation you are using on the Status/log page.
I edited my post above with more to try.

[d2d4j]

[j0hn]

It can't be the rj11 or the Netgear wouldn't sync with the cable. Only 1 pair in the rj11 cable is actually used. If they were on the wrong pins then the Netgear would not sync. They both use the same pins.

[DaleLamar]

[kitz]

I've just noticed you appended a log file in one of your later posts.  The log file is a bit odd, but it appears to be looping through training ok and the furthest its getting is PPP0 LCP confReq which is with the BTw RAS.  Its at this point things are failing and it appears to be having difficultly setting up PPP.
You should after that get a CHAP challenge so the BTw RADIUS can set up the L2TP tunnel to the ISP.

Definitely make sure that you are not putting in a static IP info as this can and often does confuse the BTw RADIUS... as its the ISP RADIUS which verifies the PPP login and at this point dishes out the IP.  I think you said in one of your posts that idNet said they could see no trace of you attempting to connect to their RADIUS. 

In theory if the BTw RAS can't connect you to your ISP, it should at this point allocate one of its own [internal] dynamic IPs which will just give you access as far as the BTw backhaul for performing certain diagnostics.

Do you get anything at all on this page from the web GUI
http://wiki.kitz.co.uk/index.php/TD-W9980_Status

[ejs]

When the WAN connection is configured as "always on", the TP-Link will keep trying to bring up the PPP connection regardless of the status of the DSL link. The PPP messages in the log are a red herring. The TP-Link log would contain "xDSL Enter SHOWTIME!!" if it had succeeded in establishing the DSL link.

[kitz]

Ah right cheers.  When I said odd,  I wondered why it was leaving showtime, without it showing in the log and thought perhaps it was a logging issue...  and why I wanted to know what showed on the status page, so we knew for certain if it was getting any sync.

Incidentally I notice there is a post on the PN forums of what appears to be similar issue on ADSL.   The EU never got to the bottom of it and RMA'd the modem.
https://community.plus.net/t5/Broadband/Problems-with-TP-Link-TD-W9980-on-ADSL/td-p/1290022

[DaleLamar]

I've just noticed you appended a log file in one of your later posts.  The log file is a bit odd, but it appears to be looping through training ok and the furthest its getting is PPP0 LCP confReq which is with the BTw RAS.  Its at this point things are failing and it appears to be having difficultly setting up PPP.
You should after that get a CHAP challenge so the BTw RADIUS can set up the L2TP tunnel to the ISP.

Definitely make sure that you are not putting in a static IP info as this can and often does confuse the BTw RADIUS... as its the ISP RADIUS which verifies the PPP login and at this point dishes out the IP.  I think you said in one of your posts that idNet said they could see no trace of you attempting to connect to their RADIUS. 

In theory if the BTw RAS can't connect you to your ISP, it should at this point allocate one of its own [internal] dynamic IPs which will just give you access as far as the BTw backhaul for performing certain diagnostics.

Do you get anything at all on this page from the web GUI
http://wiki.kitz.co.uk/index.php/TD-W9980_Status

Thanks for the information and advice.

It was A&A, using their test account. But yes, their chap said he couldn't see any PPP attempts.

The status page never shows any connection information, just 'initialising', then 'disconnected'.

Cheers.

[j0hn]

As ejs explained the references to PPP in the log are a red herring.
You need to try get sync 1st. Try each of the DSL modulation available, with SRA unchecked. I believe it's Annex A although happy to be corrected there.