VPN Connection Manager on SBS 2003 - 64-bit Issues

Hope someone can help. We are running SBS 2003 on our server and have been using the Connection Manager on laptop machines with no problem (Vista & XP). Well the other day, we now got a Vista x64 machine and I keep receiving an error when trying to install the Connection Manager:
"This profile was not built for this processor architecture. Please contact your Administrator to get the appropriate profile for this architecture."

I have searched through Google and have tried uninstalling/reinstalling it through Add/Remove Windows Components, but it didn't work and I'm back at square one.

Please help. Thanks
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

Jacobh06Connect With a Mentor Author Commented:
Well... after discussing this problem with another tech, we decided that it will be much easier downgrading and reinstalling to Vista 32-bit. That will fix all problems as we were also having issues with Exchange.
Thanks for the help though, I really appreciate it!
Rob WilliamsCommented:
I don't believe it will work on 64bit. You will likely have to create the connection on the PC/Laptop manually similar to the outline in the following link:
Jacobh06Author Commented:
I was thinking I may have to do that...
By default a Windows SBS Server 2003 still uses port 1723 for the VPN connection, correct? Or is there some other settings that I may need to be aware of?
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

Rob WilliamsCommented:
1723 is correct, which must be forwarded to the SBS, and GRE pass-through needs to be enabled, however these must be in place already and working since your other users can connect.

You should just simply need to create the VPN client on the remote PC, and no changes at the server end.

Having said that, the SBS connection manager adds  several options that help with name resolution. The basic client is the same. Once configured try connecting to a share using an IP such as  \\\ShareName  to confirm it is working. If that woks, but you cannot connect by name using \\PC-or-ServerName\ShareName,  you can 'repair' this by adding the SBS IP to the VPN client's DNS configuration, the internal domain suffix (such as MyDomain.local)  to the VPN client's DNS configuration, and the SBS IP to the VPN client's WINS configuration.
My Blog details some of these settings (see #3 & 4).
Jacobh06Author Commented:
I configured the VPN connection and I can't get connected. It keeps erroring out when trying to establish a connection with the server.
Any Ideas?
Also, I appreciate the help.
Rob WilliamsCommented:
What error # is displayed when the connection fails?  800, 721, 691...
Jacobh06Author Commented:
Error 800
Rob WilliamsConnect With a Mentor Commented:
800 is a basic connection error indicating no "handshaking" is taking place at all.
Since this is working from other machines I would suggest first testing you have the right connection information by doing a telnet test. To do so from a command line of the Vista 64bit machine  enter
telnet  1723
telnet  name.domainname.abc  1723
If you have the correct connection address (same as your VPN client), the port is open, and not blocked by a firewall,you will get a blank screen with a flashing cursor. If not it will time out or produce an error.

Having said that the telnet client is not enabled on Vista by default. You can easily enable it as per:
All Courses

From novice to tech pro — start learning today.