DHCP Enabled = No, Autoconfirguration IP Address

[nickolsen]

We have a VPN setup on one of our Windows 2003 servers out in Texas and I am in California. It is a simple VPN connection setup where you VPN directly into the server, there is not a separate server or separate NIC that handles the VPN traffic. The server does not handle then DHCP but rather a Linksys router. We connect using a url from dyndns.org which is associated with the router onsite.

Everything worked great until yesterday and for some reason I can connect but I keep getting autoconfiguration (169.X.X.X) IP addresses from windows and ipconfig says DHCP is disabled. Here is the ipconfig /all when connected to the VPN (I can verify my username and password and connect to the VPN without a problem, but I just get the autoconfig ip address so can do nothing with the connection)

Windows IP Configuration

Host Name . . . . . . . . . . . . : win-l-nickolsen
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : oc.cox.net

PPP adapter Bluffs:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluffs
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.0.61(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.2.250
NetBIOS over Tcpip. . . . . . . . : Enabled


Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : oc.cox.net
Description . . . . . . . . . . . : Dell Wireless 1505 Draft 802.11n WLAN Min
i-Card
Physical Address. . . . . . . . . : 00-1C-26-20-DA-9D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::dcc9:76e9:44f8:ecdc%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, March 20, 2009 7:44:22 AM
Lease Expires . . . . . . . . . . : Saturday, March 21, 2009 7:44:22 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 68.105.28.11
68.105.29.11
68.105.28.12
NetBIOS over Tcpip. . . . . . . . : Enabled

I checked the VPN connection properties and I have the Obtatin IP Address automatically selected for both the TCP/IP IPv4 and TCP/IP IPv6 protocols. We have another office in Texas and the workers from there are able to connect and receive DHCP IP address perfectly.

I have deleted the VPN connection within Windows and recreated it and it worked once, but never again. I tried deleting it again and recreating but it didn't work.

Any ideas?

Thanks

Nick

 

[nickolsen]

EDIT:

I realized that both the router onsite in Texas and my home router had the same IP address of 192.168.1.1 and they were both assigning DHCP IP Address starting at the range 192.168.1.100. I already had address 192.168.1.100 from my home router and the office router was trying to give me the same address. So, I changed my home router IP address to 192.168.10.1 so I wouldn't get the same IP address and everything is working without a hitch right now. Would this cause the problem and have I probably found a solution? If so, I assume that the previous times it has worked I never have gotten assigned the same address from both networks and so it has worked?