I have a couple of multihomed W2K3+SP2 systems with RRAS (running DOD VPNs
and NAT, with public Internet NIC and private Local Area Connection NIC).
Normally, the Internal interface acquires an IP from DHCP or from the static
address pool, chosen on the IP tab.
On one machine, whether DHCP or static address pool is specified, the
Internal interface always acquires an APIPA addess (169.254.x.x). This raises
havoc with subsequent attempts to establish DOD VPN connections.
I have tried removing and adding the RRAS role without effect.
Note that DHCP runs on the same machine, as does AD, DNS and WINS. Each is
an 'all-in-one' DC acting as a file/print server. No non-MS software is
installed.
Q: How can I force the Internal interface to use the setting (DHCP or
static) specified on the IP tab?
Q: How can I reset all of RRAS back to defaults, if removing and adding the
role is not sufficient?
Q: (Extra points) What could cause this APIPA use in the first place?
Thanks!
Bookmarks