Vista loses IP config when undocking

used to use ThinkVantage's Access Connections to manage my network connection profiles on my Thinkpad. I just recently uninstalled it because I decided to just rely on the Vista has natively.

Since our office requires static IP, I set that up at the LAN properties.

Everything works fine when I start from a clean boot. It's when I undock and redock to the docking station that problem starts.

I lose the static IP configuration. Instead Vista assigns:
IP: 169.254.77.37 (supposed to be 10.11.2.xxx)
Subnet: 255.255.0.0 (supposed to be 255.255.254.0)
Gateway: blank
DNS: correct

I now find myself having to do a reboot everytime I just need to undock and go to a 30 minute meeting when I used to be able to undock and redock without any problems whatsoever.

Why does Vista assign this random IP when it is hard configured?

How can I solve this problem?

Thanks.

Are you performing the undock as described in Windows Vista Help: Dock or undock a mobile PC?

Yes I have been undocking redocking as specified by manufacturers and have not have had any problems with my IP config until I decided to not use the 3rd party connection profile and instead use Vista's.

The thing is, there really is no profile to manage. It's static IP. I've used Windows 95, NT, 2000, NT etc. The behavior is the same. If it's static, the OS remembers what you set. I really do not understand why Vista does not.

Any other suggestions or solutions?

johngalt said:

Are you performing the undock as described in Windows Vista Help: Dock or undock a mobile PC?

Click to expand...

Yes, but you are changing state. In a dock you're using *one* NIC and out of dock you're using another NIC, unless you're dock is not a full dock....

Honestly, have you set the 'alternate' config for the NIC? Set it to the same, and then it should 'change' to the same config upon docking / undocking - basically fooling Vista into using the same config regardless....

I understand the scenario you're describing but I have a scenario that would baffle you too:

1. dock. boot up. using docking station's NIC. everything perfect.
2. undock. DO NOT connect to any network. (so there shouldn't be any other NIC that Vista configures.)
3. redock. Vista cannot connect to network due to wrong IP.

it's static IP on 1 NIC. still baffles me

johngalt said:

Yes, but you are changing state. In a dock you're using *one* NIC and out of dock you're using another NIC, unless you're dock is not a full dock....

Honestly, have you set the 'alternate' config for the NIC? Set it to the same, and then it should 'change' to the same config upon docking / undocking - basically fooling Vista into using the same config regardless....

Click to expand...

Even though you do not connect to any other network, Vista recognizes that you have *disconnected* from the present network, and thus uses the settings in the alternate configuration to take over to try to keep a connection alive.

Unfortunately, for whatever reason, IPAPI is very tenacious and most times will not let go of the NIC once it takes over without (at the very least) a log out and log on, and usually forcing a reboot.

hence, my suggestion - change the alternate configuration settings to match those of your current settings - so that it will not attempt to change to an IPAPI assigned IP (169.254.xxx.xxx) and that should solve your problem.

Thanks for the help John. I really appreciate it.

I tried to implement your suggestion but I can't. Whenever I configure static IP for IPv4 properties in Vista, the option (button) to set alternative IP disappears.

I did have that scenario before: dynamic as default then alternative IP. but same symptoms on undock-redock.

When I tried to put identical IP configurations in advanced options of IPv4 properties, Vista recognizes the redundant IP and doesn't allow me to continue.

Any other solutions I could try? Thanks

johngalt said:

Even though you do not connect to any other network, Vista recognizes that you have *disconnected* from the present network, and thus uses the settings in the alternate configuration to take over to try to keep a connection alive.

Unfortunately, for whatever reason, IPAPI is very tenacious and most times will not let go of the NIC once it takes over without (at the very least) a log out and log on, and usually forcing a reboot.

hence, my suggestion - change the alternate configuration settings to match those of your current settings - so that it will not attempt to change to an IPAPI assigned IP (169.254.xxx.xxx) and that should solve your problem.

Click to expand...

Wow, that *is* ugly.

Have you tried logging out and back in, or else performing an after re-docking to see if it brings you back up to par? Although you are using static, so that really should not matter, but then again, since you are using static, when you undock it should not affect anything...

Does you dock have its own NIC also?

tried:

1. login - logout
2. ipconfig/release /renew
3. disable - enable LAN
4. repair
5. remove - replace cable

and nothing has worked but a reboot.

the dock has its own LAN port.

johngalt said:

Wow, that *is* ugly.

Have you tried logging out and back in, or else performing an

Code:

ipconfiog /renew

after re-docking to see if it brings you back up to par? Although you are using static, so that really should not matter, but then again, since you are using static, when you undock it should not affect anything...

Does you dock have its own NIC also?

Click to expand...

I resorted to the penultimate resort which is to reinstall Thinkvantage Access Connections which used to work before.

But it no longer works. Same problem.

Please help

gizzzo said:

tried:

1. login - logout
2. ipconfig/release /renew
3. disable - enable LAN
4. repair
5. remove - replace cable

and nothing has worked but a reboot.

the dock has its own LAN port.

johngalt said:

Wow, that *is* ugly.

Have you tried logging out and back in, or else performing an

Code:

ipconfiog /renew

after re-docking to see if it brings you back up to par? Although you are using static, so that really should not matter, but then again, since you are using static, when you undock it should not affect anything...

Does you dock have its own NIC also?

Click to expand...

Click to expand...