Can't Create Dial-Up Connection/Dimmed out

[Guest]

Hi there,

When I go into the Network Connection Wizard on Windows XP Pro W/ SP2 I can
get as far as the screen where it gives an option to pick Dial-up Connection,
create a broadband connection that requires a user name or password PPPoE
Network connection, and a third network option that is create a broadband
connection that is always on. Both the Dial-Up Option and the PPPoE option
are greyed out (dimmed) and can't be selected. I have done some research on
this and have followed the instructions on Microsofts website as well as some
other sites that included registry edits etc. I will note that this notebook
started with SP1 and I have since upgraded it to SP2. I did remove the
telephony reg key as per Microsofts website and then performed a
repair/upgrade install of windows xp pro. This did not help in the
slightest. Does anyone else have any ideas? Any other registry edits I
could perform? Thanks.

-Dave

 

[Chuck]

Hi there,

When I go into the Network Connection Wizard on Windows XP Pro W/ SP2 I can
get as far as the screen where it gives an option to pick Dial-up Connection,
create a broadband connection that requires a user name or password PPPoE
Network connection, and a third network option that is create a broadband
connection that is always on. Both the Dial-Up Option and the PPPoE option
are greyed out (dimmed) and can't be selected. I have done some research on
this and have followed the instructions on Microsofts website as well as some
other sites that included registry edits etc. I will note that this notebook
started with SP1 and I have since upgraded it to SP2. I did remove the
telephony reg key as per Microsofts website and then performed a
repair/upgrade install of windows xp pro. This did not help in the
slightest. Does anyone else have any ideas? Any other registry edits I
could perform? Thanks.

-Dave

Dave,

You mentioned having done registry edits specified on some web sites, with no
detail, then ask for more registry edits.

What type of Internet service do you have, and how is everything physically
connected?

Did you read this article?
<http://nitecruzr.blogspot.com/2005/11/lost-ability-to-create-new-network.html>
http://nitecruzr.blogspot.com/2005/11/lost-ability-to-create-new-network.html

 

[Guest]

Thanks for the timely reply, Chuck, The link didn't lead to anything I hadn't
seen before. But I did notice something on the Microsoft site that it linked
to that I may have overlooked. I will try that in the morning and will post
back on the results as well as more details on the sites I visited as well as
other tricks I have tried. Thanks.

-Dave

 

[Guest]

Alright, Chuck, I did get the dimmed stuff to light up again, it was the
services that were stopped that should have been started. I got those all
fixed and I could finally create accounts. It also brought back all the
accounts that had previously been there as well. However, the next problem
is that whenever I try to dial-up to either our ISP or our client's ISP, you
can here it dial and the modem is fine, but as it goes to check user name and
password, it comes back with an Error 720. I know the user name and
passwords are correct and after researching the Error 720 I saw that
sometimes a winsock error can cause this, which doesn't make sense in this
scenario as I can hook up to our wireless network and surf online fine.
However I did do the Winsock fixes which didn't make a difference. Now, I
will write down which protocols and etc. are being used by the dial-up
connection and include them here: Network Monitor Driver, Internet Protocol
(TCP/IP), and QOS Packet Scheduler are all installed and checked. Unchecked
protocols include NWLINK IPX/SPX/NetBIOS compatible protocol, File and
Printer Sharing for Microsoft Networks, and Client for Microsoft Networks.
If any of this rings a bell, please let me know. Thanks for all your time.

-Dave

 

[Chuck]

Alright, Chuck, I did get the dimmed stuff to light up again, it was the
services that were stopped that should have been started. I got those all
fixed and I could finally create accounts. It also brought back all the
accounts that had previously been there as well. However, the next problem
is that whenever I try to dial-up to either our ISP or our client's ISP, you
can here it dial and the modem is fine, but as it goes to check user name and
password, it comes back with an Error 720. I know the user name and
passwords are correct and after researching the Error 720 I saw that
sometimes a winsock error can cause this, which doesn't make sense in this
scenario as I can hook up to our wireless network and surf online fine.
However I did do the Winsock fixes which didn't make a difference. Now, I
will write down which protocols and etc. are being used by the dial-up
connection and include them here: Network Monitor Driver, Internet Protocol
(TCP/IP), and QOS Packet Scheduler are all installed and checked. Unchecked
protocols include NWLINK IPX/SPX/NetBIOS compatible protocol, File and
Printer Sharing for Microsoft Networks, and Client for Microsoft Networks.
If any of this rings a bell, please let me know. Thanks for all your time.

An "Error 720" sounds like an authentication error. It's been a while since I
had to deal with that, but you might want to work with your ISP. When I saw
that, and I know I had the user name and password right, it would be a problem
with the Radius server, or the DNS pointing to the Radius server.

You might want to consider getting an external modem, and a router to manage the
modem. That eliminates the LSP / Winsock issue.
<http://nitecruzr.blogspot.com/2005/05/sharing-your-dialup-internet-service.html>
http://nitecruzr.blogspot.com/2005/05/sharing-your-dialup-internet-service.html

BTW, do you perchance remember which service you had to restart? That would be
a good detail for me to add to my article. Details matter, so thanks if you can
help.

 

[Guest]

The services I had to restart were as follows: Telephony, Remote Access
Connection Manager, and Remote Access Auto Connection Manager. Will keep you
updated of this issue. Thanks.

-D