DUN::How to stop password blanking on 691 error?

[doofus]

Hello All!

I'm just going to ask this peremptory question and people can totally
ignore it if they choose.

OS: Win2k, sp2 (IE 5.0)

Is there any way to stop DUN from blanking out the password on a 691
error (username/password invalid)? It has the consequence that a redial
will always fail even when the problem is at the ISP end, as it has been
for me repeatedly over the last couple of weeks.

Alternatively, stepping back a peg or two, are there any windows
diallers out there which could be run in batch mode and which give the
user a tad more control over these things.

best, doofus

 

[Ritchie]

Alternatively, stepping back a peg or two, are there any windows
diallers out there which could be run in batch mode and which give the
user a tad more control over these things.

Maybe you could try the built-in dialer, RASDIAL. It accepts a
username and password on the commandline:-

c:\>rasdial/?
USAGE:
rasdial entryname [username [password|*]] [/DOMAIN:domain]
[/PHONEhonenumber] [/CALLBACK:callbacknumber]
[/PHONEBOOKhonebookfile] [/PREFIXSUFFIX]

rasdial [entryname] /DISCONNECT

 

[doofus]

Maybe you could try the built-in dialer, RASDIAL. It accepts a
username and password on the commandline:-

[..]

Thanks, Ritchie. That's a great answer and this is a great group!

I'm off to have a look at it. Thanks.

 

[doofus]

Maybe you could try the built-in dialer, RASDIAL. It accepts a
username and password on the commandline:-

[..]

Just for the record. That works a charm. RASDIAL optionally uses the
password provided on the command line and everything connected up
brilliantly.

This has been one of my more successful adventures onto usenet news.

A big thanks to Mr. Ritchie from Dr. Doofus. ;-)