Windows 7  64 bit Connecting to SBS 2003 32 bit

Posted on 2009-12-28
Last Modified: 2012-05-08
I am trying to connect a VPN to a Win 2003 32 Bit Server, but I get this :this profile not built for this processor architecture. I even tried creating manually with the Win 7 VPN wizard, but it still will not connect. Any ideas?
Question by:jackm1
    LVL 9

    Assisted Solution

    I presume you were trying to connect with the Connection Manager package built on the 32bit server. You have to build the 64bit version to run on your Windows7 Machine. AFAIK you need to do that on a 64bit server. The manual connection should not give you this same error can you definately confirm that error with a manual connection?

    LVL 4

    Expert Comment

    As jeff_01 said, you are not able to use Connection Manager to connect to a SBS 2003 32-bit from a 64bit client. This message is expected. Since this is SBS 2003, why not use RWW? This is more convenient than VPN from my point of view.

    Author Comment

    Well I tried setting up the VPN manually, and I get Connecting:Wan miniport pptp and then L2TP
    Then I get: Error 800 The Remote connection was not made because the attempted VPN tunnelsfailed
    If the SBS Connection worked before shouldn't the VPN work too in Win7. I setup a VPN in the past with a XP notebook and it worked before?
    My client does not want to use RWW.
    LVL 4

    Accepted Solution

    Please refer to this blog:

    As we can see, possible Cause of the error is:
    This error comes when the VPN tunnel type is Automatic and the connection establishment fails for all the VPN tunnels.

    Possible Solutions:

    a> If you know which tunnel should actually be used for your deployment, try to set the Type of VPN to that particular tunnel type on the VPN client side. [This can be set by clicking the Network Connections icon on the bottom right of the task bar, Select your Connection, Right Click -> Properties -> Securities Tab -> Under Type of VPN select the interested VPN tunnel type ]

    By making VPN connection with a particular tunnel type, your connection will still fail but it will give a more tunnel specific error (for example: GRE blocked for PPTP, Certificate error for L2TP, SSL negotiation errors for SSTP, etc.)

    b> This error usually comes when the VPN server is not reachable or the tunnel establishment fails.

    i. Make sure the VPN server is reachable (try to PING the server).

    ii. If interested in PPTP, make sure PPTP port (TCP 1723) or GRE Port (47) is not blocked on in between firewalls.

    iii. If interested in L2TP, make sure

    1. Correct pre-shared key or machine certificate are present both on client and server.

    2. L2TP port (UDP 1701) is not blocked on any of the firewalls.

    iv. If interested in IKEv2 based VPN tunnel, make sure

    1. IKE port (UDP port 500, UDP port 4500) is not blocked.

    2. Correct machine certificate for IKE are present both on client and server.

    Featured Post

    IT, Stop Being Called Into Every Meeting

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    Join & Write a Comment

    Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found listed in my profile here: http:…
    This is a little timesaver I have been using for setting up Microsoft Small Business Server (SBS) in the simplest possible way. It may not be appropriate for every customer. However, when you get a situation where the person who owns the server is i…
    In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
    Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

    729 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

    Need Help in Real-Time?

    Connect with top rated Experts

    19 Experts available now in Live!

    Get 1:1 Help Now