Re: Kerberos UDP vs TCP
- From: "Joe Richards [MVP]" <humorexpress@xxxxxxxxxxx>
- Date: Wed, 15 Nov 2006 00:06:52 -0500
Various network devices and improperly configured network cards are what I most often see screwing up the UDP packet delivery. I have had to use TCP to troubleshoot but it was always to help identify that some network component was screwing up.
UDP is used initially because that is the standard. It generally works just fine, in the hundreds of networks I have experienced first hand and thousands I have dealt with second/third hand the number of times I have seen UDP issues is less than 15.
TCP does add a good amount of overhead and I would recommend doing a network impact study before considering switching whole hog to TCP. Actually I would say go find why UDP isn't working, it will take some time with a sniffer to find out what device is throwing out the packets. but once you determine that you can investigate it and correct it. This can usually, in my experience, be fixed by correcting configurations or updating firmwares of various network devices.
--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net
---O'Reilly Active Directory Third Edition now available---
http://www.joeware.net/win/ad3e.htm
paolo valsecchi wrote:
Hi everybody.
I'm facing some problems with Kerberos authentication using UDP protocol. As suggested by Microsoft using TCP protocol the problem has been solved instead.
Questions:
Why Microsoft uses UDP by default if there are authentication problems?
What would be the global impact on the network (WAN) using Kerberos authentication through TCP? Would it be a suitable solution?
Any help really appreciated.
- Prev by Date: Re: Kerberos UDP vs TCP
- Next by Date: Re: EFS algorithm
- Previous by thread: Re: Kerberos UDP vs TCP
- Next by thread: files on ur web directory
- Index(es):
Relevant Pages
|