netsh, static IP, DHCP

"RemoteAccess" service is installed through the "Dial-up Server for
Windows". This drags in tapi, jet, mdac. Not as bad as pulling in MMC, but
it is a bump in size.
netsh now shows and set static ip addresses. There is still a message about
"SOme commands may not be available.", but the one of specific interest is
now working.


Looks like this would be another area for further XPe componentization.

"Jon Fincher (MS)" <jonfi_online@microsoft.com> wrote in message
news:Xns93A0A43B36137jonfiatmicrosoftdotc@157.54.3 .22...

> "Michael Larkin" <michael.larkin@wyatt.com> wrote in
> news:036c01c33517$de461280$a501280a@phx.gbl:
>

>
> Well - and this is just a wild stab in the dark - do you have the Remote
> Access components in your image as well?
>
> --
> --Jon, MS
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

I forgot to mention that "RemoteAccess" is installed "Disabled", so you need
to also be sure to install SC.Exe or such to get the config set to "auto".
"Richard Mahn" <RichardM@Entivity.Com> wrote in message
news:%23b$6PoIUDHA.3640@tk2msftngp13.phx.gbl...

> "RemoteAccess" service is installed through the "Dial-up Server for
> Windows". This drags in tapi, jet, mdac. Not as bad as pulling in MMC, but
> it is a bump in size.
> netsh now shows and set static ip addresses. There is still a message

about

> "SOme commands may not be available.", but the one of specific interest is
> now working.
>
>
> Looks like this would be another area for further XPe componentization.
>
> "Jon Fincher (MS)" <jonfi_online@microsoft.com> wrote in message
> news:Xns93A0A43B36137jonfiatmicrosoftdotc@157.54.3 .22...

>
>

is the Netsh for setting a static IP also working in Minlogon ? I get also
the error message 'interface name xyz is invalid'. Just adding the
Rasmontr.dll crashes Netsh.exe. Is there a solution without installing tons
of files for not needed RAS ?

"Richard Mahn" <RichardM@Entivity.Com> schrieb im Newsbeitrag
news:%233dOB6IUDHA.3192@tk2msftngp13.phx.gbl...

> I forgot to mention that "RemoteAccess" is installed "Disabled", so you

need

> to also be sure to install SC.Exe or such to get the config set to "auto".
> "Richard Mahn" <RichardM@Entivity.Com> wrote in message
> news:%23b$6PoIUDHA.3640@tk2msftngp13.phx.gbl...

but

> about

is

The Explorer shell names the network interface by default. If you're
running a shell other than Explorer, you will need to name the interface by
calling HrRenameConnection:

rundll32 netshell.dll HrRenameConnection

Verify that the connection is named (Local Area Connection, for example)
with the following command:

netsh interface ip show address


Now that the interface is named, you should be able to configure it with
netsh.

Thanks,
Dan


--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Johannes Stratmann" <-zz-jstratmann@t-online.de> wrote in message
news:OIutcXuUDHA.1512@TK2MSFTNGP11.phx.gbl...

> is the Netsh for setting a static IP also working in Minlogon ? I get also
> the error message 'interface name xyz is invalid'. Just adding the
> Rasmontr.dll crashes Netsh.exe. Is there a solution without installing

tons

> of files for not needed RAS ?
>
> "Richard Mahn" <RichardM@Entivity.Com> schrieb im Newsbeitrag
> news:%233dOB6IUDHA.3192@tk2msftngp13.phx.gbl...

> need

"auto".

> but

interest

> is

>
>

Thanks for your reply,
I have renamed the interface by using a script 'localnet.vbs' from Bernardo
Del Seno (Dibbe), included in the 'Netsetup' component on www.xpefiles.com
... When I check with 'netsh interface ip show address' then the interface
has the requested name. But I still get the 'invalid interface name' error.
I wll try your renaming method later.



"Dan Simpson [MS]" <dansimp@online.microsoft.com> schrieb im Newsbeitrag
news:3f2533c8$1@news.microsoft.com...

> The Explorer shell names the network interface by default. If you're
> running a shell other than Explorer, you will need to name the interface

by

> calling HrRenameConnection:
>
> rundll32 netshell.dll HrRenameConnection
>
> Verify that the connection is named (Local Area Connection, for example)
> with the following command:
>
> netsh interface ip show address
>
>
> Now that the interface is named, you should be able to configure it with
> netsh.

great, you won. After calling the HrRenameConnection it worked. The names
from the script were still kept, but the order (script uses the key order in
registry) seems to be quite random for multiple interfaces.
Is there any documentation on the HrRenameConnection function ?


"Dan Simpson [MS]" <dansimp@online.microsoft.com> schrieb im Newsbeitrag
news:3f2533c8$1@news.microsoft.com...

> The Explorer shell names the network interface by default. If you're
> running a shell other than Explorer, you will need to name the interface

by

> calling HrRenameConnection:
>
> rundll32 netshell.dll HrRenameConnection