Dial up connection : logon/password not recognized

[Charles Zingeline]

I am trying to set up a Win2000 machine to connect to an ISP. And am VERY
frustrated.

The connection to the ISP is always made. But the logon and/or password are
never accepted, always rejected with a message saying that either the logon
or password is invalid. I KNOW both are valid!

The tech people of the ISP assure me that the account is alive and well. And
I agree.

The office where I'm trying to do this also has a Win98 machine. This
computer can dial in and logon in to the same account just fine. This is
done at least once a day, and works very well.

The idea is to have the two computers in the small office use the same
telephone line on time-sharing basis; this matches the needs and schedules
of the office people.

The Knowledge Base at MS hasn't helped with this problem, where the Win2000
account seems to set up okay but doesn't make the logon connection. Nor have
a couple Win2000 books helped. I appear to be doing everything right.

When I was putting together the Win2000 machine on my home workbench, I had
the same problem of a failed logon. Now that the machine is in the client's
office, the problem continues. And the second machine is needed very soon.

What could cause this non-recognition of the logon and/or password? What can
I do to fix the problem?

I've tried adjusting many parameters of the dial-up account setup, but
nothing works.

Thanks for advice and direction.

Charlie

 

[Guest]

Charlie
It looks like your Windows 2000 computer may have some hardware issues. Can ANY dial-up accounts authenticate from that machine? Check your modem.

Pete Choppin


----- Charles Zingeline wrote: -----

I am trying to set up a Win2000 machine to connect to an ISP. And am VERY
frustrated.

The connection to the ISP is always made. But the logon and/or password are
never accepted, always rejected with a message saying that either the logon
or password is invalid. I KNOW both are valid!

The tech people of the ISP assure me that the account is alive and well. And
I agree.

The office where I'm trying to do this also has a Win98 machine. This
computer can dial in and logon in to the same account just fine. This is
done at least once a day, and works very well.

The idea is to have the two computers in the small office use the same
telephone line on time-sharing basis; this matches the needs and schedules
of the office people.

The Knowledge Base at MS hasn't helped with this problem, where the Win2000
account seems to set up okay but doesn't make the logon connection. Nor have
a couple Win2000 books helped. I appear to be doing everything right.

When I was putting together the Win2000 machine on my home workbench, I had
the same problem of a failed logon. Now that the machine is in the client's
office, the problem continues. And the second machine is needed very soon.

What could cause this non-recognition of the logon and/or password? What can
I do to fix the problem?

I've tried adjusting many parameters of the dial-up account setup, but
nothing works.

Thanks for advice and direction.

Charlie

 

[Mike D]

Not knowing your ISP, I can't be sure that this applies,
and may be stating the obvious. However, when hooking up
to my ISP via dialup, I have to use an entirely different
logon/password than the ones that I use to access email.
The required info was saved to my computer when I signed
up, but isn't in a very obvious spot. Hope this helps.

-----Original Message-----
Charlie
It looks like your Windows 2000 computer may have some

hardware issues. Can ANY dial-up accounts authenticate
from that machine? Check your modem.

 

[Bob I]

Double check that you have the same "Error correction and compression
settings" on the Win2000 modem that you have on the Windows 98 modem.

 

[Charles Zingeline]

The problem is solved. Windows 2000 can now logon and verify okay.

My ISP had published incorrect information. And tech support had given me
the same bad information over the telephone. It took a trip with the
computer to a more advanced tech person at the ISP to recognize and fix the
problem - which he did in 10 minutes. Makes one wonder.....

Thanks for your interest and help.

Charlie