Discussion Locked

Can't get domain policies to dl over vpn

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have two remote offices connecting to a Small Business Server 2000 Domain over a hardware vpn, Lynksys VPN Routers. All of the workstations are XP PRO. After domain login the login scripts are processed and drives are mapped but the domain grouppolicies are not applied and the company shared folders and user folders shortcuts are not added to the desktop.
In the event log under application this is the error.

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

I have checked all DNS server setting in IP config and verified the host entries on the DNS server.

In-order to get the workstation to log into the domainquickly and successfully I had to make this registry setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters\MaxPacketSize = 0
for more info see Microsoft Knowledge Base Article - 244474. All computers have all of the latest updates and service packs. Any help on this question will be greatly appreciated.

12 replies

by beermonster

Hi,
I'm wondering if what you are seeing here is slow link detection. By default parts of the group policy will be 'dropped' if a slow link is detected, such as might be the case given your network setup. This can be configured in the gpo such that the check for a slow link can be disabled or the parameters 'tweaked'. I'm going this route because I get the feeling that error message might be a red herring. If a dc couldn't be contacted then , although a login could still occur using cached credentials, you would not see a login script running (I'm assuming the script is specified within the user account rather than the gpo, and using the %logonserver% variable which would not be available if a full domain logon had not occurred). Hope this gives some ideas....

by bwilson

I tried this route by disabling slow link detection in the gpo of the workstation and on the domain controller. The login script that runs is located on the server in sysvol/domain/scripts.

by darrell raines

Have you tried implementing an LMHOSTS file? I ran into this same problem with the same setup. In the long run we ended up putting a domain controller at the secondary site to speed things up, but to fix the problem until we had the DC, we used LMHOSTS file.

To set it up, you will need to do the following:

drop to a command prompt
change to the root of the C: drive

cd %SystemRoot%
cd system32
cd drivers
cd etc

edit LMHOSTS

in the LMHOSTS file, input the following:

IP Address for server
hit tab twice
input server name

should look like this:

192.168.x.x servername

Do this for all servers.

Let me know if this helps any.

by draegor

Hi - I got an off the wall idea. Check to make sure the router is not blocking protocol 50 and 51. Also make sure that UDP 500 is allowed too. We have it up at work internally, but could not get to work externally until these were done. See if you can get a list of what's open on the router. It might be blocking something critical.

by bwilson

Called Linksys and checked into this but they said the router is not blocking the ports.

by bwilson

I found the solution. I was logging in as users who did not have administrator access. What I had to do to fix the problem was log in as the administrator and from the command prompt run \\server\client\setup\sbsclnt.exe \s server
This loads the small business client and adds the needed registry entries to the workstation. After this is done reboot the computer and log in as the other user everything should work fine.

You can verify that the registry keys have been added by looking for this key on the clients workstation "HKEY_LOCAL_MACHINE\Software\Microsoft\Small Business"
As users log in they will show up under the user key. You can delete their key to reinitialize there settings.

by gopher_49

I'm having the exact same problem. I have 2 x Win XP Pro clients who get the Event ID:1054 in their application log. I've tried everything mentioned in this discussion. I'm using a Cisco PIX 501 and a 506e. All ports are open. Do you guy know of anything else to try? I can another remote site using the same config on both the workstations and the Cisco PIX 501's, however, they work perfectly fine?!

I'm lost.

by gopher_49

typo here's what I meant to say... 'I have another remote site using the same config on both the workstations and the Cisco PIX 501's, however, they work perfectly fine?!

by gopher_49

I got it to work! The suggestion of disabling the 'slow link detection' in the GPO worked. I had to disable 'slow link detection' on ALL GPO's. I've been running query's on the GPO status of the computer and the user. Both always received a critical and/or a gerenal network failure. Also, in the Computer Configuration Summary it showed it only using the 'local' GPO instead of the domain GPO. In the User Configuration Summary it showed the domain.

Now, both summaries show the computer account and the user account being the domain accounts. Also, all GPO's were applied successfully. I'm using the GPMC utility to generate the reports and to push the GPO's.

Anyway, it works perfect now. Just remeber to disable the 'slow link detection' on ALL GPO's.

thanks again.

by wholborn

I was able to resolve and fix Error ID 1054 at a remote site connected by Cisco Pix 501's by adding the following registry keys to each of the problematic remote computers and then by making changes to the Domains Group Policy.

Add these registry keys...
========================
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\System]
"GroupPolicyMinTransferRate"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System]
"GroupPolicyMinTransferRate"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\System]
"GroupPolicyMinTransferRate"=dword:00000000
=================================
This registry change will disable slow link detection, but a Group Policy will undo these registry changes unless you make changes to the group policy.

Then open your console and under Computer Configuration and also User Configuration go to Administrative Templates, System, Group Policy Then Choose "Group Policy Slow Link Detection" and set to Enabled and configure for "0". (Note Default is "500".)

This will disable the slow link detection through the group policy and Error ID 1054 should stop showing up in the users event logs.

This discussion is closed to new replies.