Was this sorted out eventually and the fault identified? Did iDNet reply either via phone or email?

if there's a quick way that might get rid of a problem it's almost always worth trying it first,

unless that has an effect like 30 other users [perhaps of disparate isp's] finding their line has dropped and reconnected.

In reply to a post by Tacitus:

Was this sorted out eventually and the fault identified? Did iDNet reply either via phone or email?

The OP got a call later the same evening:

http://forums.thinkbroadband.com/idnet/t/3994571-ftt...

but I don't know the outcome.

Ok all sorted now. IDnet arrange for BT engineer, first thing Monday morning (8am), however the next engineer slot was Tuesday .

Engineer arrived 8am, tried a new modem, but that didn't work. So I went on to explain to him that originally when I had the install done, I had two lift had shifts, originally port 71 to 51 then finally to port 1.

The original engineer found that port 50 on-wards were not working, so they put me on port 1. Over the weekend there was some sort of reset, and because my port details were not updated port 1 was shut down.

Finally got it all sorted, but I think remembering what happens originally helped a lot.

The engineer was great as he agreed there was mis-communication and that the details had not been updated. Its all sorted now

That's good to hear

But once again, it's a pity you had to wait several days for an engineer call-out to fix a problem that could have been fixed remotely in a few minutes if BT had decent lines of communication available to both ISPs and end users

Or even if BT just had decent lines of communication between departments as well.

In reply to a post by billford:

The OP got a call later the same evening:

Thanks Bill, I missed that one. Looks as though all is now well

where are you as this rings a bell?

Ilford seven kings off green lane