Results 1 to 6 of 6

Thread: Windows 2003 Server "Routing and Remote Access" VPN

  1. #1
    Senior Member
    Join Date
    Sep 2005
    Posts
    587
    Thanks
    7
    Thanked
    7 times in 7 posts

    Windows 2003 Server "Routing and Remote Access" VPN

    Hello, can someone please help me figure out why I am getting "Error 691: The connection was denied because the username and/or password you specified is invalid"?


    The username and password is correct. I have followed this tutorial to successfully set up the "Remote Access/VPN Server" Role.

    Then I went into Active Directory and ensured that the user had the proper "Dial-In" permissions:


    Then I added the DHCP server's IP in the Relay properties, which this site told me to do:


    Then I went into the Remote Access Policies properties and changed "Deny" to "Grant":


    It's still not working though Anyone know some info that will let me do it? It would be great to get this working before the weekend! Thanks
    Last edited by latrosicarius; 24-01-2009 at 05:02 PM.

  2. #2
    Jay
    Jay is offline
    Gentlemen.. we're history Jay's Avatar
    Join Date
    Aug 2006
    Location
    Jita
    Posts
    8,365
    Thanks
    304
    Thanked
    568 times in 409 posts

    Re: Windows 2003 Server "Routing and Remote Access" VPN

    do you have the Windows logon domain check box is selected in the Options tab?
    □ΞVΞ□

  3. #3
    Senior Member
    Join Date
    Sep 2005
    Posts
    587
    Thanks
    7
    Thanked
    7 times in 7 posts

    Re: Windows 2003 Server "Routing and Remote Access" VPN

    lol where is this "Options tab" you speak of?

    EDIT: If you mean this checkbox on the client-side connection setup, then yes. All values are default except for the pertinant information asked for by the wizard (address, username, password, domain).
    Last edited by latrosicarius; 24-01-2009 at 05:04 PM.

  4. #4
    Senior Member
    Join Date
    Sep 2005
    Posts
    587
    Thanks
    7
    Thanked
    7 times in 7 posts

    Re: Windows 2003 Server "Routing and Remote Access" VPN

    Okay, I solved the problem. You were very close, jay!

    To anyone else who encounters this problem, be wary of what you enter in the "domain" box.

    Some networks are set up with DNS being the following domains "mysubdomain.mydomain" or a multi-step domain.

    For the VPN, however you will want to use only the part of that which your Active Directory usernames log into.

    For instance, when logging onto your server you use:

    Code:
    User1@mysubdomain.mydomain
    - or -
    MYSUBDOMAIN\User1
    Use only the subdomain if you have this setup. In other words, the lower box:


    Thanks for your help though, jay
    Last edited by latrosicarius; 24-01-2009 at 05:07 PM.

  5. #5
    Senior Member
    Join Date
    Sep 2005
    Posts
    587
    Thanks
    7
    Thanked
    7 times in 7 posts

    Re: Windows 2003 Server "Routing and Remote Access" VPN

    One more thing, while I'm at it...

    When you connect to the VPN, it routes all your internet traffic through the server. This means 2 things:

    1.) Your connection will be momentarily dropped because your IP address is essentially changing from that of your computer, to that of the server.

    2.) VPN is slow. Since all your traffic is going first going INTO your server, and then being sent OUT of your server, to your computer, all your traffic will be limited to the maximum upload speed of your SERVER's internet connection.

    Unless your server's ISP is providing a symmetrical line (i.e.: 20/20 MBps) or at least a higher upload speed than a normal residential connection, the traffic to your client will be severely slowed down by the inability of the server's connection to UPLOAD your traffic back out to the net and tunneled to you at the speed at which you are used to DOWNLOADING.

    ---

    To prevent both of these conditions, go into the VPN Connection properties on the client, and go to the "Networking" tab.

    For Vista you will have to do this for IPv6 and IPv4. For XP, only IPv4.

    Click "Properties", on the next window that opens, click "Advanced". Finally another window opens where you can de-select the checkbox titled "Use default gateway on remote network":


    On my client, I actually created 2 identical VPN connections with the only difference between them being this checkbox is ON for one, and OFF for the other. This way, I can just click whichever one I want, depending on if I want to keep my direct connection to the internet, or have internet traffic routed through the server's connection.
    Last edited by latrosicarius; 24-01-2009 at 05:08 PM.

  6. #6
    Jay
    Jay is offline
    Gentlemen.. we're history Jay's Avatar
    Join Date
    Aug 2006
    Location
    Jita
    Posts
    8,365
    Thanks
    304
    Thanked
    568 times in 409 posts

    Re: Windows 2003 Server "Routing and Remote Access" VPN

    Glad you got it sorted.
    □ΞVΞ□

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Windows - hotfixing overview
    By Paul Adams in forum Software
    Replies: 13
    Last Post: 13-10-2009, 11:17 AM
  2. Network Storage Device
    By Whatsthisdo in forum Networking and Broadband
    Replies: 31
    Last Post: 14-11-2007, 03:37 AM
  3. VPN Server 2003 and DG834GT
    By pcpower in forum Networking and Broadband
    Replies: 1
    Last Post: 21-08-2007, 08:37 PM
  4. New Windows Updates out peeps
    By Skii in forum Software
    Replies: 10
    Last Post: 04-08-2004, 06:19 AM
  5. Windows 2003 Remote Desktop
    By Richie in forum Software
    Replies: 2
    Last Post: 28-01-2004, 02:44 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •