Cannot Obtain Domain Controller Name

I have a WinXP Pro laptop that connects wirelessly. The domain controller is
WinServer2003. Sometimes I get get an error that the machine cannot obtain
domain controller name. It can get an IP address OK. And then Automatic
certificate enrollment for local system failed to contact active directory.
IE works OK to get connected to outside, but can't e-mail. Another laptop
works fine with no issues. Sometimes the problem unit works OK for e-mail
but at other times it's a problem. I assume the errors generated are the
reason why e-mail is a problem. What needs to be fixed.

pestocat <(E-Mail Removed)> wrote:
> I have a WinXP Pro laptop that connects wirelessly. The domain
> controller is WinServer2003. Sometimes I get get an error that the
> machine cannot obtain domain controller name. It can get an IP
> address OK. And then Automatic certificate enrollment for local
> system failed to contact active directory. IE works OK to get
> connected to outside, but can't e-mail. Another laptop works fine
> with no issues. Sometimes the problem unit works OK for e-mail but at
> other times it's a problem. I assume the errors generated are the
> reason why e-mail is a problem. What needs to be fixed.

Are you using the native Windows wireless zero configuration? I've found
that works better than third party wireless helper software.
Do you have "always wait for network on startup & logon" enabled via GPO? Do
so, if not...it's important.
Check your event logs & the output of an rsop.msc for more clues.....

"Lanwench [MVP - Exchange]"
<(E-Mail Removed) hoo.com> wrote in message
news:(E-Mail Removed)...
> pestocat <(E-Mail Removed)> wrote:
>> I have a WinXP Pro laptop that connects wirelessly. The domain
>> controller is WinServer2003. Sometimes I get get an error that the
>> machine cannot obtain domain controller name. It can get an IP
>> address OK. And then Automatic certificate enrollment for local
>> system failed to contact active directory. IE works OK to get
>> connected to outside, but can't e-mail. Another laptop works fine
>> with no issues. Sometimes the problem unit works OK for e-mail but at
>> other times it's a problem. I assume the errors generated are the
>> reason why e-mail is a problem. What needs to be fixed.
>
> Are you using the native Windows wireless zero configuration? I've found
> that works better than third party wireless helper software.
> Do you have "always wait for network on startup & logon" enabled via GPO?
> Do so, if not...it's important.
> Check your event logs & the output of an rsop.msc for more clues.....
>
Thank you for the reply. The solution search has been very frustrating. I
took suggestion and used the Windows configuration for the wireless. I had
been using the Dell configuration and that seemed to work OK for me but
there was still the problem for the client with the issue. I then looked at
the Events on the server and read that the problem client was not getting
access as she should. I could log into the same machine with no problems.
Looking further down I saw that client was getting logged into a different
group that I was. I deleted that group from clients member list and now she
gets logged in correctly. I think the problem is fixed. Thank you.

pestocat <(E-Mail Removed)> wrote:
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) hoo.com> wrote in
> message news:(E-Mail Removed)...
>> pestocat <(E-Mail Removed)> wrote:
>>> I have a WinXP Pro laptop that connects wirelessly. The domain
>>> controller is WinServer2003. Sometimes I get get an error that the
>>> machine cannot obtain domain controller name. It can get an IP
>>> address OK. And then Automatic certificate enrollment for local
>>> system failed to contact active directory. IE works OK to get
>>> connected to outside, but can't e-mail. Another laptop works fine
>>> with no issues. Sometimes the problem unit works OK for e-mail but
>>> at other times it's a problem. I assume the errors generated are the
>>> reason why e-mail is a problem. What needs to be fixed.
>>
>> Are you using the native Windows wireless zero configuration? I've
>> found that works better than third party wireless helper software.
>> Do you have "always wait for network on startup & logon" enabled via
>> GPO? Do so, if not...it's important.
>> Check your event logs & the output of an rsop.msc for more clues.....
>>
> Thank you for the reply. The solution search has been very
> frustrating. I took suggestion and used the Windows configuration for
> the wireless. I had been using the Dell configuration and that seemed
> to work OK for me but there was still the problem for the client with
> the issue. I then looked at the Events on the server and read that
> the problem client was not getting access as she should. I could log
> into the same machine with no problems. Looking further down I saw
> that client was getting logged into a different group that I was. I
> deleted that group from clients member list and now she gets logged
> in correctly. I think the problem is fixed. Thank you.

Glad to hear it, but definitely apply that GPO setting for *all* your client
workstations if you're running XP.