kraftee wrote:
> Ben wrote:
>
>>P H wrote:
>>
>>>You should also be able to connect with: bt_test_user@ (your ISP
>>>domain) which will prove the fault into your ISP if you can connect
>>>with it, but not with your username/password.
>>>
>>>Phill H
>>>
>>>
>>
>>Yes, im aware of that. No, it doesnt connect either!
>>
>>I just dont believe that im not activated when it syncs and connects
>>with bt_test@startup_domain
>>
>>Ben (mad!)
>
>
> bt_test will connect on any ip-stream port, but if the port is not
> configured for your account (in doing so routed for your ISP) you are up the
> creek & can't do anything.
>
Exactly what I thought, however, BTw state
"They can connect on the bt test page as the frames were not recovered
on the adsl cease. Not recovering the frame is standard on cease &
provides. The linecards are still there but the ports and radius
connections are gone. Because the ports etc were recovered the line is
connecting to the test page rather than a domain."
And are citing a capacity issue at the exchange (ports?) as the reason
for a delay until the 18th (Again!)
Now, if Im connected to a port, but not a configured one, surely
capacity has nothing to do with it as it just requires a config and
RADIUS setup?
> The only thing you do know from what you're reporting is that you are
> connected to an active port on a DSLAM at your local exchange...
>
Thats what I thought, BTw however do not agree
Ben