CMAK on Server 2003 creating troublesome connectoids on XP Pro; worksgreat on Vista U SP1

I used CMAK on a Server 2003 machine to create a VPN conectoid. When I
install it on a Vista Ultimate machine, it works well.

However, when the same connectoid is installed on an XP SP2 machine,
two problems occur:

1. The connectoid defaults to the option that requires an ISP be
dialed before the VPN connection is made. Of course, simply checking
the radio button to not dial an ISP first will take care of the
problem, but I'm not thrilled about writing instructions that each XP
user will need to follow to get the VPN working correctly. It's a
small thing, but I like the things that I deploy to work seemlessly if
at all possible. Oddly enough, when the connectoid is deployed on
Vista SP1 machines, the default does NOT require an ISP to be dialed
first. Does anyone have insight into why the default is different on
Vista vs. XP and if I can get it to work uniformly on both OSs?

2. When I try to connect to the VPN on XP I can make it past making
the connection and then get to verifying the password, but after a few
seconds the connectiod throws the following error: "Connection Manager
was unable to launch CMMON32.EXE. Connecting is cancelled. For
troubleshooting information click help." It works great on Vista
Ultimate SP1! What's really odd is that using iHound.com to search for
that particular error only returns a couple of items. Most of them
seem to be in languages other than English. 0_o BTW, I have the
connectoid set to install Connection Manager 1.3 if it's not already
on the client machine.


Here's a couple of bonus questions if someone would like to answer
them:

Is the new version of CMAK on Server 2008 any better?

Is there an alternative to CMAK to build a VPN connection for mass
deployment?

Can the connectoid creation process be scripted with netsh or
vbscript? The former seems impossible and the later is made to be
impossible because of my nonexistant VB skills. Maybe I can hack
something together with rasphone and rasdial?


Guidance is appreciated. =)

If I understand #1 correction, start with figure 29 (near bottom) and work
your way to the end. (This suppresses the need to create a "dialup" and you
end up with just a "vpn" connectoid.)

Not sure about #2. When I build x86/x64 vpn connectiods using CMAK, I don't
select the option to include the Connection Manager since my site doesn't
support anything less than WinXP.

Haven't adopted Server 2008, so I can't answer the CMAK question.
<(E-Mail Removed)> wrote in message
news:7dd3bb68-6716-47e1-94bc-(E-Mail Removed)...
>I used CMAK on a Server 2003 machine to create a VPN conectoid. When I
> install it on a Vista Ultimate machine, it works well.
>
> However, when the same connectoid is installed on an XP SP2 machine,
> two problems occur:
>
> 1. The connectoid defaults to the option that requires an ISP be
> dialed before the VPN connection is made. Of course, simply checking
> the radio button to not dial an ISP first will take care of the
> problem, but I'm not thrilled about writing instructions that each XP
> user will need to follow to get the VPN working correctly. It's a
> small thing, but I like the things that I deploy to work seemlessly if
> at all possible. Oddly enough, when the connectoid is deployed on
> Vista SP1 machines, the default does NOT require an ISP to be dialed
> first. Does anyone have insight into why the default is different on
> Vista vs. XP and if I can get it to work uniformly on both OSs?
>
> 2. When I try to connect to the VPN on XP I can make it past making
> the connection and then get to verifying the password, but after a few
> seconds the connectiod throws the following error: "Connection Manager
> was unable to launch CMMON32.EXE. Connecting is cancelled. For
> troubleshooting information click help." It works great on Vista
> Ultimate SP1! What's really odd is that using iHound.com to search for
> that particular error only returns a couple of items. Most of them
> seem to be in languages other than English. 0_o BTW, I have the
> connectoid set to install Connection Manager 1.3 if it's not already
> on the client machine.
>
>
> Here's a couple of bonus questions if someone would like to answer
> them:
>
> Is the new version of CMAK on Server 2008 any better?
>
> Is there an alternative to CMAK to build a VPN connection for mass
> deployment?
>
> Can the connectoid creation process be scripted with netsh or
> vbscript? The former seems impossible and the later is made to be
> impossible because of my nonexistant VB skills. Maybe I can hack
> something together with rasphone and rasdial?
>
>
> Guidance is appreciated. =)

On May 30, 10:22*pm, "neo [mvp outlook]"
<n...@discussions.microsoft.com> wrote:
> If I understand #1 correction, start with figure 29 (near bottom) and work
> your way to the end. *(This suppresses the need to create a "dialup" andyou
> end up with just a "vpn" connectoid.)
>
> Not sure about #2. *When I build x86/x64 vpn connectiods using CMAK, I don't
> select the option to include the Connection Manager since my site doesn't
> support anything less than WinXP.
>
> Haven't adopted Server 2008, so I can't answer the CMAK question.<Nonapept....@gmail.com> wrote in message
>
> news:7dd3bb68-6716-47e1-94bc-(E-Mail Removed)...
>
> >I used CMAK on a Server 2003 machine to create a VPN conectoid. When I
> > install it on a Vista Ultimate machine, it works well.
>
> > However, when the same connectoid is installed on an XP SP2 machine,
> > two problems occur:
>
> > 1. The connectoid defaults to the option that requires an ISP be
> > dialed before the VPN connection is made. Of course, simply checking
> > the radio button to not dial an ISP first will take care of the
> > problem, but I'm not thrilled about writing instructions that each XP
> > user will need to follow to get the VPN working correctly. It's a
> > small thing, but I like the things that I deploy to work seemlessly if
> > at all possible. Oddly enough, when the connectoid is deployed on
> > Vista SP1 machines, the default does NOT require an ISP to be dialed
> > first. Does anyone have insight into why the default is different on
> > Vista vs. XP and if I can get it to work uniformly on both OSs?
>
> > 2. When I try to connect to the VPN on XP I can make it past making
> > the connection and then get to verifying the password, but after a few
> > seconds the connectiod throws the following error: "Connection Manager
> > was unable to launch CMMON32.EXE. Connecting is cancelled. For
> > troubleshooting information click help." It works great on Vista
> > Ultimate SP1! What's really odd is that using iHound.com to search for
> > that particular error only returns a couple of items. Most of them
> > seem to be in languages other than English. 0_o BTW, I have the
> > connectoid set to install Connection Manager 1.3 if it's not already
> > on the client machine.
>
> > Here's a couple of bonus questions if someone would like to answer
> > them:
>
> > Is the new version of CMAK on Server 2008 any better?
>
> > Is there an alternative to CMAK to build a VPN connection for mass
> > deployment?
>
> > Can the connectoid creation process be scripted with netsh or
> > vbscript? The former seems impossible and the later is made to be
> > impossible because of my nonexistant VB skills. Maybe I can hack
> > something together with rasphone and rasdial?
>
> > Guidance is appreciated. =)

Thanks! I hadn't fully grasped the power of the advanced settings at
the end of the CMAK. I was able to successfully change the default
option.

Wow. There are alot of possibilites that CMAK offers.

Thanks again, =)

BTW, the CMMON32.exe error mysteriously disappeared.

I chose to not install the Connection Manager for this latest
connectoid. Not sure if that had anything to do with it. Nonetheless,
I'm happy. =)