In reply to a post by vimto_girl:

Strange, but an explanation closer to home is more likely.

Did you configure these connections and devices before or are they new to you?
You swapped the router, but did you check with a clean 'naked' test device and configuration?

First time i had visited these clients. The BT ones were just bt hubs, bt home hubs two and three respectively. The problem was identical on both routers.

The problem was *not* caused by the connecting the devices. The problem was present on both wired and wireless, and other devices such as ipad etc. All devices were able to obtain ip addresses offered by router. The router itself would authenticate and acquire an external ip address. Tested from the test socket behind faceplate of mastersocket, filters swapped over.

This fault was replicated when i used my own test router, as ive mentioned. Customers own email address and also the generic [email protected] address used.

The information on my test router was as should be.

In what way could the explanation be closer to home?

That i wasnt able to test.

The person i saw on fri with the problem got a ring back from tier 2 support telling him that their is no problem and are sending him out a new router, despite him telling them alternative equipment had been tried.

In reply to a post by gazter:

In reply to a post by vimto_girl:

Strange, but an explanation closer to home is more likely.

Did you configure these connections and devices before or are they new to you?
You swapped the router, but did you check with a clean 'naked' test device and configuration?

First time i had visited these clients. The BT ones were just bt hubs, bt home hubs two and three respectively. The problem was identical on both routers.

The problem was *not* caused by the connecting the devices. The problem was present on both wired and wireless, and other devices such as ipad etc. All devices were able to obtain ip addresses offered by router. The router itself would authenticate and acquire an external ip address. Tested from the test socket behind faceplate of mastersocket, filters swapped over.

This fault was replicated when i used my own test router, as ive mentioned. Customers own email address and also the generic [email protected] address used.

The information on my test router was as should be.

In what way could the explanation be closer to home?

That was a lot of words to just say "no", you did not check with a test endpoint.

Being allocated a local IP means nothing - it does not mean you can exclude the endpoint to blame. You provide IT support so you should know that?

This is what I meant by closer to home - not a WAN side fault.

At the network level a tracert as I suggested ages ago might help to show if things are progressing or for example its a duff IP due to a radius timeout or similar.