DHCP/Alternate Static IP

[Guest]

I'm trying to setup a laptop to work with a DHCP for remote locations and a
static IP for in the office. It is connected to the network but does not see
the static IP instead it assigns itself a bogus DHCP ip. I've tried
IPAutoconfiguartionEnabled to 0 in the registry, but that didn't work. Any
ideas. Thanks.

 

[Al Romanosky]

What is the "bogus" IP address?

 

[Guest]

192.168.x.x The laptop is assigning it.

 

[Newtechie]

Hi Al,

Bogus means fake.

Newtechie

 

[Newtechie]

RJC,

You could go in the properties of the NIC, and type in the information. On
the general tab, check the "use the following address". Here you type the
IP address, subnet mask and default gateway. Also at the bottom of that
same tab, check the "use the following DNS server addresses". All that info
can be obtained from doing a start---run---cmd---ipconfig /all.

Hope this helps.

Newtechie

 

[Guest]

Right I'm clear on how to assign a static ip, my problem is that I'm trying
to switch between DHCP and a static IP. When I'm connected into the network
that uses the static IP, the DHCP on the laptop assigns itself a bogus
addresses and does not use nor see the static IP. I thought the whole idea
of of an alternate configuration on a nic is to be able to switch between
the DHCP and static ip based on what the system found upon boot. Thanks

 

[Newtechie]

Ok - I see what you're saying, but maybe that's how the remote locations are
set up because
you are on someone else's network. This is just a guess as I'm not certain
so I can't give you a
better solution. Try the newsgroup microsoft.public.windowsxp.network_web.
I'm sure someone
there will have the answer. Steve Winograd, Chuck, and TimH give excellent
feedback.

Newtechie

Right I'm clear on how to assign a static ip, my problem is that I'm
trying
to switch between DHCP and a static IP. When I'm connected into the
network
that uses the static IP, the DHCP on the laptop assigns itself a bogus
addresses and does not use nor see the static IP. I thought the whole
idea
of of an alternate configuration on a nic is to be able to switch between
the DHCP and static ip based on what the system found upon boot. Thanks

RJC,

You could go in the properties of the NIC, and type in the information.
On
the general tab, check the "use the following address". Here you type
the
IP address, subnet mask and default gateway. Also at the bottom of that
same tab, check the "use the following DNS server addresses". All that
info
can be obtained from doing a start---run---cmd---ipconfig /all.

Hope this helps.

Newtechie

 

[Guest]

Thanks, for the web site, I'll try there too. I'm on my network with the
static IP-and we don't have any DHCP here to interfere. THis machine based
on the what the documentation says should use the static ip since that is the
network it is plugged into. THe DHCP should just time out and the static ip
take over, but it is not. It is assigning a bogus IP and not going to the
static ip at all. RJC

Ok - I see what you're saying, but maybe that's how the remote locations are
set up because
you are on someone else's network. This is just a guess as I'm not certain
so I can't give you a
better solution. Try the newsgroup microsoft.public.windowsxp.network_web.
I'm sure someone
there will have the answer. Steve Winograd, Chuck, and TimH give excellent
feedback.

Newtechie

Right I'm clear on how to assign a static ip, my problem is that I'm
trying
to switch between DHCP and a static IP. When I'm connected into the
network
that uses the static IP, the DHCP on the laptop assigns itself a bogus
addresses and does not use nor see the static IP. I thought the whole
idea
of of an alternate configuration on a nic is to be able to switch between
the DHCP and static ip based on what the system found upon boot. Thanks

 

[Al Romanosky]

First - Assuming TCP/IP properties are set to obtain "address
automatically" - General tab set for auto - click alternate tab and set user
configure address. You are correct in assuming that in the absence of a
DHCP auto assigned address the alternate configuration becomes operational.
However it appears you have and active DHCP and which is assigning a correct
address (192.168.0.0) and is not a "bogus" (My opinion) address.

 

[Al Romanosky]

My question was not for the definition of "bogus" - It was "What IS the
bogus IP address" - fortunately RJC understood the question.