• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 522
  • Last Modified:

Event ID 5719 on WinXP clients on Win Server 2003 Domain

We are getting Event ID 5719 on our Windows XP Pro SP3 clients on a Windows Server 2003 domain.

This is causing problems with access to some of our servers but most importantly it is causing our Content Management filtering device to block all Internet access for that client until the client has rebooted, or waited 30 - 45 minutes.

And the incidents are increasing.

We have tried increasing the MaxDgramBuffering value from 128 KB to 256 KB:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q310339 

But it had no effect.

We tried restarting the Net Logon service on the client and when we did that we could get access to the servers the client previously couldnt get access to, but it didnt help with the Content Management device and access to the Internet, we still have to either reboot the client or wait 30  45 minutes.
0
BMCKRob
Asked:
BMCKRob
1 Solution
 
oBdACommented:
This is most commonly caused by incorrect DNS settings.
In short: *all* domain members may *only* use DNS servers that are authoritative for your AD DNS name; routers or external DNS server (from the ISP, for example) may *not* appear in the TCP/IP settings of any domain member (including the DCs). In a usual setup, this means that only the DC(s) may provide DNS services for AD members. Configure forwarders on your DNS servers to forward external requests to your ISP, or simply rely on the root hints.
Details here:

10 DNS Errors That Will Kill Your Network
http://redmondmag.com/features/article.asp?EditorialsID=413

Frequently asked questions about Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?kbid=291382

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/?kbid=825036
0
 
BMCKRobAuthor Commented:
Sorry to take so long, We tested this on a couple of our machines for a couple days then rolled it out to the domain and now everything works fine, not a single problem has occurred and our original problem has been solved.

I scoured the Net looking for a solution to this and everything kept pointing to the MaxDgramBuffering as the solution.

Thanks for the help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now