Unfortnately this is not a typical workstation. It is a touchscreen
terminal with an odd form factor, and its integrated PCI NIC is no
longer functioning. I have not been able to source a replacement part
so I opted for the USB NIC as a workaround.
I've spent most of today searching online. There seem to be some
reports of similar problems with wireless ethernet adapters and
description of the problem in the article summary but it fails to
provide a specific solution to my problem. I have tried variously
making the Netlogon, Lanmanworkstation, and TCPIP services dependent
on the USB200M driver in separate tests, to no avail. Checking the
bootlog reveals that the NIC driver is loaded in the same order in
each of these tests.
The only way I've yet been able to make the driver load sooner in the
boot process was by changing the registry value
I changed it from a value of 3 (Manual) to 0 (SERVICE_BOOT_START) as
described at http://www.yqcomputer.com/
revealed that the driver was loaded much sooner at bootup but this did
not seem to affect things as the problem retrieving the roaming user
I've reviewed the workstation's event log and tcpip reports that the
USB NIC has connected to the network but 16 seconds later, netlogon
reports that there are no domain controllers for the network.
Curiously, this tcpip event message appears AFTER the netlogon error
in the event list but is timestamped as having occured 16 seconds
than the netlogon error. This leads me to believe that while the
detection/loading of the USB NIC may have begun before the reported
netlogon error, is is only after the error that this NIC detection/
loading process completes and writes the event to the event log. Am I
on to something here? Any thoughts?
On Sep 14, 12:58 pm, DanielWalters6