We have a Terminal Server in are DMZ.

Problem is when logging on, GPO's are not being applied. The guy incharge of the firewalls reports their are no errors in the logs.

Any ideas?

Prob that it can't communicate with the AD server,

See this link and have a chat with your firewall guy;

Microsoft TechNet Windows Server 2003 Active Directory

We had all kinds of issues getting our frontend exchange server to communicate with the AD server across a firewall. In the end it was the firewall at fault, everything appeared to be working and not being blocked but due to a fault in the firewall software it was being blocked.

The event ID is 1054

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

When a do a gpupdate /force I get the same error.

The firewall is blocking pings to the dc's so I had a feeling it was detecting a slow network as it cant ping so stopping gpo's from processing. But after changing the local gp it didnt work.

By using nltest /dcgetdc:domain I get my dc info.

Do the other apps work on the terminal server.

Try installing the 2003 adminpak.msi file and see if you can access "active directory users and computers". and actually see the ad contents.

Do the other apps work on the terminal server.

Try installing the 2003 adminpak.msi file and see if you can access "active directory users and computers". and actually see the ad contents.

No need. Think I've found the problem using userenv.logs "dsgetdcname failed with 59"

How to troubleshoot Group Policy object processing failures that occur across multiple forests

ICMP is disabled.

Just had the guy allow ICMP to the 3 dc's for now and it works.

Thanks anyway guys.

Oh and Mannyo dont think my last thread about system restore is over

Their is a reg file (well their should be ) to disable slow speed connections.

Oh and Mannyo. Dont think my last thread about system restore is over Once I get some time I'm back on it

I was about to say that that rang a bell and I thought ping was used to determine link speeds (it won't be in Longhorn apparently)