Hello all, For the past 3 months we are facing problems with our network during logon. We receive the following error: 5719 The RPC server is unavailable Followed by: 1097 Windows cannot find the machine account, No authority could be contacted for authentication. 1030 Windows cannot query for the list of Group Policy objects. on Windows XP client machines. Subsequently the logon script fails to execute and the mapped drives are not connected. Occasionally authentication during logon to the domain fails altogether on the Windows XP clients and a reboot is required to be able to logon to the domain. All clients are Windows XP with service pack 3 updated with all the Microsoft updates. Our domain servers are Windows 2003 with service pack 2 and all the Microsoft updates. Server network drivers have been updated with the latest drivers from HP (2 domain servers have HP NC373i Gigabit cards, 1 domain server has an HP NC321i Gigabit card, all network cards are not teamed and the second adapter is disabled). We have tried to remove update KB948496 and this seems to improve but not eliminate the problem. Is anyone facing the similar problems? Any suggestions would be welcomed as we have hit a dead end.Thanks a lot for any help on this!

hi there,your question is related to windows xp , there is a seperate forum which handles your queries, please do post it under http://social.technet.microsoft.com/forumsnavigate to windows IT pro forum sainath Windows Driver Development

Sainath Into Driver Development said: hi there,your question is related to windows xp , there is a seperate forum which handles your queries, please do post it under http://social.technet.microsoft.com/forumsnavigate to windows IT pro forum sainath Windows Driver DevelopmentHiI think that it is related to Windows 2003 Server. Windows XP are the clients but the problem is on the server OS, not at the clients. Also, the aforementioned update, was installed on the Windows Server, so we believe that the problem is there (at the server side).Anyway, if you insist, just tell me so and i will re-post it to the Windows XP forum.

hi there,if u feel this issue is related to win 2003 , please do post under the below forumhttp://www.microsoft.com/communities/newsgroups/en-us/default.aspx?sainath Windows Driver Development

Hi,can you please re-type the link ? That one does not direct me to any forum.Thanks again for your help!

Hello Kikapu, To isolate the issue, here are some information we may need to confirm with you? 1. Does the issue occur only on Windows XP SP3 clients? Or it occurs with all the clients (including Windows Vista / Windows Server 2003)? 2. Do this domain controller has one or more replication partners in the domain since the failure of the SYSVOL replication might lead to failure to apply Group policy? If there are multiple domain controllers in the environment, please use the command "repadmin /showrepl" to check if the AD replication is normal. 3. if there are multiple domain controllers, please run "netdom query fsmo" on the domain controllers and then check if the domain controller which holds PDC emulator is available. 4. There are other several reasons that may result in the client failed to logon domain. For example there may be problems with IP connectivity, DNS name resolution, or security authentication that are preventing successful logon to the domain. a. please check the TCP/IP configuration of the NIC on the clients to see if the Preferred DNS server is pointed to the DNS server in the domain.b. and then you may test to see if the clients can ping through the domain controller. 5. From the error message Windows cannot find the machine account, No authority could be contacted for authentication., it seems that there may be no corresponding computer accounts in the domain. Please check to see if the computer account exist in Active Directory. If not, please rejoin the problematic clients into the domain and then check if you can logon with them successfully. 6. As this issue happened after KB948496 was installed, please also refer to following steps to disable TCP Offload and RSS on the Windows Server 2003 SP2 to test if this issue will re-occure: a.Click Start, click Run, type regedit, and then click OK.b.Locate the following registry subkey: c.HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parametersd.Right-click EnableTCPChimney, and then click Modify.e.In the Value data box, type 0, and then click OK.f.Right-click EnableRSS, and then click Modify.g.In the Value data box, type 0, and then click OK.h.Right-click EnableTCPA, and then click Modify.9.In the Value data box, type 0, and then click OK.i.Exit Registry Editor, and then restart the computer. If the error message still continues, please refer to my previous thread to troubleshoot the issue.http://social.technet.microsoft.com/forums/en-US/winservergen/thread/ccc2051a-0c87-4378-b0fa-51a61ce97d9a Hope it helps.This posting is provided "AS IS" with no warranties, and confers no rights.

Hi David, Thank you for your suggestions. Finally we were able to resolve our problem by turning off TCPChimney, EnableRSS, TCPA and all other NIC settings related to Offloading: Tx IP Checksum Offload, Rx IP Checksum Offload, Tx TCP Checksum Offload, Rx TCP Checksum Offload, Large Send Offload. After turning off all of these features the error messages stopped appearing and connectivity to the 2003 domain servers is working without any problems. Update: As I was writing these lines the RPC error appeared in one Windows XP client (talk about Murphys law!) and the login script failed. I hope that this was just a freak event, because throughout the repeated tests this was the one and only time this happened.

UPDATE: After repeated testing we observed that using the settings from our previous post the errors: 5719 The RPC server is unavailable, 1097 Windows cannot find the machine account, No authority could be contacted for authentication and 1030 Windows cannot query for the list of Group Policy objects are still present. The login problems are greatly reduced but not eliminated. Is anyone else facing the same problems? Do we have any news from MS developers on a possible fix? Thank you in advance for your time.