Thanks George,
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.
where I work (under funded school 8-() the TCP/IP addresses are
specified, so there is only the general config page available.
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.
My WiFi router does just that. So when I come home I have to switch to
assign automatically, which then loses all the selected settings, very
useful, not! I could configure my home router similarly to my work's
setting I suppose, but it would mean changing the DNS server settings
every time I changed location.
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.
Still think it would be more useful to two config pages, one specified
and one dynamic.
Many thanks George for clearing things up.
Mike H