2 replies
by alan_viens Accepted solution
by robo_dev Accepted solution
You can reconfigure XP to use TCP for Kerberos authentication with a simple registry hack:
http://support.microsoft.com/kb/244474
The issue is that the authentication protocol used by Windows, Kerberos, uses UDP (to be standards-compliant). UDP is a stateless protocol (therefore is unreliable).
VPNs and UDP do not get along because MTU sizes and latency issues create out-of-order packets. TCP can tolerate out-of-order or fragmented packets, but UDP cannot.
I believe part of the 'same subnet' issues exist is because UDP broadcasts will typically be limited to a single subnet (unless you've enabled multicast across multiple subnets, which is a bad idea).
So my first guess is to add the TCP hack to use TCP for Kerberos.
My next guesses would involve fiddling with WINS and LMHOSTS and also the nbtstat command.
Remember, Microsoft Networking is an art, not a science.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending