I
Ian
Hello,
Since creating an Incoming (VPN) Network Connection on my Windows XP
Professional based machine, I find repeated occurences of the following two
messages in my System event log.
# | Event Type | Event Source | Event ID | Description... | (Data)
#1 | Error | RemoteAccess | 20106 | Unable to add the interface
{E8236C84-6226-498D-92F0-055AA0F87EE2} with the Router Manager for the IP
protocol. The following error occurred: Cannot complete this function. |
0000: eb 03 00 00
#2 | Warning | RemoteAccess | 20192 | A certificate could not be found.
Connections that use the L2TP protocol over IPSec require the installation
of a machine certificate, also known as a computer certificate. No L2TP
calls will be accepted.
I have researched both of these messages and have found useful information
over at EventID.net but it is written in the context of Windows 2000 (not
Windows XP). Their advice (for 20192) is basically to use RRASMGMT.MSC to
configure VPN to use only PPTP (i.e. disable L2TP). The problem is that the
RRASMGMT.MSC snap-in for MMC does not seem to exist in (at least in my
installation of) Windows XP Professional. Is there a way to add this
snap-in to Windows XP or is there perhaps another way to configure VPN to
not use L2TP? Alternately, how would I go about obtaining my own machine
certificate?
With regard to #20106 - I am unclear whether it's related to VPN &
(PPTP/L2TP) or if it's because I have 2 physical network interfaces in my
machine. I have your basic everyday Ethernet Adapter and also a Firewire
Card that can potentially be configured for "Firewire" networking - not
something that I intend to setup anytime soon. Could someone tell me how to
drill down to this interface {E823...blah blah blah ...EE2} and find out
what it is? This naming convention they use for interfaces is certainly an
improvement over what we used to do back in the days of hollerith punch
machines & paper tapes (NOT!)
Thanks in advance to the learned individuals who can shed some light here,
Ian
Since creating an Incoming (VPN) Network Connection on my Windows XP
Professional based machine, I find repeated occurences of the following two
messages in my System event log.
# | Event Type | Event Source | Event ID | Description... | (Data)
#1 | Error | RemoteAccess | 20106 | Unable to add the interface
{E8236C84-6226-498D-92F0-055AA0F87EE2} with the Router Manager for the IP
protocol. The following error occurred: Cannot complete this function. |
0000: eb 03 00 00
#2 | Warning | RemoteAccess | 20192 | A certificate could not be found.
Connections that use the L2TP protocol over IPSec require the installation
of a machine certificate, also known as a computer certificate. No L2TP
calls will be accepted.
I have researched both of these messages and have found useful information
over at EventID.net but it is written in the context of Windows 2000 (not
Windows XP). Their advice (for 20192) is basically to use RRASMGMT.MSC to
configure VPN to use only PPTP (i.e. disable L2TP). The problem is that the
RRASMGMT.MSC snap-in for MMC does not seem to exist in (at least in my
installation of) Windows XP Professional. Is there a way to add this
snap-in to Windows XP or is there perhaps another way to configure VPN to
not use L2TP? Alternately, how would I go about obtaining my own machine
certificate?
With regard to #20106 - I am unclear whether it's related to VPN &
(PPTP/L2TP) or if it's because I have 2 physical network interfaces in my
machine. I have your basic everyday Ethernet Adapter and also a Firewire
Card that can potentially be configured for "Firewire" networking - not
something that I intend to setup anytime soon. Could someone tell me how to
drill down to this interface {E823...blah blah blah ...EE2} and find out
what it is? This naming convention they use for interfaces is certainly an
improvement over what we used to do back in the days of hollerith punch
machines & paper tapes (NOT!)
Thanks in advance to the learned individuals who can shed some light here,
Ian