Dial-up problem

[Sheng-Chi Huang]

Hi all,
Has anyone had this problem before?

Question 1:
In my Windows XP embedded system, the "Connect using a dial-up modem"
selection within the "New Connection Wizard" is grayed and disabled.
It seems that this was a common problem when SP1 came out
(http://www.jsiinc.com/SUBL/tip5800/rh5880.htm).

Based on the previous postings, I have also included the following
components to make sure that my RAS is properly set.
Connection Manager Runtime
Device: Multifunction
Dial-up Client for Windows
Dial-Up Networking Common Libraries
Dial-up Server for Windows
IP Router Monitor Library
Phone and Modem Control Panel
RAS Async Adapter
Remote Access Monitory
Standard 33600 bps Modem

Am I missing other required components? Is there a way to "enable"
the "Connect using a dial-up modem" selection ?


Question 2:
If I follow the home page, and delete ALL the subkeys in the following
registry, "Connect using a dial-up modem" becomes enabled.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP

Then I was able to make a new connection. However before my
connection performs the username and password verification, the
following error occured:
all devices connected
error 50: the request is not supported

What does this error mean?

Thank you.

 

[KM]

Sheng-Chi,

A few hints:
- Patch RasMan stuff with the latest:
http://www.microsoft.com/downloads/...75-0ca0-45c6-a897-7cebe89d02f7&DisplayLang=en

- Add TAPI related components. Particularly the "TAPI Performance DLL" component (I believe "Primitive: Tapi32"and "Telephony"
components are already in your configuration).
Also, add "System Event Notification Service (SENS)" component.

- Make sure that RasMan ("Remote Access Connection Manager") and TapiSrv ("Telephony") services are running at run time.

- Check out FBALog for RAS/TAPI related errors

- Create RasBook. You can do this at run time with a command like: "rasphone -f <path>\phonebook.pbk", where <path> is the path
you want the rasbook to be located. If this fixes you problem, you can wrap up this command to be run during FBA.

- Make sure you've got available COM ports (if you do Dial-up via COM)

- Learn about EAP APIs and registry settings: http://msdn.microsoft.com/library/en-us/eap/eap/eap_start_page.asp

Let us know if something from the list helps you.

 

[Sheng-Chi Huang]

Hi KM,
Thanks for the detailed response. Actually, our RAS service did not
start at all. When I manually start the service, I also got the
following error dialog:

----------------------------
Services
Could not start the Remove Access Connection Manager service on Local
Computer.
Error 50: The request is not supported.
----------------------------

Not sure exactly what this means though

I will try your sugesstions and report back. Again, thanks for the
great help!

 

[KM]

Sheng-Chi,

Somehow I missed you reply.
Well.. I suspected that the Rasman was not started at your runtime and that is why I sent you the list of different things to try.
I would suggest you to concentrate on the RASbook suggestion as it may cause the Rasman service start errors.

Also (in case nothing from the list helps you) you can debug the problem much easier now as you got a good repro steps.
Just launch Regmon (and Filemon) tool and monitor failed entries while you are running "net start Rasmon" command. That hsould tell
you what's missing from your runtime.

I am going to be out for a couple of weeks so won't be able to help you more. I hope you fix your issues.

 

[drlivingstone]

I just had the same error appear over the past couple of days.
Rebooting and dialing again seemed to work but dialing a second time
would produce the error. I downloaded Spybot S&D and loaded the latest
database. Ran it and immunized my computer. Upon reboot and finishing
the Spyware S&D upon next bootup the problem was gone. I'm not sure
which spyware culprit is the problem but one was. If you still have
this problem trying running Spybot and I bet the problem will go away
if you remove all spyware on your computer. Best of luck.