Hi everybody,i was wondering if there is any registry entry that forces only tcp comunication in order to prevent UDP overflow or errors..there is an entry for windows server 2003 to prevent Kerberos UDP communications and force to use TCP..Dword: MaxUdpPacketand enter a value of 1.in the control\Lsa\Kerberos\Parametersnow how can i use the same thing in a home pc??thanks in advance,RR

The registry key only forces Kerberos traffic to use TCP.A home PC will not use Kerberos over a network, unless it's a member of an Active Directory domain or other Kerberos-enabled Directory Service. Then again, it wouldn't really be a home PC when it's domain-joined...Certain service protocols use TCP, other service protocols use UDP. Some protocols allow both UDP and TCP, but these are limited.Depending on the network services a home PC consumes you may be able to force certain service protocols to use TCP, but there will always be UDP-based service protocols in use. It is the nature of some protocols.

Hi Sander,Thanks for replying and yeah i know that its only a domain joined machine that uses kerberos but i was curious if there was a way to redirect UDP packets to tcp and i tried applying that setting in the TCPIP\parameters Ndiswan\protocols\0 and also Control\Lsa ...it seems to be working ,i was getting spammed on UDP ports and a whole bunch of destination unreachable was getting triggered ,now it is solved believe it or not...i also used some UDP parameters over TCPIP\parameters ..it seems to be working..i only receive echo pings every once in a while but thats ok ....its better than getting spammed ...Thanks a lot and if u know any usable registry parameter for UDP ports just let me know !and yeah i know some essential services uses UDP ports such as 500(IKE) and 135(epmapper)...Thanks in advance for any news and i apreciate ur reply ^^Kind regards,RR