Re: Routing and Remote Access

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Bill Grant (not.available_at_online)
Date: 07/17/04


Date: Sun, 18 Jul 2004 09:32:50 +1000


   The internal interface is the endpoint for the VPN connection. It will
become active and acquire an IP when a client connects. So what you are
seeing is really a symptom that VPN is not working, not a cause.

    If you are using private addresses behind a router, the VPN client must
initially connect to the router's public IP address. You then forward TCP
port 1723 (pptp) to the LAN IP of the RRAS server to extend the connection
to the server on the LAN.

    But if you have a VPN capable router, why are you trying to connect to
the server at all? Just make a VPN connection to the router and use normal
LAN routing to see the LAN machines.
"Happy" <anonymous@discussions.microsoft.com> wrote in message
news:2e17401c46c28$c4663220$a601280a@phx.gbl...
> I have been trying to configure our Windows Server 2003
> for a VPN (behind a VPN router). I had the VPN working
> from some locations outside our network, but not others.
> I suspected that the cause of this intermitent
> connectivity was that our internal lan was configured on
> 192.168.1.xxx. I understand that when both the LAN that
> you are coming from and going too have the same IP's there
> can be problems. To resolve this problem I changed the
> LAN/Router IP's to 192.168.10.xxx. I can no longer access
> the server through the VPN, but everything seems normal
> inside the LAN.
>
> I suspect the problem is reflected at the Routing and
> Remote Access\ServerName\IP Routing\General\Internal.
> When I look at this setting (under Routing and Remote
> Access) it says
> IP Address: Not available
> Administrative Status: Unknown
> Oprational Status: Non-operational
> Incoming bites: -
> Outgoing bites: -
>
> As I recall, there used to be values under Internal. I
> can't find any method of reseting this. I tried removing
> the server from Routing and Remote Acces then
> reconfiguring it, but I can change this Internal settings.
>
> Is this my VPN problem and, if so, how do I fix it?



Relevant Pages

  • RE: VPN Error 800
    ... On the Small Business Server 2003-based server, click To Do List in the ... Click Next, click Enable Remote Access, click to select the VPN Access ... go to the client and establish the VPN connection to the ... please help me gather the ISA info and ISA log: ...
    (microsoft.public.windows.server.sbs)
  • RE: Enabling VPN Remote Access using SBS 2003 standard with ISA 2004
    ... SBS Server, the inbound VPN connection no longer worked. ... Configure the VPN connection on the client and do a VPN test. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN via Wireless Broadband
    ... I don't know how timing-sensitive VPN connections are. ... Browsing to the User shared folder from the client doesn't work. ... shares on the server and SYSVOL is there and one can use Windows ... How to configure a VPN connection to your corporate network in Windows XP ...
    (microsoft.public.windows.server.sbs)
  • Re: Certifcate reset error - Need for mobile device connect
    ... What I am trying to accopmlish is to have my SBS exchange server synch wireless with a Motorola Q phone. ... Manager packet from the SBS 2003 server to recreate the VPN connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA2004 kills VPN outbound
    ... The VPN connection you're seeing into the branch-office server is me ... > Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)