General discussion

Locked

Windows ME logon to NT Domain Problem

By cascomp ·
I?m having difficulty getting ME to log onto our NT domain. Many of our staff will be using laptop computers as their primary workstation. The laptop has a PCMCIA NIC card for when users are away from the office. When in the office, the laptop isin a docking station, which also has a NIC card. Windows seems to only utilize whichever NIC was the last to be installed when attempting to log onto our NT domain network.

The laptops are running Windows ME. Two hardware profiles exist, "dock1" and "undocked", and the PCMCIA card is disabled in the 'dock1' profile. Workstations are configured for dynamic IP. At startup, we initially log into an NT domain (NT 4) which then runs the logon scripts mapping drives etc.

As an example, the laptop is placed in the networked docking station and booted. The first prompt the user sees is the error "no domain server exists to verify your account" (not exact syntax). By acknowledging the error and canceling the password dialog, Windows starts up fine. Once booted, I can see that the laptop did get an IP address. I can browse the web and even see other systems on the domain. The only thing affected is logging into the NT domain. This seems to happen if the PCMCIA NIC was the last of the two NIC's configured and whether or not the PCMCIA NIC is physically in the laptop.

The reverse is also true, if the docking station NIC was last to be configured and the laptop is undocked and using the PCMCIA NIC, the same error occurs. (Yes, the NT domain parameters are set correctly). This 'last card installed' seems to be the more common scenario but may not be absolute. I have some laptops that will not log into the NT domain either docked or undocked without reinstalling either or both NIC?s.

I did check the obvious such as is the domain server being available, NIC being properly installed and configured, etc....

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Windows ME logon to NT Domain Problem

by Edward Clint In reply to Windows ME logon to NT Do ...

It seems clear that something is lost when a second NIC is installed. Something that the machine relies on to locate and communicate over SMB with the DC. Perhaps netbios bindings. Or perhaps The machine is confused about when NIC it is supposed to use to communicate with the DC- regardless of the 'disabled' status.
When you boot and run winipcfg, how many nics get listed? in what order?
It may also be useful to jump to a dos promot, and do a ROUTE PRINT. What interface is the default route?(ie the one 0.0.0.0 is mapped to)
The machines might be trying to communicate over the disabled interface.

Have you tried adding a static HOSTS file entry to associate the DC IP and name?

I know this may not help, but I am curious why you are bothering to use the NICs in the docking station if every laptop already has a NIC of its own. Why not just use the PCMCIA NIC whether docked or undocked? Do the docking stations block it or something? Why add complexity =)

Good luck.

-Ed

Collapse -

Windows ME logon to NT Domain Problem

by cascomp In reply to Windows ME logon to NT Do ...

Poster rated this answer

Collapse -

Windows ME logon to NT Domain Problem

by cascomp In reply to Windows ME logon to NT Do ...

This question was closed by the author

Back to Windows Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums