remote access on windows 2003.

  • Thread starter Thread starter vasant.naidu
  • Start date Start date
V

vasant.naidu

Hi,

First let me explain to you my setup:

1. PC - Windows XP.
This PC has two network cards, one for local network and one for
internet. Both have IP addresses:
local card -> 192.168.1.5 (our local network address) 255.255.255.0

internet card -> 10.12.174.93 (this IP is provided by the Internet Service Provider)
Click to expand...
255.255.0.0
Default Gateway -> 10.12.174.1 (provided by ISP)

2. Server - Windows 2003 server edition
network card -> 192.168.1.101
Click to expand...
255.255.255.0

Both the above PC are in my office in india.

Now I am in america and I want to remotely connect to my server to run
applications.

How do I go about this.

I tried to check out VPNs, but I am not sure how and where I start. I
also tried IP forwarding but even that does not work.

Can anybody help me out.

Regards,
Vasant
 
If your ISP is providing an IP address on the 10 network, it may not be
possible. You need an incoming path for either RDP or a VPN that can be
routed. The 10 network is private and cannot be publicly routed. If the 10
network is on the back side of a cable or DSL modem, the public side should
have a public IP address. In that case, you'd need to know what it is, and
forward the port(s) for remote access to your server. Do you have a local
router? Can you web into it?

....kurt
 
Switch your configuration. Put two nic's in the W2K3 Server. Assign the
nics with your static ip (local/public). Install and Configure DHCP on
the W2K3 Server. Configure Routing and Remote Access to use NAT.
Connect your local nic to your switch/hub. Connect your XP box to the
switch/hub. The XP PC will recieve IP config from your W2K3 DHCP server
and access the internet via NAT. For remote access simply turn on
terminal services in remote administration mode. From your remote
location run mstsc and type in your public ip.

Or you could buy a cheap-o router and configure lan/wan ip's and dhcp
to give your server and xp pc ip configuration. Then you would have to
the router to pass 3389 to the local ip of your server. Usage of mstsc
would not be changed.

Hope this helps,
psg
 
Nice fix psg .... if DSL with lease durations on your WAN interface
might I suggest using DDNS to track the WAN IP change. No.ip is free
and has a kewl little updater u can install on your w2k3 box.
Otherise what psg said.. =0p
 
thanks for the acknowledgement... The ddns suggestion would be very
helpful for Dynamic Public IP's being used for remote adminstration
purposes. Vasant, if you want you could ask your ISP for a static IP.
If you have a domain name I could host dns for you. Instead of using an
ip you could use computername.yourdomain.com. Just a suggestion..

psg
 
Back
Top