>I have a employee who is getting the following error everytime he restarts
>his laptop.
>
>"A domain controller for your domain could not be contacted.  You have been
>logged on using cached account information.  Changes made to your profile
>since you last logged on may not be available."
>
>The funny thing is that when he logs in everything work.  He can get access
>to the internet and to the network.
>
>If he just logs off and doesn't get the error.
>
>He is running Windows XP SP2 with all the latest updates.  If you have any
>ideas please let me know.
>
>Thanks,
>Fsunoles68

"Chuck" wrote:

> On Mon, 23 Oct 2006 10:53:01 -0700, Fsunoles68
> <Fsunole***@discussions.microsoft.com> wrote:
>
> >I have a employee who is getting the following error everytime he restarts
> >his laptop.
> >
> >"A domain controller for your domain could not be contacted.  You have been
> >logged on using cached account information.  Changes made to your profile
> >since you last logged on may not be available."
> >
> >The funny thing is that when he logs in everything work.  He can get access
> >to the internet and to the network.
> >
> >If he just logs off and doesn't get the error.
> >
> >He is running Windows XP SP2 with all the latest updates.  If you have any
> >ideas please let me know.
> >
> >Thanks,
> >Fsunoles68
>
> I'd check his DNS / IP setup, and the domain DNS setup.  DNS based name
> resolution, to identify the domain controller, has to be done deliberately.
> <http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
> http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html
>
> --
> Cheers,
> Chuck, MS-MVP [Windows - Networking]
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem, when it's a normal response from experience.
> My        email         is          AT         DOT
>    actual       address    pchuck       mvps        org.
>

>"Chuck" wrote:
>
>> On Mon, 23 Oct 2006 10:53:01 -0700, Fsunoles68
>> <Fsunole***@discussions.microsoft.com> wrote:
>>
>> >I have a employee who is getting the following error everytime he restarts
>> >his laptop.
>> >
>> >"A domain controller for your domain could not be contacted.  You have been
>> >logged on using cached account information.  Changes made to your profile
>> >since you last logged on may not be available."
>> >
>> >The funny thing is that when he logs in everything work.  He can get access
>> >to the internet and to the network.
>> >
>> >If he just logs off and doesn't get the error.
>> >
>> >He is running Windows XP SP2 with all the latest updates.  If you have any
>> >ideas please let me know.
>> >
>> >Thanks,
>> >Fsunoles68
>>
>> I'd check his DNS / IP setup, and the domain DNS setup.  DNS based name
>> resolution, to identify the domain controller, has to be done deliberately.
>> <http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
>> http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html

>He is getting his IP address through DHCP like the rest of our network. 
>Everyone else works fine.  Also I thought it might be something to do with
>his ethernet card, so I disabled it and tried it on the wireless, but it did
>the samething.
>
>Fsunoles68

"Fsunoles68" wrote:

> I have a employee who is getting the following error everytime he restarts
> his laptop.
>
> "A domain controller for your domain could not be contacted.  You have been
> logged on using cached account information.  Changes made to your profile
> since you last logged on may not be available."
>
> The funny thing is that when he logs in everything work.  He can get access
> to the internet and to the network.
>
> If he just logs off and doesn't get the error.
>
> He is running Windows XP SP2 with all the latest updates.  If you have any
> ideas please let me know.
>
> Thanks,
> Fsunoles68