alternate IP configuration bug?

  • Thread starter Thread starter mister.jones
  • Start date Start date
M

mister.jones

Hi! I have a peculiar problem with my workplace network. It is not a DHCP,
so in the wireless adapter IP settings I have manually entered the IP etc.
as an "alternate configuration". When first connecting to that network, I
get the appropriate address and everything is fine. But when I disconnect
somehow (leaving and returning, sleep mode, ...), I get an IP in the
169.254.x.x range, which of course does not work. The only way to reconnect
is either to restart the computer or to manually enter another IP address in
"alternate configuration". When I disconnect/reconnect the next time, I need
to enter a third (different) IP.
It seems that Vista somehow remembers the IP as taken and does not reissue
it to my adapter on a reconnect. Is there any remedy for this behavior?
Thanks!
mister.jones
 
Hello Jones,

Thank you for using newsgroup!

From your post, the following article may be helpful:
926180: When an IP address changes to a static IP address, a static IP
address and an alternate IP address remain on the network interface in
Windows Vista
http://support.microsoft.com/default.aspx?scid=kb;EN-US;926180

Thanks & Regards,

Ken Zhao

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.





--------------------
| From: "mister.jones" <[email protected]>
| Subject: alternate IP configuration bug?
| Date: Mon, 5 Feb 2007 02:04:32 +0100
| Lines: 14
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-1";
| reply-type=original
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Windows Mail 6.0.6000.16386
| X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
| X-MS-CommunityGroup-MessageCategory:
{E4FCE0A9-75B4-4168-BFF9-16C22D8747EC}
| X-MS-CommunityGroup-PostID: {E6747FC0-780A-4E93-B675-BADE17D30A8F}
| Newsgroups: microsoft.public.windows.vista.networking_sharing
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.networking_sharing:1206
| NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| X-Tomcat-NG: microsoft.public.windows.vista.networking_sharing
|
| Hi! I have a peculiar problem with my workplace network. It is not a
DHCP,
| so in the wireless adapter IP settings I have manually entered the IP
etc.
| as an "alternate configuration". When first connecting to that network, I
| get the appropriate address and everything is fine. But when I disconnect
| somehow (leaving and returning, sleep mode, ...), I get an IP in the
| 169.254.x.x range, which of course does not work. The only way to
reconnect
| is either to restart the computer or to manually enter another IP address
in
| "alternate configuration". When I disconnect/reconnect the next time, I
need
| to enter a third (different) IP.
| It seems that Vista somehow remembers the IP as taken and does not
reissue
| it to my adapter on a reconnect. Is there any remedy for this behavior?
| Thanks!
| mister.jones
|
|
 
Hi Ken! Thanks for your quick reply.
If I understand correctly, each time I want to connect to that network, I
have to manually clear all IP settings and enter the static IP of my
workplace network? So, having an automatic configuration with DHCP enabled
and an "alternate configuration" with static IP is not working? Will there
be a patch soon?
Actually, I think the article you gave me is not 100% describing my problem,
because instead of remaining wih the alternate IP address, Vista issues a
private IP (169.254.x.x) after the first disconnect to the DHCP-less network
(but it takes the correct settings for Gateway and DNS).
Thanks for your help
Thomas Jones




"Ken Zhao [MSFT]" said:
Hello Jones,

Thank you for using newsgroup!

From your post, the following article may be helpful:
926180: When an IP address changes to a static IP address, a static IP
address and an alternate IP address remain on the network interface in
Windows Vista
http://support.microsoft.com/default.aspx?scid=kb;EN-US;926180

Thanks & Regards,

Ken Zhao

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.





--------------------
| From: "mister.jones" <[email protected]>
| Subject: alternate IP configuration bug?
| Date: Mon, 5 Feb 2007 02:04:32 +0100
| Lines: 14
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-1";
| reply-type=original
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Windows Mail 6.0.6000.16386
| X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
| X-MS-CommunityGroup-MessageCategory:
{E4FCE0A9-75B4-4168-BFF9-16C22D8747EC}
| X-MS-CommunityGroup-PostID: {E6747FC0-780A-4E93-B675-BADE17D30A8F}
| Newsgroups: microsoft.public.windows.vista.networking_sharing
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.networking_sharing:1206
| NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| X-Tomcat-NG: microsoft.public.windows.vista.networking_sharing
|
| Hi! I have a peculiar problem with my workplace network. It is not a
DHCP,
| so in the wireless adapter IP settings I have manually entered the IP
etc.
| as an "alternate configuration". When first connecting to that network,
I
| get the appropriate address and everything is fine. But when I
disconnect
| somehow (leaving and returning, sleep mode, ...), I get an IP in the
| 169.254.x.x range, which of course does not work. The only way to
reconnect
| is either to restart the computer or to manually enter another IP
address
in
| "alternate configuration". When I disconnect/reconnect the next time, I
need
| to enter a third (different) IP.
| It seems that Vista somehow remembers the IP as taken and does not
reissue
| it to my adapter on a reconnect. Is there any remedy for this behavior?
| Thanks!
| mister.jones
|
|
 
From your post "...Vista issues a private IP (169.254.x.x) after the first
disconnect to the DHCP-less network... ".
If you have auto configuration checked each time the computer starts and
does not "find" a DHCP source private IPs are assigned to both initial and
alternate configuration settings.
You state "...have a peculiar problem with my workplace network. It is not a
DHCP, ...". If DHCP is not being provided why is auto configuration
selected and why are you using the alternate configuration setting and not
the settings in the "General" dialogue box?
 
From your post "...Vista issues a private IP (169.254.x.x) after the first
disconnect to the DHCP-less network... ".
If you have auto configuration checked each time the computer starts and
does not "find" a DHCP source private IPs are assigned to both initial
and alternate configuration settings.

On the "alternate configuration" tab, you can choose between "automatic,
private IP" and "user defined IP". I need "user defined".
You state "...have a peculiar problem with my workplace network. It is not
a DHCP, ...". If DHCP is not being provided why is auto configuration
selected and why are you using the alternate configuration setting and not
the settings in the "General" dialogue box?

Did I mention, this is a laptop with WLAN. Generally, I connect with DHCP.
Only when I am at work, I need to use the fixed IP. As this usually happens
each day, I don't want to manually enter the whole config each morning.
 
Hi Thomas,

Does the article help to resolve the issue?

Thanks & Regards,

Ken Zhao

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.





--------------------
| From: "mister.jones" <[email protected]>
| References: <[email protected]>
<[email protected]>
| In-Reply-To: <[email protected]>
| Subject: Re: alternate IP configuration bug?
| Date: Mon, 5 Feb 2007 19:49:42 +0100
| Lines: 98
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-1";
| reply-type=original
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Windows Mail 6.0.6000.16386
| X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
| X-MS-CommunityGroup-PostID: {3A129CCC-FD86-4499-8B2C-C63967162F02}
| X-MS-CommunityGroup-ThreadID: E6747FC0-780A-4E93-B675-BADE17D30A8F
| X-MS-CommunityGroup-ParentID: AE02AE1D-CD90-4439-9E63-0831BEC5F80E
| Newsgroups: microsoft.public.windows.vista.networking_sharing
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.networking_sharing:1259
| NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| X-Tomcat-NG: microsoft.public.windows.vista.networking_sharing
|
| Hi Ken! Thanks for your quick reply.
| If I understand correctly, each time I want to connect to that network, I
| have to manually clear all IP settings and enter the static IP of my
| workplace network? So, having an automatic configuration with DHCP
enabled
| and an "alternate configuration" with static IP is not working? Will
there
| be a patch soon?
| Actually, I think the article you gave me is not 100% describing my
problem,
| because instead of remaining wih the alternate IP address, Vista issues a
| private IP (169.254.x.x) after the first disconnect to the DHCP-less
network
| (but it takes the correct settings for Gateway and DNS).
| Thanks for your help
| Thomas Jones
|
|
|
|
| | > Hello Jones,
| >
| > Thank you for using newsgroup!
| >
| > From your post, the following article may be helpful:
| > 926180: When an IP address changes to a static IP address, a static IP
| > address and an alternate IP address remain on the network interface in
| > Windows Vista
| > http://support.microsoft.com/default.aspx?scid=kb;EN-US;926180
| >
| > Thanks & Regards,
| >
| > Ken Zhao
| >
| > Microsoft Online Partner Support
| > Get Secure! - www.microsoft.com/security
| >
| > =====================================================
| > When responding to posts, please "Reply to Group" via your newsreader so
| > that others may learn and benefit from your issue.
| > =====================================================
| > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| >
| >
| >
| >
| >
| > --------------------
| > | From: "mister.jones" <[email protected]>
| > | Subject: alternate IP configuration bug?
| > | Date: Mon, 5 Feb 2007 02:04:32 +0100
| > | Lines: 14
| > | Message-ID: <[email protected]>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | format=flowed;
| > | charset="iso-8859-1";
| > | reply-type=original
| > | Content-Transfer-Encoding: 7bit
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Windows Mail 6.0.6000.16386
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
| > | X-MS-CommunityGroup-MessageCategory:
| > {E4FCE0A9-75B4-4168-BFF9-16C22D8747EC}
| > | X-MS-CommunityGroup-PostID: {E6747FC0-780A-4E93-B675-BADE17D30A8F}
| > | Newsgroups: microsoft.public.windows.vista.networking_sharing
| > | Path: TK2MSFTNGHUB02.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl
| > microsoft.public.windows.vista.networking_sharing:1206
| > | NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| > | X-Tomcat-NG: microsoft.public.windows.vista.networking_sharing
| > |
| > | Hi! I have a peculiar problem with my workplace network. It is not a
| > DHCP,
| > | so in the wireless adapter IP settings I have manually entered the IP
| > etc.
| > | as an "alternate configuration". When first connecting to that
network,
| > I
| > | get the appropriate address and everything is fine. But when I
| > disconnect
| > | somehow (leaving and returning, sleep mode, ...), I get an IP in the
| > | 169.254.x.x range, which of course does not work. The only way to
| > reconnect
| > | is either to restart the computer or to manually enter another IP
| > address
| > in
| > | "alternate configuration". When I disconnect/reconnect the next time,
I
| > need
| > | to enter a third (different) IP.
| > | It seems that Vista somehow remembers the IP as taken and does not
| > reissue
| > | it to my adapter on a reconnect. Is there any remedy for this
behavior?
| > | Thanks!
| > | mister.jones
| > |
| > |
| >
|
|
 
Sorry, Ken, no it does not. The article tells me to remove IP settings and
configure a static IP address.
I need, however, DHCP usally and static only when at work (alternate
configuration).

Although the configuration is entered correctly, Vista issues the fixed IP
only on the first connect after a reboot. On the second connect it issues a
private IP 169.254.x.x, which it shouldn't. This is obviously a bug.

(My workaround - because I did not want to reboot every day - was to enter a
second static IP. This works once, then I need a third one, etc. It seems
that Vista internally remembers these IPs as already in use, until the next
reboot.)

Best regards
Thomas
 
Hi Thomas,

Thanks for your efforts and let us know your current situation. Actually,
this is a problem that our proper department is investigating this problem.

I do understand your concerns. From my point of view, I understand your
feeling and how frustrated when you find that our product cannot meet your
needs. So, it is my pleasure to help you to reflect your recommendation to
the proper department for their consideration.

In addition, please feel free to submit your suggestion on our product to
the following link. Our Product Group reviews the suggestions submitted by
our customers. Your feedback is valuable for us to improve our products and
increase the level of service provided.

https://support.microsoft.com/common/survey.aspx?scid=sw;en;1208&showpage=1&
ws=search

Thanks you for your support for our new products.

Thanks & Regards,

Ken Zhao

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.





--------------------
| From: "mister.jones" <[email protected]>
| References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
| In-Reply-To: <[email protected]>
| Subject: Re: alternate IP configuration bug?
| Date: Thu, 8 Feb 2007 13:48:02 +0100
| Lines: 95
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-1";
| reply-type=original
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Windows Mail 6.0.6000.16386
| X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.windows.vista.networking_sharing
| NNTP-Posting-Host: liege-1-1-193-58.adsl.hyperline.be 85.234.193.58
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.networking_sharing:1470
| X-Tomcat-NG: microsoft.public.windows.vista.networking_sharing
|
| Sorry, Ken, no it does not. The article tells me to remove IP settings
and
| configure a static IP address.
| I need, however, DHCP usally and static only when at work (alternate
| configuration).
|
| Although the configuration is entered correctly, Vista issues the fixed
IP
| only on the first connect after a reboot. On the second connect it issues
a
| private IP 169.254.x.x, which it shouldn't. This is obviously a bug.
|
| (My workaround - because I did not want to reboot every day - was to
enter a
| second static IP. This works once, then I need a third one, etc. It seems
| that Vista internally remembers these IPs as already in use, until the
next
| reboot.)
|
| Best regards
| Thomas
|
|
| > Hi Thomas,
| >
| > Does the article help to resolve the issue?
| >
| > Thanks & Regards,
| >
| > Ken Zhao
| >
| > |
| > | Hi Ken! Thanks for your quick reply.
| > | If I understand correctly, each time I want to connect to that
network,
| > I
| > | have to manually clear all IP settings and enter the static IP of my
| > | workplace network? So, having an automatic configuration with DHCP
| > enabled
| > | and an "alternate configuration" with static IP is not working? Will
| > there
| > | be a patch soon?
| > | Actually, I think the article you gave me is not 100% describing my
| > problem,
| > | because instead of remaining wih the alternate IP address, Vista
issues
| > a
| > | private IP (169.254.x.x) after the first disconnect to the DHCP-less
| > network
| > | (but it takes the correct settings for Gateway and DNS).
| > | Thanks for your help
| > | Thomas Jones
| > |
| > | > Hello Jones,
| > | >
| > | > Thank you for using newsgroup!
| > | >
| > | > From your post, the following article may be helpful:
| > | > 926180: When an IP address changes to a static IP address, a static
IP
| > | > address and an alternate IP address remain on the network interface
in
| > | > Windows Vista
| > | > http://support.microsoft.com/default.aspx?scid=kb;EN-US;926180
| > | >
| > | > Thanks & Regards,
| > | >
| > | > Ken Zhao
| > | >
| > | > |
| > | > | Hi! I have a peculiar problem with my workplace network. It is
not a
| > | > DHCP,
| > | > | so in the wireless adapter IP settings I have manually entered
the
| > IP
| > | > etc.
| > | > | as an "alternate configuration". When first connecting to that
| > network,
| > | > I
| > | > | get the appropriate address and everything is fine. But when I
| > | > disconnect
| > | > | somehow (leaving and returning, sleep mode, ...), I get an IP in
the
| > | > | 169.254.x.x range, which of course does not work. The only way to
| > | > reconnect
| > | > | is either to restart the computer or to manually enter another IP
| > | > address
| > | > in
| > | > | "alternate configuration". When I disconnect/reconnect the next
| > time,
| > I
| > | > need
| > | > | to enter a third (different) IP.
| > | > | It seems that Vista somehow remembers the IP as taken and does not
| > | > reissue
| > | > | it to my adapter on a reconnect. Is there any remedy for this
| > behavior?
| > | > | Thanks!
| > | > | mister.jones
| > | > |
| > | > |
| > | >
| > |
| > |
| >
|
|
 
| From: "mister.jones" <[email protected]>

PMFJI...
| I need, however, DHCP usally and static only when at work (alternate
| configuration).
| Although the configuration is entered correctly, Vista issues the fixed
IP only on the first connect after a reboot. On the second connect it issues
a private IP 169.254.x.x, which it shouldn't. This is obviously a bug.

XP and Vista fall back to that address range as a self-asigned one,
when no DHCP server is found ("limited connectivity" etc.).

So to hold a static IP, you'd want to prevent Vista from looking for a
DHCP server that isn't there. I'm not too sure how the logic works,
i.e. whether Vista will fall back from the "front" DHCP settings to
the "alternate" fixed-IP. It may also be confounded by a gateway IP
that persists, so that Vista asks the gateway for an IP, doesn't get
it, and then falls back to "limited connectivity" instead of static IP
| (My workaround - because I did not want to reboot every day - was to
enter a second static IP. This works once, then I need a third one, etc.
It seems that Vista internally remembers these IPs as already in use, until
the next reboot.)

Ahh... that could be a different kind of bug ;-)

I often wonder if PCs see themselves as if they were different PCs on
the same LAN, when the same PC has different IP addresses. If so,
then it may not assign the same static IP as it could clash with what
is assumed to be another PC on the LAN that may not be running or
plugged in yet. You can see the problem there.

There's another issue with alternate IP, and that is where the PC is
reached by name (as SQL services sometimes use), then the name is
mapped only to one of the multiple alternative assignments.

A cheap fix may be to add a second network adapter and set each
adapter to different IP strategies. May be cheaper than butting your
head against it for days on end :-)


--------------- ---- --- -- - - - -
Saws are too hard to use.
Be easier to use!
 
PMFJI...
Sure.
XP and Vista fall back to that address range as a self-asigned one,
when no DHCP server is found ("limited connectivity" etc.).
Yep, that is, when you have selected "automatically assigned, private
IP-address" on the "alternate configuration" tab. Then, a private address in
the 169.254.x.x range is and sould be assigned. If you enter a static
address instead, this one is selected. This worked fine under XP. Under
Vista, this works only on the first connect after a reboot. (This is a
laptop, so I move around, so there is more than one connect.) On the second
connect, Vista assigns a private address.
A cheap fix may be to add a second network adapter and set each
adapter to different IP strategies. May be cheaper than butting your
head against it for days on end :-)
An even cheaper fix would have been not to install Vista at all....
(Sorry, but I am a bit frustrated with all these Vista bugs and driver
problems.)

And, thanks Ken Zhao for bringing this issue to the attention of the
programmers.
 
On Tue, 13 Feb 2007 01:25:33 +0100, "mister.jones"
Yep, that is, when you have selected "automatically assigned, private
IP-address" on the "alternate configuration" tab. Then, a private address in
the 169.254.x.x range is and sould be assigned. If you enter a static
address instead, this one is selected. This worked fine under XP.

Just to be clear...
- primary settings are to assign a fixed IP
- alternate settings are to auto-assign
....or have I got these the wrong way round?
Vista, this works only on the first connect after a reboot. (This is a
laptop, so I move around, so there is more than one connect.) On the second
connect, Vista assigns a private address.

I'd look for something in the /kb about address retention, i.e. how
long Vista may "remember" an IP is in use before allowing it to be
used again. It may be part of a strategy to avoid this sort of thing:
- a certain private address range is used, e.g. 192.168.0.x
- a DHCP server serves 192.168.0.100-200
- some PCs on the LAN have fixed IP in same range
- in particular, one PC is set to use 192.168.0.103
- that PC is switched off when you power up
- you get assigned 192.168.0.103 via DHCP
- the PC fixed to 192.168.0.103 powers up, and... . . . .
An even cheaper fix would have been not to install Vista at all....
(Sorry, but I am a bit frustrated with all these Vista bugs and driver
problems.)

Heh, understood, but even in best-case conditions (you upgrade from XP
to Vista, you maintained an Undo, you've done no work or installations
since starting in Vista) there's prolly more time spent in falling
back from Vista to XP than adding an extra LAN card to Vista.

With that in mind, it depends on what your time is worth.

With two LAN cards, you should be able to fix the IP for the one card
and have it float on the other. By choosing which to plug into, you'd
know exactly what you're getting.

With a laptop, it's slightly costlier (tho PCMCIA LAN cards are
cheaper now) but if you're "legacy free" (no PC Card slot) it's ugly.


--------------- ---- --- -- - - - -
Saws are too hard to use.
Be easier to use!
 
Thanks

Ken Zhao

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
| From: "cquirke (MVP Windows shell/user)" <[email protected]>
| Subject: Re: alternate IP configuration bug?
| Date: Tue, 13 Feb 2007 20:48:34 +0200
| Reply-To: (e-mail address removed)
| Message-ID: <[email protected]>
| References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
| X-Newsreader: Forte Free Agent 2.0/32.646
| MIME-Version: 1.0
| Content-Type: text/plain; charset=us-ascii
| Content-Transfer-Encoding: 7bit
| Newsgroups: microsoft.public.windows.vista.networking_sharing
| NNTP-Posting-Host: dsl-240-65-105.telkomadsl.co.za 41.240.65.105
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.networking_sharing:1853
| X-Tomcat-NG: microsoft.public.windows.vista.networking_sharing
|
| On Tue, 13 Feb 2007 01:25:33 +0100, "mister.jones"
|
| >> XP and Vista fall back to that address range as a self-asigned one,
| >> when no DHCP server is found ("limited connectivity" etc.).
|
| >Yep, that is, when you have selected "automatically assigned, private
| >IP-address" on the "alternate configuration" tab. Then, a private
address in
| >the 169.254.x.x range is and sould be assigned. If you enter a static
| >address instead, this one is selected. This worked fine under XP.
|
| Just to be clear...
| - primary settings are to assign a fixed IP
| - alternate settings are to auto-assign
| ...or have I got these the wrong way round?
|
| >Vista, this works only on the first connect after a reboot. (This is a
| >laptop, so I move around, so there is more than one connect.) On the
second
| >connect, Vista assigns a private address.
|
| I'd look for something in the /kb about address retention, i.e. how
| long Vista may "remember" an IP is in use before allowing it to be
| used again. It may be part of a strategy to avoid this sort of thing:
| - a certain private address range is used, e.g. 192.168.0.x
| - a DHCP server serves 192.168.0.100-200
| - some PCs on the LAN have fixed IP in same range
| - in particular, one PC is set to use 192.168.0.103
| - that PC is switched off when you power up
| - you get assigned 192.168.0.103 via DHCP
| - the PC fixed to 192.168.0.103 powers up, and... . . . .
|
| >> A cheap fix may be to add a second network adapter and set each
| >> adapter to different IP strategies. May be cheaper than butting your
| >> head against it for days on end :-)
|
| >An even cheaper fix would have been not to install Vista at all....
| >(Sorry, but I am a bit frustrated with all these Vista bugs and driver
| >problems.)
|
| Heh, understood, but even in best-case conditions (you upgrade from XP
| to Vista, you maintained an Undo, you've done no work or installations
| since starting in Vista) there's prolly more time spent in falling
| back from Vista to XP than adding an extra LAN card to Vista.
|
| With that in mind, it depends on what your time is worth.
|
| With two LAN cards, you should be able to fix the IP for the one card
| and have it float on the other. By choosing which to plug into, you'd
| know exactly what you're getting.
|
| With a laptop, it's slightly costlier (tho PCMCIA LAN cards are
| cheaper now) but if you're "legacy free" (no PC Card slot) it's ugly.
|
|
|
| >--------------- ---- --- -- - - - -
| Saws are too hard to use.
| Be easier to use!
| >--------------- ---- --- -- - - - -
|
 
I have the same problem. very annoying. xp worked fine.
Now I use this program to avoid typing manually the static ip address:
www.netsetman.com
great piece of software, vista developper should get inspired.
 
Back
Top