I have a Server 2003 SP2 domain controller with 65 Windows XP_SP3 and 2 Windows 7 Pro workstations. There are several problems related, so I will list them and discuss my workarounds. 1) Windows 7 machines will not connect to an external site through the default gateway. We use GoToMyPC for remote access. The XP client will connect to the GoToMyPC agent and establish a connection. The Win7 machines will not. The workaround is for me to hard set the IP/Netmask/and gateway, but I have to use a different gateway than the firewall. I also need to set an external DNS server. My initial thought was the firewall was blocking a port, but Citrix support says the Win7 agent and the XP agent are the same. 2) Trust relationship between this workstation and primary domain has failed error . I have had this error a few times. The workaround is well known (Unplug net cable, remove from domain, delete account from domain, add to domain) but it isn’t a fix as I have had the same problem 3 times on my Win7 station and once on another. I am looking for a resolution before I deploy Win7 to my users. Windows IP Configuration Host Name . . . . . . . . . . . . : 3R6SHK1 Primary Dns Suffix . . . . . . . : taxwarriors.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : taxwarriors.com Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : taxwarriors.com Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Network Connection Physical Address. . . . . . . . . : 00-25-64-AA-09-A0 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::8db1:3635:eece:2eb5%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.54(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, August 06, 2010 12:59:03 PM Lease Expires . . . . . . . . . . : Saturday, August 07, 2010 12:59:02 PM Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.7 DHCPv6 IAID . . . . . . . . . . . : 234890596 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-CA-C8-FE-00-25-64-AA-09-A0 DNS Servers . . . . . . . . . . . : 192.168.0.7 NetBIOS over Tcpip. . . . . . . . : Enabled

Hi, I would like to share: ERROR_TRUSTED_RELATIONSHIP_FAILURE The trust relationship between this workstation and the primary domain failed Best Regards DalePlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I am not seeing that error code on the Window 7 machines, and I do not have a Server 2008 box running. I have found a few other points, but I am not sure how they relate: System Log 8/10/2010 8:41:38 AM 3210 - NETLOGON This computer could not authenticate with \\ODIN, a Windows domain controller for domain DOMAIN, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator. 8/10/2010 8:39:25 AM 3210 - NETLOGON This computer could not authenticate with \\HEIMDAL, a Windows domain controller for domain DOMAIN, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator. 8/10/2010 8:39:15 AM 5719 - NETLOGON This computer was not able to set up a secure session with a domain controller in domain DOMAIN due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. The part that I find odd is my WindowsXP clients (right on 65 of them) are running flawlessly. No Internet issues, no internal problems with local webservers, no logon problems. I have no warnings or error from the PDC or BDC during that time-frame. Any other thoughts?

Bump.

I've been seeing- " This computer could not authenticate with \\DC, a Windows domain controller for domain DOMAIN" on one of our servers recently. I noticed WDS services wouldn't start and I found that entry. ****UPDATED I just disjoined and joined the server to the domain and it appears the event log cleared up. I saved the System and App. logs before the disjoin and the new ones look good. MCTS 70-620 Certified