Windows 2000 Server-VPN-No Address assigned to internal interface

[tgbennett]

Hi,

I have a windows 2000 Server set up as a VPN server.
The problem is that the internal interface will not pick up an address.
The server is leasing 10 addresses as it's supposed to.
Under "Routing and Remote Access"/ "server name"/ "IP" tab i have manually set the DHCP Relay Agent to get its information from the interface connected to the LAN
The DHCP Relay Agent is configured to the internal interface and has the IP of the DHCP server.

I also get an error in the system log stating:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Source: IPBOOTP
Event ID: 30022

IPBOOTP was unable to receive an incoming message on the local interface with IP address172.27.17.187. The data is the error code.
I had it running for a poriod of time and it worked fine. So i am confident that other any other configuration is OK.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
172.27.17.187 is the interface connected to the LAN.

I have a feeling this has something to do with the problem.

Any help you might provide is greatly appreciated I have struggled with this issue for 3 weeks now and am at my wits end.


Sincerly,
Tim Bennett

 

[Kinjin]

I'm running into the same thing... internal interface will not pick up an address. Any resolution?

 

[tlcscousin]

check that the internal is set to the right nic card. if its giving out ip's look and see if they are getting a 169.254.x.x address.If you have it set to auto it could be going to the wrong one.

 

[Kinjin]

I can't even get it to answer an incoming call. It's a very basic setup, server is even on the DMZ, so I know it's not a port forwarding issue. This is a clean vanilla install, nothing at all configured for use as of this time. I've tried it with and without AD, same thing. I've tried the VPN wizard, and the Microsoft Technet manual configuration.


I've done this at clients before, with no problems whatsoever. I'm only using one NIC, but again, I've never had an issue setting it up at clients with one adapter.

Topology is as follows:

linksys befsr41
|
|
|
Win2k server

Not much more simple than that, eh?

 

[vasilepoenaru]

I assume that you have a DHCP server up and running. I also assume that you have an 'external' and an 'internal' interface.

first
1) Desktop -> right-click My computer -> Manage : "Computer management" starts
2) Services and Applications -> DHCP -> right-click / Properties -> Advanced tab -> click 'Bindings...' buton (on the bottom)
3) choose the interface you want this server to serve (I have only chosed the 'internal' interface on my machine)

second
1) Under "Routing and Remote Access"/ "server name"/ "IP" is enough to have 'General' and 'Static routes'. I also have NAT but this is anouther story ...
2) right click 'Routing and Remote acces Server' -> IP tab -> 'IP address management' should be set to use DHCP

!and now!

on the bottom of the above form you have a combo box to choose from the adapter: choose the one selected on the Bindings of the DHCP

How many leases the DHCP server shows as used by RAS depends on how many PPTP/L2TP ports you have enable (one for each port). To set the numer of each kind of port righ-click 'Ports' (under 'Routing and Remote Access'), select PPT and L2TP and then modify as you consider enough ... 5 for each one is quite ok


it works
i know it
i also use it

good luck
poe