Win2k Client issue

I have a client machine that is driving me up a wall. The client is running
XP Pro SP2. All servers are running Windows 2000 Server SP4 utilizing DHCP
along with a NAT router. The server doesn't recognize the client as a member
of the domain. This occurs every day or two.

From the client machine I will use a UNC path to a share or to access
another client and I receive an authentication dialog that requires me to
specify a domain user and password. Additionally the server will not allow
the user of that client machine use their own credentials. The same user can
log on to another machine without any problems accessing shares or other
clients.

I have tried disjoining the client from the network and then rejoining after
a reboot and it solves the problem on the client for a day or two.

Another little caveat. If I try to access the problem client from any server
or other client it never works. I get a path not found area. I cannot even
ping the problem client even by using it's IP address.

The only thing out of the ordinary is the the client machine was taken home
and the user accessed another computer at their home as they have a wireless
router set up to share a cable modem. The client was not disjoined from the
domain at any time while in use at the users home.

This on is really a thorn in my side!! Anyone got any ideas??

Check out the local policy on that machine, how much time it takes to update
the domain group policy in your domain. see if there is a domain gp that is
implemented on this machine (through to which group this machine belongs )
and compare between machines under this policy.

Ask that user about when he took his machine home, what settings has he
changed so that you can reconfigure them and get the machine as it was.

Has he changed SID (through sysprep for example)?

And finally, reset the machine account after rejoining the domain.

"RBell" wrote:

> I have a client machine that is driving me up a wall. The client is running
> XP Pro SP2. All servers are running Windows 2000 Server SP4 utilizing DHCP
> along with a NAT router. The server doesn't recognize the client as a member
> of the domain. This occurs every day or two.
>
> From the client machine I will use a UNC path to a share or to access
> another client and I receive an authentication dialog that requires me to
> specify a domain user and password. Additionally the server will not allow
> the user of that client machine use their own credentials. The same user can
> log on to another machine without any problems accessing shares or other
> clients.
>
> I have tried disjoining the client from the network and then rejoining after
> a reboot and it solves the problem on the client for a day or two.
>
> Another little caveat. If I try to access the problem client from any server
> or other client it never works. I get a path not found area. I cannot even
> ping the problem client even by using it's IP address.
>
> The only thing out of the ordinary is the the client machine was taken home
> and the user accessed another computer at their home as they have a wireless
> router set up to share a cable modem. The client was not disjoined from the
> domain at any time while in use at the users home.
>
> This on is really a thorn in my side!! Anyone got any ideas??

Is the Windows Time service running on the client (it should be)? Is the
time on the client within 5 minutes of the Domain Controller - or is it
drifting?

This can cause kerberos authentication problems. Everything needs to be
within 5 minutes by default.

"Zer0byte" wrote:

> Check out the local policy on that machine, how much time it takes to update
> the domain group policy in your domain. see if there is a domain gp that is
> implemented on this machine (through to which group this machine belongs )
> and compare between machines under this policy.
>
> Ask that user about when he took his machine home, what settings has he
> changed so that you can reconfigure them and get the machine as it was.
>
> Has he changed SID (through sysprep for example)?
>
> And finally, reset the machine account after rejoining the domain.
>
> "RBell" wrote:
>
> > I have a client machine that is driving me up a wall. The client is running
> > XP Pro SP2. All servers are running Windows 2000 Server SP4 utilizing DHCP
> > along with a NAT router. The server doesn't recognize the client as a member
> > of the domain. This occurs every day or two.
> >
> > From the client machine I will use a UNC path to a share or to access
> > another client and I receive an authentication dialog that requires me to
> > specify a domain user and password. Additionally the server will not allow
> > the user of that client machine use their own credentials. The same user can
> > log on to another machine without any problems accessing shares or other
> > clients.
> >
> > I have tried disjoining the client from the network and then rejoining after
> > a reboot and it solves the problem on the client for a day or two.
> >
> > Another little caveat. If I try to access the problem client from any server
> > or other client it never works. I get a path not found area. I cannot even
> > ping the problem client even by using it's IP address.
> >
> > The only thing out of the ordinary is the the client machine was taken home
> > and the user accessed another computer at their home as they have a wireless
> > router set up to share a cable modem. The client was not disjoined from the
> > domain at any time while in use at the users home.
> >
> > This on is really a thorn in my side!! Anyone got any ideas??

The service is running on the client and the time matches exactly with the
servers.

"fred" wrote:

> Is the Windows Time service running on the client (it should be)? Is the
> time on the client within 5 minutes of the Domain Controller - or is it
> drifting?
>
> This can cause kerberos authentication problems. Everything needs to be
> within 5 minutes by default.
>
> "Zer0byte" wrote:
>
> > Check out the local policy on that machine, how much time it takes to update
> > the domain group policy in your domain. see if there is a domain gp that is
> > implemented on this machine (through to which group this machine belongs )
> > and compare between machines under this policy.
> >
> > Ask that user about when he took his machine home, what settings has he
> > changed so that you can reconfigure them and get the machine as it was.
> >
> > Has he changed SID (through sysprep for example)?
> >
> > And finally, reset the machine account after rejoining the domain.
> >
> > "RBell" wrote:
> >
> > > I have a client machine that is driving me up a wall. The client is running
> > > XP Pro SP2. All servers are running Windows 2000 Server SP4 utilizing DHCP
> > > along with a NAT router. The server doesn't recognize the client as a member
> > > of the domain. This occurs every day or two.
> > >
> > > From the client machine I will use a UNC path to a share or to access
> > > another client and I receive an authentication dialog that requires me to
> > > specify a domain user and password. Additionally the server will not allow
> > > the user of that client machine use their own credentials. The same user can
> > > log on to another machine without any problems accessing shares or other
> > > clients.
> > >
> > > I have tried disjoining the client from the network and then rejoining after
> > > a reboot and it solves the problem on the client for a day or two.
> > >
> > > Another little caveat. If I try to access the problem client from any server
> > > or other client it never works. I get a path not found area. I cannot even
> > > ping the problem client even by using it's IP address.
> > >
> > > The only thing out of the ordinary is the the client machine was taken home
> > > and the user accessed another computer at their home as they have a wireless
> > > router set up to share a cable modem. The client was not disjoined from the
> > > domain at any time while in use at the users home.
> > >
> > > This on is really a thorn in my side!! Anyone got any ideas??