Training in terms of routers like yours is referring to the ADSL handshaking that occurs when you switch the ADSL modem, and it is attempting to sync with the hardware at the telephone exchange.

You are confusing the DLM training period with the standard sync process

Gateway inside the modem yup - according to its GUI and if I SSH into it as well. I figured if I could get the modem to ping smthg on the net that would at least narrow the problem down.

If you take the IP address given to the WAN interface and do a reverse DNS lookup (using another connection) what does it reveal.

If this is old fashioned IPStream it should say BT Central Plus.

Your inability to ping makes me think that while authentication is working, it is really failing and dropping you at a walled garden. The lack of detail such as IP address, gateway info makes it very much guesswork for people trying to help you.

At end of the day what do you want to achieve? Is this DLink proving worth the effort?

Thanks again. I'll give that a go and see what comes up with it and get back to you.

How much detail would you like re IP address etc? Wasnt sure how much was safe to publicly give.

Probably not worth the effort - but its one of those started so I'll finish type of things really now. I'm a stubborn swine!!

ping the WAN side of your router with http://tools.pingdom.com/ping/
your router may have disabled WAN side ping.

if it's a dynamic IP address who cares if you publish it, we could find it by scanning BT's allocated blocks

I forget, can you actually access th einternet ?

does nslookup www.bbc.co.uk give a sane answer ?

Hopefully I'll manage to answer all the questions here.

Before unpluggin the Hub I checked the reverse DNS and it came back with BTCentralPlus. This was on an IP addy starting 86.156. The new modem comes up with 86.151 but also on BTCentralPlus.

The default gateway for each is the same (217.47.207.58) and the DNS are the same as well. (primary being 217.32.171.21).

Subnet is 255.255.255.255, I can't check that on the Hub though so not sure if its the same.

Tried to ping my Hub from the site given but all the packets were lost but traceroute provided a more successful run. I tried the same on the new modem and the result was almost exactly the same. One tiny difference in an IP half way down the list but otherwise intact.

And allegedly I am connected to the net but to ping anything outside my four walls is futile - even the default gateway or DNS.

Thanks for all your time so far guys.

In reply to a post by Anonymous:

And allegedly I am connected to the net but to ping anything outside my four walls is futile

Due to the netmask being 255.255.255.255. Try reconnecting the Hub and seeing what the netmask should be.

In reply to a post by BatBoy:

In reply to a post by Anonymous:

And allegedly I am connected to the net but to ping anything outside my four walls is futile

Due to the netmask being 255.255.255.255. Try reconnecting the Hub and seeing what the netmask should be.

Unfortunately I can't see any way to check the netmask on the Hub itself and it wont take SSH / telnet to work it out.

Subnet mask of 255.255.255.255 is not uncommon for a single IP allocation - think about it.

Everything is pointing towards the IP being fine, and something simple like NAT is disabled or a firewall is running on the DLink.

Has this modem being known to work for sure on any broadband connection?

It means only packets addressed to 217.47.207.58 will be sent.