CE 3.0 Dual NIC's Problem - NDIS Adapter Order Changes

Hi,

I know, CE 3.0 is ancient history, but I have a problem with a CEPC system
that has two Ethernet Adapters. One adapter is connected to a factory
network and the other is connected to Ethernet devices on the machine which
the CE system is controlling.

The system has the ability to store the registry to DiskOnChip. It does a
dual boot on startup to use the stored registry. The problem I have is that
saving the registry reverses the order in which the adapters are registered
with NDIS. I think I'm correct here because when I do "ipconfig /all", the
Adapter Indexes have reversed. As a result, CE wants to use the wrong
adapter for "net use". Instead, it tries to use the adapter connected to
the ethernet devices on the machine. While registry saves are not done
frequently, when they are the customer's machine is down and production is
lost.

I'm looking for suggestions on how to deal with this. I've thought about
eliminating the dual boot/saved registry and running an application on boot
that modifies the registry as needed. A potential problem with that is that
the factory network NIC's IP address differs from customer to customer. If
I have to wait for the DiskOnChip to be accessible to my application, the IP
address in the original registry entry may have been used.

Any suggestions would be most welcome. We are planning an upgrade to CE 5.0
on these machines, but the user interface was done in eVB and needs to be
rewritten. In the meantime, our customers want a fix.

Thanks,

Jim Frazer


.

Relevant Pages

  • Re: setting IP address without using control panel
    ... WMI methods born to set/query ... the IPCONFIG still returned nothing. ... >>> just writing some registry keys. ... all adapter information is gone completely. ...
    (microsoft.public.win32.programmer.networks)
  • Re: Programmatically setting static IPv6 address in Winodws CE
    ... The registry keys for IPv6 ... Set the registry settings and rebind the network adapter. ...
    (microsoft.public.windowsce.embedded)
  • Re: NDISWAN TCPIP Event Error 4191 - Stack Problems
    ... Will the netsh command work in Windows 2000 Server? ... ndiswanip registry entry. ... IP could not open the registry key for adapter ...
    (microsoft.public.windows.server.networking)
  • RE: Registry explanation of ghosted network adapters
    ... NoteID for Adapter is the network adapter that TCP/IP is bound to. ... It appears that each individual network adapter has a unique PNPInstanceID ... The reason I ask is because server "a" is configured now with a NIC with MAC ... - I do not have to remove the ghost adapter from the registry because I want ...
    (microsoft.public.windows.server.networking)
  • Re: How to set IP address, subnet mask, default gateway for an adapter
    ... To find the correct key you can use a ... combination of IP Helper and Registry Access. ... I am trying to programmatically setup an IP adapter (static IP, ... > gateway, DNS server, alt DNS server, WINS server, alt WINS server ...
    (microsoft.public.pocketpc.developer)