Gp over VPN (DNS Issue)

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

I am having trouble getting policies to remote locations
over a VPN connection in the event log I get the
following error:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1054
Date: 6/22/2004
Time: 8:19:29 AM
User: NT AUTHORITY\SYSTEM
Computer: WPG-72Y7041
Description:
Windows cannot obtain the domain controller name for your
computer network. (An unexpected network error
occurred. ). Group Policy processing aborted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


A while back we computers in these remote locations were
logging in very slow. After calling MS they told us to
add a registry key under
HKEY\LocalMachine\System\CurrentControlSet\Control\LSA\Ker
beros\Parameters MaxPacketSize = 1.

This sped up the login process but didnt help our policy
issue. I tryed removing this reg edit and still didn't
receive policies & the logon was extremely slow. Could
anyone shed some light on these issues?

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

You internal computers' NIC DNS properties much ALL
be pointing (solely) to internal, DYNAMIC DNS servers.

Do not try to point them to the ISP or mix them.

--
Herb Martin


"steinway" <anonymous@discussions.microsoft.com> wrote in message
news:1f7c001c45870$955789a0$a601280a@phx.gbl...
> I am having trouble getting policies to remote locations
> over a VPN connection in the event log I get the
> following error:
> Event Type: Error
> Event Source: Userenv
> Event Category: None
> Event ID: 1054
> Date: 6/22/2004
> Time: 8:19:29 AM
> User: NT AUTHORITY\SYSTEM
> Computer: WPG-72Y7041
> Description:
> Windows cannot obtain the domain controller name for your
> computer network. (An unexpected network error
> occurred. ). Group Policy processing aborted.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> A while back we computers in these remote locations were
> logging in very slow. After calling MS they told us to
> add a registry key under
> HKEY\LocalMachine\System\CurrentControlSet\Control\LSA\Ker
> beros\Parameters MaxPacketSize = 1.
>
> This sped up the login process but didnt help our policy
> issue. I tryed removing this reg edit and still didn't
> receive policies & the logon was extremely slow. Could
> anyone shed some light on these issues?
>
>
>