Vista loses IP config when undocking

I 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.

On Tue, 12 Aug 2008 04:09:15 -0700 (PDT), Gizzo <gbacareza@gmail.com>
wrote:

>I 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.

I'm sorry, but I don't have an answer for you. I use ThinkVantage's
Access Connections on my ThinkPad.

Perhaps Lenovo has modified the Vista operating system in a way that
we don't know about. I recommend either:

1. Re-installing that program.

2. Contacting Lenovo support for help.

3. Going to the Lenovo forum for your model:

http://forums.lenovo.com/lnv/
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Alas I wish it was as simple as reinstalling "Access Connections"
because I finally gave up and reinstalled it. It didn't work. Even
when I created a named profile in AC, whenever I apply it after a
redock, the same thing happens: Vista does not set the IP and subnet
mask though everything else is ok. I still have to reboot to get my IP
back. very very annoying and unproductive.

Something is definitely wrong either with the registries, the OS
itself or the adapter.

On Aug 15, 4:31*pm, Steve Winograd <bc0705...@comcast.net> wrote:
> On Tue, 12 Aug 2008 04:09:15 -0700 (PDT), Gizzo <gbacar...@gmail.com>
> wrote:
>
>
>
> >I 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.
>
> I'm sorry, but I don't have an answer for you. *I use ThinkVantage's
> Access Connections on my ThinkPad.
>
> Perhaps Lenovo has modified the Vista operating system in a way that
> we don't know about. *I recommend either:
>
> 1. Re-installing that program.
>
> 2. Contacting Lenovo support for help.
>
> 3. Going to the Lenovo forum for your model:
>
> * *http://forums.lenovo.com/lnv/
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see. *I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional Programhttp://mvp.support.microsoft.com

On Tue, 26 Aug 2008 09:17:01 -0700 (PDT), Gizzo <gbacareza@gmail.com>
wrote:
>> >I 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.
>>
>> I'm sorry, but I don't have an answer for you. *I use ThinkVantage's
>> Access Connections on my ThinkPad.
>>
>> Perhaps Lenovo has modified the Vista operating system in a way that
>> we don't know about. *I recommend either:
>>
>> 1. Re-installing that program.
>>
>> 2. Contacting Lenovo support for help.
>>
>> 3. Going to the Lenovo forum for your model:
>>
>> * *http://forums.lenovo.com/lnv/
>
>Alas I wish it was as simple as reinstalling "Access Connections"
>because I finally gave up and reinstalled it. It didn't work. Even
>when I created a named profile in AC, whenever I apply it after a
>redock, the same thing happens: Vista does not set the IP and subnet
>mask though everything else is ok. I still have to reboot to get my IP
>back. very very annoying and unproductive.
>
>Something is definitely wrong either with the registries, the OS
>itself or the adapter.

If you don't get an answer here, I recommend that you contact Lenovo
support for help or post your question in the appropriate Lenovo
forum.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

On Tue, 26 Aug 2008 18:18:05 -0600, Steve Winograd
<bc070521m@comcast.net> wrote:

>
>If you don't get an answer here, I recommend that you contact Lenovo
>support for help or post your question in the appropriate Lenovo
>forum.

Vista, unlike XP and 2000, has MAJOR issues when network conditions
change. For example, if you have a network card and a hard-wired
connection and try to switch between them, it will most always go
South. Or, if a piece of the network goes away (like a server) it will
also become unusable. Unlike XP & 2000, which dealt smoothly with such
matters, Vista just starts locking up processes and requires a reboot
- often a hard reboot since it will be too whacked to shutdown
normally.

I know some people who have had luck going into device manager (before
disconnecting or changing other network conditions) and disabling the
network card/connection, then changing the connection conditions
(undock for you) then restarting the network device afterwards.

Then again, I know some people who this has not worked at all for. You
might want to give it a try and see if it helps.