Windows cannot obtain the domain controller name for your computer network

  • Thread starter Thread starter Lou
  • Start date Start date
L

Lou

Guest
"Windows cannot obtain the domain controller name for your computer network.
(An unexpected network error occurred)
Group Policy processing aborted."

This is from the Application log of the server itself (SBS2003)! Repeats
every 5 minutes. Have spent ages trying to find solution without success. I
suspect it has to do with MS Virtual PC 2007. I need it to run tests on
Windows 2000, XP and Vista without having to have any more hardware.
Typically have 2 or 3 virtual PCs running at the same time. They also report
Winlogon and Browser failures but browse network fine. Some are domain
members others are on the same name workgroup.
Server otherwise functions OK with occasional slowness in web browsing
probably due to DNS issues when it forgets its own name. It sits on the
green channel of IPcop Linux based router and is itself the DHCP server.
Making IPcop the DHCP server makes no difference.
Any ideas?
 
Re: Windows cannot obtain the domain controller name for your computer network

Lou <octex1@gxyzmail.com> wrote:
> "Windows cannot obtain the domain controller name for your computer
> network. (An unexpected network error occurred)
> Group Policy processing aborted."
>
> This is from the Application log of the server itself (SBS2003)!

Hi - since you're using SBS, I suggest you post in
microsoft.public.windows.server.sbs. SBS does many things its own way. I'm
setting up this reply to crosspost there.

> Repeats every 5 minutes. Have spent ages trying to find solution
> without success.

Try posting an unedited ipconfig /all from this server.

> I suspect it has to do with MS Virtual PC 2007.

Why?

I
> need it to run tests on Windows 2000, XP and Vista without having to
> have any more hardware. Typically have 2 or 3 virtual PCs running at
> the same time. They also report Winlogon and Browser failures but
> browse network fine. Some are domain members others are on the same
> name workgroup. Server otherwise functions OK with occasional slowness in
> web browsing
> probably due to DNS issues when it forgets its own name. It sits on
> the green channel of IPcop Linux based router and is itself the DHCP
> server. Making IPcop the DHCP server makes no difference.

You don't want to do that, definitely. Keep SBS running DHCP.

> Any ideas?
 
Re: Windows cannot obtain the domain controller name for your computer network



"Lou" <octex1@gxyzmail.com> wrote in message
news:#2A82lE4IHA.220@TK2MSFTNGP02.phx.gbl...
> "Windows cannot obtain the domain controller name for your computer
> network.
> (An unexpected network error occurred)
> Group Policy processing aborted."
>
> This is from the Application log of the server itself (SBS2003)! Repeats
> every 5 minutes. Have spent ages trying to find solution without success.
> I suspect it has to do with MS Virtual PC 2007. I need it to run tests on
> Windows 2000, XP and Vista without having to have any more hardware.
> Typically have 2 or 3 virtual PCs running at the same time. They also
> report Winlogon and Browser failures but browse network fine. Some are
> domain members others are on the same name workgroup.
> Server otherwise functions OK with occasional slowness in web browsing
> probably due to DNS issues when it forgets its own name. It sits on the
> green channel of IPcop Linux based router and is itself the DHCP server.
> Making IPcop the DHCP server makes no difference.
> Any ideas?
>
>
Where are you running VPC? Not on the DC, I hope!
 
Re: Windows cannot obtain the domain controller name for your computer network

Bill Grant <not.available@online> wrote:
> "Lou" <octex1@gxyzmail.com> wrote in message
> news:#2A82lE4IHA.220@TK2MSFTNGP02.phx.gbl...
>> "Windows cannot obtain the domain controller name for your computer
>> network.
>> (An unexpected network error occurred)
>> Group Policy processing aborted."
>>
>> This is from the Application log of the server itself (SBS2003)!
>> Repeats every 5 minutes. Have spent ages trying to find solution
>> without success. I suspect it has to do with MS Virtual PC 2007. I
>> need it to run tests on Windows 2000, XP and Vista without having to
>> have any more hardware. Typically have 2 or 3 virtual PCs running at
>> the same time. They also report Winlogon and Browser failures but
>> browse network fine. Some are domain members others are on the same
>> name workgroup. Server otherwise functions OK with occasional slowness in
>> web
>> browsing probably due to DNS issues when it forgets its own name. It
>> sits on the green channel of IPcop Linux based router and is itself
>> the DHCP server. Making IPcop the DHCP server makes no difference.
>> Any ideas?
>>
>>
> Where are you running VPC? Not on the DC, I hope!

Why not?
 
Re: Windows cannot obtain the domain controller name for your computer network

"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:%23Rz8b6E4IHA.1420@TK2MSFTNGP06.phx.gbl...
>
> Try posting an unedited ipconfig /all from this server.
>
The only suspicious line in ipconfig /all is:
"Node type............Unknown"
Otherwise the DC is the primary WINS and DNS server, the IPcop router is the
secondary DNS server.
>
>> I suspect it has to do with MS Virtual PC 2007.
>
> Why?
>
Because I have near identical SBS2003 on the blue channel of the IPcop
router and it does not have the same problems. It also hasn't yet got VPC
installed. However, I am planning to install it as the virtual machines run
Outlook 2003 to sanitize, de-junk and sort email for mobile users running
MailforExchange on their Nokia phones.
 
Re: Windows cannot obtain the domain controller name for your computer network

"Bill Grant" <not.available@online> wrote in message
news:eMvLM4J4IHA.3500@TK2MSFTNGP05.phx.gbl...
>
>
> "Lou" <octex1@gxyzmail.com> wrote in message
> news:#2A82lE4IHA.220@TK2MSFTNGP02.phx.gbl...
>>
> Where are you running VPC? Not on the DC, I hope!
>
Its the ideal place. Powerful dual processor machine, 4GB of RAM, dedicated
SCSI hdd for the virtual machines, it all runs beautifully apart from the
above mentioned problem.
Due to space and heat considerations I cannot put any more PC hardware in
the control room.
 
Re: Windows cannot obtain the domain controller name for your computer network

Lou <octex1@gxyzmail.com> wrote:
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
> message news:%23Rz8b6E4IHA.1420@TK2MSFTNGP06.phx.gbl...
>>
>> Try posting an unedited ipconfig /all from this server.
>>
> The only suspicious line in ipconfig /all is:
> "Node type............Unknown"
> Otherwise the DC is the primary WINS and DNS server, the IPcop router
> is the secondary DNS server.
>>
>>> I suspect it has to do with MS Virtual PC 2007.
>>
>> Why?
>>
> Because I have near identical SBS2003 on the blue channel of the IPcop
> router and it does not have the same problems. It also hasn't yet got
> VPC installed. However, I am planning to install it as the virtual
> machines run Outlook 2003 to sanitize, de-junk and sort email for
> mobile users running MailforExchange on their Nokia phones.

Hmm. I run virtual machines on SBS with no problem....
 
Back
Top