Solved

VPN Connection Manager on SBS 2003 - 64-bit Issues

Posted on 2009-05-06
8
1,478 Views
Last Modified: 2013-11-14
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
0
Comment
Question by:Jacobh06
  • 4
  • 4
8 Comments
 
LVL 77

Expert Comment

by:Rob Williams
ID: 24314552
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:
http://www.onecomputerguy.com/networking/vista_vpn_client.htm
0
 
LVL 3

Author Comment

by:Jacobh06
ID: 24315200
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?
Thanks
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 24315658
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  \\192.168.16.123.123\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).
http://msmvps.com/blogs/robwill/archive/2008/05/10/vpn-client-name-resolution.aspx
0
Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

 
LVL 3

Author Comment

by:Jacobh06
ID: 24325617
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.
~Jake
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 24325814
What error # is displayed when the connection fails?  800, 721, 691...
0
 
LVL 3

Author Comment

by:Jacobh06
ID: 24325898
Error 800
Thanks,
~Jake
0
 
LVL 77

Assisted Solution

by:Rob Williams
Rob Williams earned 500 total points
ID: 24326486
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  123.123.123.123  1723
or
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:
http://www.tech-recipes.com/rx/2050/vista_install_enable_telnet_client_server/
0
 
LVL 3

Accepted Solution

by:
Jacobh06 earned 0 total points
ID: 24350911
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!
~Jake
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

OpenVPN is a great open source VPN server that is capable of providing quick and easy VPN access to your network on the cheap.  By default the software is configured to allow open access to your network.  But what if you want to restrict users to on…
Finding original email is quite difficult due to their duplicates. From this article, you will come to know why multiple duplicates of same emails appear and how to delete duplicate emails from Outlook securely and instantly while vital emails remai…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question