User Authentication

On the computers in the remote office, configure their LMHOSTS files to point to the BDC. That will do the trick.
The LMHOSTS file can handle name resolution in the same way that a WINS server does, but I feel that LMHOSTS file is better at it.
So, add a single line to the LMHOSTS files on these Win2k, associating the IP address and machine name of the BDC, with the #PRE and #DOM commands. For example, if your BDC is called MYBDC and it has an IP address of 10.1.1.2 and your NT domain is called MYDOMAIN, then the LMHOSTS files on each Win2K workstation in the remote offices would need the following:

10.1.1.2 MYBDC #PRE #DOM:MYDOMAIN

That will force the Win2K machines to authenticate to the BDC.

Technet article Q180094 talks about the LMHOSTS file and domain resolution:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q180094
(please remove any spaces)

hope this helps

This may or may not help, but usually when a client logs on it receives a DHCP lease from the local dhc server on the subnet. Is the DHCP server in HQ? if not check the IP address to see if it's local and it the same subnet. In addition, If you are using wins and if there is a wins server locally make sure that the client is pointing to that server restart the netlogon service on the bdc and re-log in the clients

use nt reskit utility to reset the authentication path. eg. nltest /sc_reset:domain_name

Also you can check the profiles size and if you use roaming profiles, implement with System policies editor a max limit for users profiles. Or set to use by default local profile.

Microsoft provides a utility called SETPRFDC.EXE that will do what you want.

Refer to MS knowledge base article Q181171.

Hope that helps.

This question was closed by the author