Re: XP Remote Desktop over VPN problem

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Sorry for disturb your discussion, but I have a similar problem maybe you
could help.
I have a normal LAN, connected to internet and with a PC running SQL-Server
express. I need to connect a external PC via VPN to the LAN. For security
reasons I can not use de SQL PC as a VPN server, but maybe I could use one of
the others as a VPN server and connect through it to the SQL-PC. This is the
idea: the LAN is in the 192.168.16.x range, I use an internte router with
the needed ports open and the VPN server PC with 2 NICs (network cards).
What is the configuration method I should use? Thank you for your help.
--
José Camacho Vaca
Colima, MX


"Sooner Al [MVP]" wrote:

So your basic connection is like this if you ignore the desktop and laptop
on the VPN servers network. You only have the VPN client and the VPN server
which is also the PC you want to access with Remote Desktop (RDC), right?

http://theillustratednetwork.mvps.org/Vista/PPTP/VPN-HomeUser.html

As far as dynamically assigned IPs from an ISP you could use a service like
No-IP.com to map a fully qualified domain name (FQDN) to the ISP assigned
IP. That way you simply call the remote VPN server or Remote Desktop (RDC)
host PC by the FQDN.

The 169.254.X.X address is not assigned by the VPN or DHCP server. That
simply means the client PC your seeing it on is not getting a valid IP from
the local DHCP server.

If your running the built-in PPTP VPN server on an XP box you can manually
configure what the address is the client will receive. In the case of an XP
box acting as both a PPTP VPN server and the RDC host use the first address
in the example, ie. the From: address. The client gets the To: address.

http://theillustratednetwork.mvps.org/WM2003/VPN_Server/IncomingConnectionsTCPIP.JPG

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375


"Stew" <Stew@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6916C4BF-0A72-4CB5-A030-B601159B9BCC@xxxxxxxxxxxxxxxx
The PC I'm remoting into is unmanned (telemetry PC) and uses a Wireless
Broadband modem with dynamic IP address. Often I am using the same config
on
my local PC. Therefore the IP addresses are allocated from the ISPs pool
and
appear to be across the various Public IP address ranges and I assume have
no
control over this (they don't offer a static IP service). I have have just
noted in another thread on another site that VPN allocates it's own
separate
set of IP addresses inside of this. They tend to be in the 169.254.x.x
range.
I have also just found I can see the client/server addresses at the local
end
and can use the server IP address in RDT to connect. However these
addresses
seem to be dynamic as well and I was trying to find a way to use a
consistent
connection name in RDT (like Computer Name) as I have a number of
different
remote PCs to connect into. I tried putting the VPN server IP address in
the
HOST file of the remote PC with a text name, but it didn't work.
Fundamentally I'm trying to keep it simple and just wanted to use a
hostname
to establish VPN and Computer Name for RDT.

"Sooner Al [MVP]" wrote:

Correction..."client on 192.168.1.X for example. Note the third octet."

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375

"Sooner Al [MVP]" <SoonerAl@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C296F5BB-DF82-499D-9CD5-639C965DE4A7@xxxxxxxxxxxxxxxx
When you connect with the VPN can you ping the target Remote Desktop
(RDC)
host PC by IP?

Note that if the PPTP VPN server network and the remote network your
accessing the server on are using the same address scope, ie. both in
the
192.168.0.X range for example, you will have trouble connecting to the
RDC
host. Its a good idea for the server network and the remote network to
be
in different address ranges, ie. PPTP VPN server on 192.168.0.X and the
remote client on 102.168.1.X for example. Note the third octet.

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375

"Stew" <Stew@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:298A9DFF-AF45-4A7F-9C07-507A6944691D@xxxxxxxxxxxxxxxx
OS: XP Pro V2002 SP2.
Trying to use XP Remote Desktop within VPN (using XP inbuilt VPN
Client/Server) between two standalone PCs. Each work fine on their own
ie.
VPN connects OK or RDT connects and works OK, but once I setup VPN
connection
and try and run RDT over it, it fails to connect. I have used this
solution
successfully between two XP PCs, but with domains defined (using
Computer
Name in the RDT Connection 'Computer:' field). The PCs I have the
problem
with both have a workgroup defined, not domain, (Windows default of
WORKGROUP). I have tried both the Computer Name and the hostname,
neither
work.
Can anyone help with a solution?




.

Relevant Pages

  • Re: ISA2004 kills VPN outbound
    ... I have the same problem connecting to several different VPN servers. ... > it use a hardware router or a windows-based computer to be its VPN Server? ... > connection will fail in some cases when a hardware firewall resides in the ... > |> FW client and configure the client as a SecureNAT client. ...
    (microsoft.public.windows.server.sbs)
  • Re: Conecting to an external VPN
    ... but the VPN server is not mine.. ... There is no firewall client.. ... However, the connection still timesout.. ...
    (microsoft.public.isa.vpn)
  • Re: I cant access files in VPN server when connected via VPN
    ... The fact that you cannot ping your VPN server when in a VPN connection indicates some kind of network configuration issue. ... It would be advisabe to post this on a networking/VPN forum to get further troubleshooting steps and narrow down the place where the network setup is failing. ... Remote desktop is: “The client could not connect to the remote computer. ...
    (microsoft.public.windows.terminal_services)
  • Re: VP Error 47 with sbs 2003
    ... The client recieves the following error.. ... A connection between the VPN server and the VPN client 63.229.16.227 has been established, but the VPN connection cannot be completed. ... The most common cause for this is that a firewall or router between the VPN server and the VPN client is not configured to allow Generic Routing Encapsulation packets. ... Verify that the firewalls and routers between your VPN server and the Internet allow GRE packets. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN question.
    ... Routing and Remote Access is on and setup. ... > Is your VPN Server configured for routing? ... Doe sit have 2 NICs or a single ... >> connection at a time. ...
    (microsoft.public.isa.vpn)