Remote-access Guide

event id 20063 remote access

by Buddy Boyle Published 2 years ago Updated 1 year ago
image

Event Id: 20063: Source: Rasman: Description: Remote Access Connection Manager failed to start because the Point to Point Protocol failed to initialize. The network request is not supported. Event Information: According to Microsoft : CAUSE This problem occurs if both of the following conditions exist:

Event ID - 20063
Remote Access Connection Manager failed to start because the Point to Point Protocol failed to initialize. The network request is not supported. This problem occurs if both of the following conditions exist: You upgrade a Windows 2000 Service Pack 3 (SP3)-based computer to Windows 2000 SP4.

Full Answer

What are the RemoteAccess 20063 errors on bootup?

The host machine event viewer reports two RemoteAccess 20063 errors on bootup relating to Remote Access Connection Manager, Protocol engine not initiating, rasgreeng.dll and IKEv2. RACM, however, is running and set to auto as are the Remote Access Auto Connection Manager and the Secure Socket Tunneling Protocol services.

Why did the remote access connection manager fail to start?

Error: Remote Access Connection Manager failed to start because the Point to Point Protocol failed to initialize. The specified module could not be found. Error: The Remote Access Connection Manager service terminated with the following error: The specified module could not be found.

Why is my Remote Access not working on Windows 2000 SP4?

• You have not configured the Routing and Remote Access service or a remote access dial-up connection on the computer that you upgrade to Windows 2000 SP4. To work around this problem, restart the computer. When you restart the computer, all the remote access binary files are brought up to date.

image

Question

The regular community answers forum wouldn't accept my post (gave me an error message about the wrong number of characters), so I am visiting here. Hope that's OK.

Answers

Thanks so much for the advice. It's fixed. The problem was a combination of two factors. First, the Windows 10 updates were a problem. They were installed the day before this issue appeared. I could only uninstall one of them and that did not work. Fortunately, another update appeared last night.

All replies

I need to supplement this information with the fact that I was able to connect to my Colorado W10 host from Austin, TX on November 6 and had not tried to do so again until November 15, when the attempt failed. I changed nothing in either the laptop or desktop configuration in the interim.

image
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 1 2 3 4 5 6 7 8 9