Re: TCP/IP properties page
- From: "george" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 20 Apr 2005 17:43:55 +0200
Actually Mike,
It is the other way around.
Imagine if you will, the more or less 'standard' way of using machines
(laptops notably) in a company environment and being allowed to take it home
to do 'distance-working' or other stuff.
In companies it is very common to use automatically assigned IP addresses
via DHCP, so the network card would be configured as such.
Now comes the problem.
You're at home and that company-DHCP server is no good to you for your home
network, so you won't get an address assigned then.
In comes the 'alternate' possibility.
Here's where you would define your 'home-network-address' and all would be
well in both locations, company and home, without you having to muck about
with re-configuration of the TCP/IP stack, depending on the location you
happen to be in.
Don't forget, MS built this stuff with companie-setups in mind and not
necessarily the individual home-user's one.
george
"Mike Hyndman" <mike@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:p3qc61d59n3lsevr6hh9tiqhgn4kp1l0ib@xxxxxxxxxx
>
>
> Thanks again George
> You got it!though why two pages are required for alternate TCP/IP
> configs when set to Auto is a mystery. It would seem more logical to
> have an alternate option when the first page is set to "specified", then
> for whatever reason (on a specified TCP/IP WiFi connection was not
> available for example) it would select the alternate "dynamic" page and
> configure accordingly.
>>unless I misunderstand you, one machine shows one property dialog because
>>it
>>is *not* set to 'automatically assigned';
>>the other is showinf two, because it *is* set to 'automatically assigned'.
>>The appearance of the second dialog box is 'dynamic', ie. when general is
>>set on 'automatic' the second one is there., otherwise it is not.
>>
>>hth ?
>>
>>george
>
> many thanks
> Mike H
>>
>
.
- Follow-Ups:
- Re: TCP/IP properties page
- From: Mike Hyndman
- Re: TCP/IP properties page
- References:
- TCP/IP properties page
- From: Mike Hyndman
- Re: TCP/IP properties page
- From: george
- Re: TCP/IP properties page
- From: Mike Hyndman
- Re: TCP/IP properties page
- From: george
- Re: TCP/IP properties page
- From: Mike Hyndman
- TCP/IP properties page
- Prev by Date: Re: home network
- Next by Date: Re: Error 501
- Previous by thread: Re: TCP/IP properties page
- Next by thread: Re: TCP/IP properties page
- Index(es):
Relevant Pages
|