VPN server on RC2 not getting DHCP

Hi, I have just upgraded my 03 server to RC2.
Prior to this I had a VPN server set up and working with no problems. After
the upgrade the VPN server seems to be not getting a DHCP address. It is
assigning a 169.254.133... address and as such when a conection is made to
the VPN server the clients are getting a 169 as well. If I set a static in
the properties of the users account on the domain its OK but I don't want to
have to do this. I want DHCP to dynamically assign addresses.
DHCP is working fine on the network, local users are able to request and
receive IP's.
Any insight would be appreciated. Why is the VPN internal interface getting
this IP?
thanks
jason

Is the DHCP also windows server? Do you also receive Event ID 20169? If the VPN server has a problem to connect to the DHCP, it will assign 169.254.x.x IP. This may help,

tcp/ip settings for vpnThis is because your VPN server doesn't have DHCP to assign IP so that the the VPN server uses APIPA to provides an address like 169.x.x.x. ...
http://www.chicagotech.net/vpntcpipsettings.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"bassjace" <(E-Mail Removed)> wrote in message news:B10B122D-FBF3-4406-B394-(E-Mail Removed)...
Hi, I have just upgraded my 03 server to RC2.
Prior to this I had a VPN server set up and working with no problems. After
the upgrade the VPN server seems to be not getting a DHCP address. It is
assigning a 169.254.133... address and as such when a conection is made to
the VPN server the clients are getting a 169 as well. If I set a static in
the properties of the users account on the domain its OK but I don't want to
have to do this. I want DHCP to dynamically assign addresses.
DHCP is working fine on the network, local users are able to request and
receive IP's.
Any insight would be appreciated. Why is the VPN internal interface getting
this IP?
thanks
jason

Thanks for your reply.
The DHCP server and the routing and remote access service are on the same
machine. That is why I find it very strange. The previous setup was exactly
the same except now it is a RC2 machine. I have told the RAS to use DHCP and
not a static pool. If I set a static pool, IP's are assigned out of that
range and all is OK. But put it back to DHCP and it gets a APIPA. This is not
how it should be.
Is there a event log I should be looking at?

"Robert L [MVP - Networking]" wrote:

> Is the DHCP also windows server? Do you also receive Event ID 20169? If the VPN server has a problem to connect to the DHCP, it will assign 169.254.x.x IP. This may help,
>
> tcp/ip settings for vpnThis is because your VPN server doesn't have DHCP to assign IP so that the the VPN server uses APIPA to provides an address like 169.x.x.x. ...
> http://www.chicagotech.net/vpntcpipsettings.htm
>
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "bassjace" <(E-Mail Removed)> wrote in message news:B10B122D-FBF3-4406-B394-(E-Mail Removed)...
> Hi, I have just upgraded my 03 server to RC2.
> Prior to this I had a VPN server set up and working with no problems. After
> the upgrade the VPN server seems to be not getting a DHCP address. It is
> assigning a 169.254.133... address and as such when a conection is made to
> the VPN server the clients are getting a 169 as well. If I set a static in
> the properties of the users account on the domain its OK but I don't want to
> have to do this. I want DHCP to dynamically assign addresses.
> DHCP is working fine on the network, local users are able to request and
> receive IP's.
> Any insight would be appreciated. Why is the VPN internal interface getting
> this IP?
> thanks
> jason

Check the Event Viewer.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"bassjace" <(E-Mail Removed)> wrote in message news:F134B68C-5939-4B6C-9655-(E-Mail Removed)...
Thanks for your reply.
The DHCP server and the routing and remote access service are on the same
machine. That is why I find it very strange. The previous setup was exactly
the same except now it is a RC2 machine. I have told the RAS to use DHCP and
not a static pool. If I set a static pool, IP's are assigned out of that
range and all is OK. But put it back to DHCP and it gets a APIPA. This is not
how it should be.
Is there a event log I should be looking at?

"Robert L [MVP - Networking]" wrote:

> Is the DHCP also windows server? Do you also receive Event ID 20169? If the VPN server has a problem to connect to the DHCP, it will assign 169.254.x.x IP. This may help,
>
> tcp/ip settings for vpnThis is because your VPN server doesn't have DHCP to assign IP so that the the VPN server uses APIPA to provides an address like 169.x.x.x. ...
> http://www.chicagotech.net/vpntcpipsettings.htm
>
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "bassjace" <(E-Mail Removed)> wrote in message news:B10B122D-FBF3-4406-B394-(E-Mail Removed)...
> Hi, I have just upgraded my 03 server to RC2.
> Prior to this I had a VPN server set up and working with no problems. After
> the upgrade the VPN server seems to be not getting a DHCP address. It is
> assigning a 169.254.133... address and as such when a conection is made to
> the VPN server the clients are getting a 169 as well. If I set a static in
> the properties of the users account on the domain its OK but I don't want to
> have to do this. I want DHCP to dynamically assign addresses.
> DHCP is working fine on the network, local users are able to request and
> receive IP's.
> Any insight would be appreciated. Why is the VPN internal interface getting
> this IP?
> thanks
> jason