Kerberos Problem; UDP Packet Loss

R

Richard Moreno

Hi-

Has anyone come across the following event log?

EVENT ID: 10
SOURCE: Kerberos
Description:
The kerberos subsystem is having problems fetching tickets from your domain
contoller using the UDP network protocol. This is typically due to network
problems. Please contact your systems administrator.

This is the 1st time I've encountered this issue. Suffice it to say, DNS
configuration is good, site topology is covered. I want to say that this is
a complete communications problem of the network hardware (routers,
switches, WAN) because I've scoured my AD Infrastructure and configuration.

One major issue that stems from this (randomly) is that once a user enters
their logon credentials the ctrl-alt-del window sits there for a few minutes
and eventually moves to the "loading personal settings" progress bar. It
takes 40 minutes for the desktop to come up and even then there's no access
to network resources because the client never actually got authenticated.

Comments?

--
Thanks,
Richard Moreno
MCSE NT4\2000, MCSA 2000

This posting is provided "AS IS" with no warranties, and confers no
rights.
 
R

Richard Moreno

Hi-

Thank you. I did find this article previously and have used it sparingly
however in your opinion is this all there is? I'm looking for a root cause
if I can find one. And what is the result of network usage in shifting all
Kerberos traffic to talk over TCP rather than it's standard UDP?

--
Thanks,
Richard Moreno
MCSE NT4\2000, MCSA 2000

This posting is provided "AS IS" with no warranties, and confers no
rights.



Richard McCall said:
Based on the error and problems you are seeing try the setting in this
article.
244474 How to Force Kerberos to Use TCP Instead of UDP
http://support.microsoft.com/?id=244474


--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
Richard Moreno said:
Hi-

Has anyone come across the following event log?

EVENT ID: 10
SOURCE: Kerberos
Description:
The kerberos subsystem is having problems fetching tickets from your domain
contoller using the UDP network protocol. This is typically due to network
problems. Please contact your systems administrator.

This is the 1st time I've encountered this issue. Suffice it to say, DNS
configuration is good, site topology is covered. I want to say that this is
a complete communications problem of the network hardware (routers,
switches, WAN) because I've scoured my AD Infrastructure and configuration.

One major issue that stems from this (randomly) is that once a user enters
their logon credentials the ctrl-alt-del window sits there for a few minutes
and eventually moves to the "loading personal settings" progress bar. It
takes 40 minutes for the desktop to come up and even then there's no access
to network resources because the client never actually got authenticated.

Comments?

--
Thanks,
Richard Moreno
MCSE NT4\2000, MCSA 2000

This posting is provided "AS IS" with no warranties, and confers no
rights.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top