Forced to ReJoin Domain every week.

[xX-spitfire-Xx]

Hi,
I am having problems with a single win2k pro machine. The machine looses
the ability to connect to network shares every week or few days. It also
gives an error when trying to logon, stating that the domain is unavailable.

If I try to rejoin the domain by using the "network identification wizard",
I am unable to do so, the wizard displays a message that "the domain is
either invalid or does not exist."

In order to rejoin the domain, I must make the workstation part of a
workgroup, then reset the computer account (Have tried deleting also) in
active directory. I am then able to use the wizard to make the workstation
part of the domain again.

This is happening very regularly on only one client machine. No other
problems are apparent. Does anyone know what is happening and how I can
stop this workstation loosing its connectivity?

TIA.

[Lanwench [MVP - Exchange]]

How is your DNS set up? Does this computer specify only the AD-integrated
DNS server's IP address in its TCP/IP properties as it should (with
forwarders specified on the DNS server for external resolution)?

[Daniel Cooper]

i had a similar problem which turned out to be down to the
machine ID, to solve it i ran sysprep and the machine
recieved a new id, if i remember correctly it was called
GID but dont quote me on that

[xX-spitfire-Xx]

The DNS is active directory integrated, and is the only DNS server that the
client machine is directed to. Forwarders are listed on the DNS server for
external resolution, and all seems to be fine. I have tried manually adding
the "primary DNS suffix" to the client but this has made no difference. I
also have added the domain controller to the lmhosts file, but this also
made no difference and eventually the machine lost domain connectivity
again. The machine is still able to by-pass the DC for direct internet
access via a netgear router, this is normal, and the way in which our
network is supposed to be set up.

I was told that every seven days or so, all clients attempt to renew their
"certificate" with the domain controller, and this can fail under certain
circumstances. We are not running "Certificate services", so I do not know
if this applies to us, I also have not been able to find any information on
this topic.

I also was told that I needed to use a tool from the resource kit to search
active directory for corrupt ldap entries. I am uncertain of the validity
of this, and have no idea which tool or how to go about doing this.

Does this make any sense to anyone? Does anyone know what I can do?
Please?
Please?
Please?

"xX-spitfire-Xx" <evol...@hotmail.com> wrote in message
news:%23JjlheM...@tk2msftngp13.phx.gbl...