NIC default settings

[Hartmut Engelke]

First, some background information:
In our XPe image we support a second network card. While all of these are
the same manufacturer with the same base model number (3COM-905xx), small
changes have been made over the years and the NICs are not exactly the same.
Under Windows NT, this was never a problem, the existing drivers worked for
all flavors of the network card. XP is more selective and if we install our
existing image (build with flavor A of the NIC) on a system with flavor B of
the NIC, XP creates a new Local Area Connection entry (#3) in the network
configuration.
Unfortunately XP is using some defaults that we would like different.

So here are the questions
1) Is there any way to convince XPe to use the existing Local Area
Connection 2 (with the correct configuration already set) instead of
creating a new one?

Since that is probably a no:
2) How does XP(e) determine which defaults to use? We would like to disable
NetBios over TCP/IP (a must) and possibly Client for Microsoft Networks.
a) is this information stored in the registry as a default template for all
network connections and can this template be configured through a component,
or
b) is this determined by settings in the NIF file of the NIC and what
changes would be required to change these defaults (well, if this is the
case I might need to post this in the networking group), or
c) an utility is required that modifies the configuration after XPe has
finalized the setup of the new network connection, or
d) none of the above, but....


Thanks in advance!

Hartmut

 

[Slobodan Brcin \(eMVP\)]

If you don't need NetBIOS then remove component "Netbios Driver" from your image.

For the rest read more about.
API "IP Helper Functions"
netsh.exe
net.exe

Best regards,
Slobodan

 

[KM]

Hartmut,

These threads may be interesting to you:
http://groups.google.com/groups?hl=...=1&[email protected]
http://groups.google.com/groups?hl=...=1&selm=OrmSwD#[email protected]
http://groups.google.com/groups?hl=...=1&[email protected]

 

[Hartmut Engelke]

We still need netbios for the first NIC, but will see if the other options
can help.

Thanks

 

[Doug Hoeffel]

Hartmut:

I had the exact problem since my XPe image is used on different versions of
the same motherboard with different rev. NIC chips. The problem with netsh
is that you have to know the exact interface name in order to do the
following:

netsh interface ip set address name="Local Area Connection X" source=static
addr=192.168.42.39 255.255.248.0 192.168.47.250 0

So, what I did is as follows and is a bit of a hack but it works:

1) I boot my HD on all flavors of mobo's so all the h/w is detected
2) Once I'm ready to deploy I delete all NIC devices via Device Manager
including the phantom devices. This does not clean-up the registry though.
3) I regedit and delete all GUID's under
[HKLM\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-0800
2BE10318}]
but leave
[HKLM\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-0800
2BE10318}\Descriptions]

The key is to delete the Connection - Name key per network GUID. Then once
I deploy then the h/w gets re-detected and the interface name is the same on
every box.

HTH... Doug