[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 539
  • Last Modified:

VPN on Windows 2003

When I connect to my Windows 2003 with VPN it assign me the IP address 169.254.x.x instead of some 192.168.x.x address. VPN is set up on the server. The server act as router for the internal network and is running DHCP. I need to acces machine on the internal network 192.168.x.x when I connect.
0
soffcec
Asked:
soffcec
4 Solutions
 
Mohed SharfiCommented:
Hi
How are you
try to add new ip on your 2003 server beginning with 192.168.x.x to route  the internal network
Best Of Luck
0
 
rowansmithCommented:
DHCP is not passing through your VPN (which is normal).

That IP address is automatically assigned by your computer to itself when it has no IP Address configured or was not able to detect an IP Address dynamically.

Check your address pool on you server.
0
 
ntypeCommented:
As someone pointed out you need configure your routing and remote access snap-in to relay DHCP requests or allocate an IP pool within it.

The following link talks about ISA server, however look for the 'Configuring the ISA Server firewall/VPN Server to Use DHCP for VPN Client Address Assignment' part, it will describe the exact procedure.



http://www.isaserver.org/img/upl/vpnkitbeta2/dhcprelay.htm





/rant funny I had answered this question but my comment disapeared

fig20.jpg
0
 
soffcecAuthor Commented:
xx
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now