WinXP creates ISP Password!/will not connect

[Legendiva]

Need help with an XP DialUp Mystery:
Although I am Computer Consultant, experienced with setting up and troubleshooting DUN; I am not yet all that familiar with WinXP/XP Pro. My husband's brand new Laptop, running XP, has been coming up with a problem I have never seen before: it creates its own, very long ISP Password! ( This has been a consistent problem since first turning the Laptop on, and I first did the setup. Initially, I was able to work around this by deleting it and entering in the correct Password, and then connecting; but the 'long/wrong' PW would always return as soon as the Connection was closed!
Now, nothing I do will permit a Connection, with ANY number I have tested with.
( We are not part of a Network )

1) This happens in spite of Manual DUN settings ( including DNS Numbers ). Allows me to enter in all my info with no problem, but will not connect. When checked, the Password will always be its own long PW instead of mine.
2) I have tested with and without Disabling the 'Automatic Detection' option; no change.
3) I have tried to enter the Password on the Connection Window DURING the Connection attempt ( deleting the 'Click here to change saved Password' line ); still will not connect.
4) I have tried with 3 DialUp Numbers we currently use
( all are fine on other systems in the house ); none will work on the Laptop at this point.
5) I have deleted/rebooted and re-created new DUNS with the various numbers, one at a time. No change; still creates its own Password and will not connect.
6) Modem tests out as ok. Phone lines inside house, outside house are fine. No problem with ISP ( Earthlink ).
7) I have set Modem Logging.; with Logging done for Connection attempt as well as Modem Diagnostic results. Some very bizarre stuff, I've never encountered before.
Here are a few of the oddities:

This when trying to connect:

DSR is low while initializing the modem. Verify modem is turned on.
Waiting for a call.
Send: ATDT##########<cr>, Attempting to abort current command, Send: <cr>, Recv: <cr><lf>NO CARRIER<cr><lf>, Interpreted response: No Carrier, Hanging up the modem.

A sample of some of the odd Modem Diagnostic logging:

Call Setup Result: Data Answering signal detected
Multi-media mode: Data Only
DTE-DCE interface mode: Async data

V.34 INFO bit map: 0x03d33fa8
Don't know to format (0x00000020, 0x000000ff) for tag 0x2a4d3263

Transmit characters sent from DTE: 0
- Received characters sent to DTE: 0
- Transmit characters lost (data overrun errors from DTE): 0
- Received characters lost (data overrun errors to DTE): 0
- Transmit Frame count: 0
- Received Frame count: 0
- Transmit Frame error count: 0
- Received Frame error count: 0
- Termination Cause: Training Failed
- Call Waiting event count: 0
- Don't know to format (0x000000f5, 0x00000043) for tag 0x2a4d3263
- Don't know to format (0x000000f6, 0x00000047) for tag 0x2a4d3263
- Don't know to format (0x000000f7, 0x00000000) for tag 0x2a4d3263
- Don't know to format (0x000000f8, 0x00000000) for tag 0x2a4d3263
- Don't know to format (0x000000f9, 0x00000000) for tag 0x2a4d3263
- Don't know to format (0x000000fa, 0x00000000) for tag 0x2a4d3263
- Don't know to format (0x000000fb, 0x00000000) for tag 0x2a4d3263
- Don't know to format (0x000000fc, 0x00000000) for tag 0x2a4d3263
- Don't know to format (0x000000fd, 0x00000000) for tag 0x2a4d3263
- Don't know to format (0x000000fe, 0x00000000) for tag 0x2a4d3263

AT#CLS=? - COMMAND NOT SUPPORTED
TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x40)
TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
TSP(0000): Dropping Call
TSP Completing Async Operation(0x00010245) Status 0x00000000
TSP(0000): Closing Call

I just checked his XP Pro Desktop System ( which is currently set to do the 'Automatic Detection/Connection': no DNS numbers entered manually ); and VOILA! it has the same 'long/wrong' PW it created for itself!
So far, this one has been connecting without a problem. Exactly WHAT it is connecting to is anyone's guess. My Earthlink UserName, and one of my usual Earthlink Dialup Numbers is entered in; but it is NOT using my assigned Password to do the Connecting; which I have never seen to work! Modem Logging for this system does NOT show anything similar to the odd stuff the Laptop Modem Logging shows.


So, question #1:
How do I get XP and XP Pro to hold the correct PW?

And, question #2:
Any ideas on what is going on with the Laptop's inability to connect, and weird Modem Logging?



Legendiva
Deborah Cancel Computer Consulting

 

[Legendiva]

And it keeps getting weirder....
I noticed that in the DUN Connections I create( in any or all, usually but not each one each time, so far ) a small rectangular symbol appears in front of the area code of the numbers I have entered. I was not able to connect when this symbol was preceding the phone number. I tested by deleting it everywhere it appeared; and I was able to connect just fine!
BUT....a few hours later, when I fired it up again and tried to connect, the same 'no connect' with all 3 DUNS again!


Legendiva

 

[BruceDickson]

Hi LegenDiva, thanks for your competent post! I am having this same exact problem with XP home.

I see no further posts. Did you solve it? What did you learn?

Can you reply to bd222@juno.com with where I can learn more? Thanks so much for what you can assist with.

Bruce Dicskon, school teacher in L.A.

 

[BruceDickson]

Here's one answer

Did it solve things for you?

You are using Windows XP? If you are then that's the reason why the password APPEARS to change, it's not, it's Windows way of disguising passwords. So once you have entered it leave it even tho' it looks as if it's changed (although you may have to re-enter your password if it fails to log on, in which case it will be blank).

 

[jampes99]

This is normal behavior for Windows XP. A google search will lead you directly to this information. WinXP will insert up to 16 dots in place of the password so that onlookers will have a harder time guessing at your password. Windows 2000 Pro also does this. You should be able to connect to your ISP without having to retype the password each time. If you have to retype the password each time in order for it to connect, then you have a cache issue, which is separate from this post.

 

[Legendiva]

Thanks. I did locate the info on the 'disguising of password'. This wasn't always generating the 10-dot line; different dot pattern at times. The only thing I was able to isolate is the strange small rectangular symbol which appeared before the area code of the access numbers I had entered: if I removed it, I could connect. If I left it alone, I could not connect. I finally removed all DUNS and Modem, rebooted and let the system autodetect the modem afresh; then set up all the DUNS again. No weird little rectangular symbol this time. No problem. ( I haven't a clue as to what the little symbol was, or why it kept appearing. )
I like to hardcode my DUNS,, because of backbone and switching problems in this area with my ISP ( their suggestion ). I have still been unable to establish a connection via manual DUN settings with either the XP system or the XP Pro system; so far I have not been able to figure out exactly why.

Legendiva

 

[sixstrings4]

For: BruceDickson

I noticed that you have a Juno account and I know for sure that Juno will not allow you to connect via dun. They require that you connect using their software. If you try to connect using dun you will get an error, such as 691, even if your username and password is correct.