I came across this, any help?
Also some USB modems have this problem.

In reply to:

---

Error 734: The PPP link control protocol was terminated.



This error is generally caused by you using the wrong username or password. The "Include Windows logon domain" check box is selected or the "Require secured password" setting is selected.

FIX 1:

Confirm Username and Password or renter them before connecting. Check that Caps etc are not on. Most logins are case sensitive.

FIX 2:

Click "Start", point to "Connect To", and then click your dial-up connection.

Click "Properties", and then click the "Options" tab.

Click to clear the "Include Windows logon domain" check box (if it is selected), and then click OK.

FIX 3:

Click "Start", point to "Connect To", and then click your dial-up connection.

In the "Connect" dialog box, click "Properties".

Click the "Security" tab.

Under "Security options", click "Allow unsecured password" in the "Validate my identity as follows" box, and then click "OK".

---

Edited by deleted (Tue 07-Nov-06 19:49:38)

I have been having the same problem. It took my 1.5 hours to connect on Sunday evening and again 16 attempts to get logged on tonight. Getting the same 718 and 734 error messages. This is becoming very annoying. I have checked with a few friends in the area and they are getting connected to their ISPs no problem (not IDNET) so it seems unlikely that its a BT problem.

Error 718 would appear to be a BT problem- see my post here.

Dunno about 734...

The authentication errors are said to have been cleared on 1st/2nd November, if you look at the full list of BT MSO reports here, Bill.

Browsing through the forums, there don't appear to be many reports of this phenomenon from other ISPs' customers.

I have been considering migration to IDNet, but this ongoing issue is encouraging me to hang on to my MAC at the moment.

Yes, I'm aware of the date, but it seems BT haven't yet got it sorted. See posts here et seq

Yes, thanks, Bill but, again, these appear to all be related to IDNet users, which is no consolation or encouragement to a potential migratee.

The second post in that thread I linked to (this one) indicated that other ISPs were also having problems. I don't know which, I haven't looked, perhaps you'd care to ask Nerval yourself?

The fourth post (here) confirmed that it's a BT problem- Miriam is one of the main CS people at IDNet, and what she says, I believe.

What more do you want?

In reply to:

---

What more do you want?

---

Call me wary after over-exposure to PlusNet's 'spin machine' but it appears odd that the issue is not being widely reported (other than during the initial MSO period) by those who use other ISPs.

Fair enough, and I apologise if I came over as a bit snappy....

TBH, I think part of the problem may be that so little ever goes wrong with this lot that a few disconnects (and it does seem to be only a few users) becomes a major catastrophe that wouldn't get even a passing comment with many other ISPs.

And I'm not spinning, I mean that!

Thanks Bill, I'll keep a watching brief, as I have a week or so before I need to commit, but IDNet certainly looks like becoming my next ISP.