S
Steve Kraus
Our server is Windows 2000, running DHCP and RAS. Until
recently, Windows XPP laptops in the field were able to
connect to the Internet via any method and then connect
via VPN to the above server.
As of recent, Windows XPP machines have not been able to
get a valid IP address from our normal scope
(192.168.1.150-199) and are instead being assigned
169.254.216.0-255 IP addresses (APIPA?) with a different
gateway.
Client with Windows 2000 in the field are not having this
problem.
The PCs in question are connecting to the Internet and
are indeed authenticating across the VPN... according to
the client. The RAS info on the server shows no ports as
being used, however, like it would when a Win2k client
connects.
Any ideas?
recently, Windows XPP laptops in the field were able to
connect to the Internet via any method and then connect
via VPN to the above server.
As of recent, Windows XPP machines have not been able to
get a valid IP address from our normal scope
(192.168.1.150-199) and are instead being assigned
169.254.216.0-255 IP addresses (APIPA?) with a different
gateway.
Client with Windows 2000 in the field are not having this
problem.
The PCs in question are connecting to the Internet and
are indeed authenticating across the VPN... according to
the client. The RAS info on the server shows no ports as
being used, however, like it would when a Win2k client
connects.
Any ideas?