ethernet - IP

[Cedric Laloyaux]

Hi,

I have a laptop with win XP home and I am plugged to the
network at home and at my office. At home, no problem: I
configure in the TCP/IP "Obtain an IP automaticcally" and
that works fine. The matter is that at my office, I have
to use a fix IP and DNS, etc... So, every morning, I have
to re-enter all those digits which is wasting time. Does
anybody know if it's possible for windows XP to havee
both configurations in memory and that it detects which
one is suitable automatically?

Thanks,

Cedric Laloyaux
PS: don't hesitate to reply also by e-mail

 

[Christian Heckelmann]

In WinXP you can enter an alternativ ip config exactly for this problem.
In the IP Configration when it's configured for DHCP there is a second
tab where you can enter the values when the computer can't find a dhcp
server.

Sorry for my english ;-)

Christian Heckelmann

 

[Rob Schneider]

Hi,

I have a laptop with win XP home and I am plugged to the
network at home and at my office. At home, no problem: I
configure in the TCP/IP "Obtain an IP automaticcally" and
that works fine. The matter is that at my office, I have
to use a fix IP and DNS, etc... So, every morning, I have
to re-enter all those digits which is wasting time. Does
anybody know if it's possible for windows XP to havee
both configurations in memory and that it detects which
one is suitable automatically?

Thanks,

Cedric Laloyaux
PS: don't hesitate to reply also by e-mail

I've never set this up, so can't help you with details. Details in Help
anyway. Create a second hardware "profile" when connected at office.

question: why doesn't the office have DHCP running and available so
that you don't have to create an IP address setting there either? (DHCP
is what makes it automatic).

 

[NobodyMan]

I've never set this up, so can't help you with details. Details in Help
anyway. Create a second hardware "profile" when connected at office.

question: why doesn't the office have DHCP running and available so
that you don't have to create an IP address setting there either? (DHCP
is what makes it automatic).

Some WANs have LAN segments that can't use DHCP. I used to work at a
place separated from our PDCs by about three miles. Fiber ran from
the server farm to the main WAN routers, which jumped to another
router, then to us. We would have had to obtain our IP Leases from
the DHCP server installed on the Domain Controllers, but our LAN
administrator couldn't set this up as it was not a routable protocol.
So every one of our 200+ computers, on two subnets, had to be manually
configured with IPs, Primary/Secondary DNS addressees and
Primary/Secondary WINS addresses.

That's a lot of fun when you have to ghost all of the machines about
once every 6-8 months; nothing better than having to hit 200+ machines
and reset all the addresses.