It took a while but Ive identified what is going on. Its a pretty complex issue:
Problem 1: The Sonicwall VPN is fragmenting the Kerberos UDP packets so the workstation is not able to authenticate successfully with the DC
FIX: Force Kerberos to only use TCP. This is a simple registry change on the workstation: http://support.microsoft.c
Problem 2: Workstations use ICMP (ping) packets to check if a DC is alive before it start communicating w/ it. With the initial ping it also includes a bit more data to test the quality of the connection. This places the size of the ICMP packet over a threshold and makes the Sonicwall think that it is a ping of death resulting in the packet being dropped.
FIX: One registry change that is applied to the HKLM and one that is applied to the HKCU the problem is that this last one has to be applied for every user and that user has to be a local admin while the registry change is applied definitely doable because we already have everyones credentials but not ideal.
http://www.experts-exchang
Main Topics
Browse All Topics





by: RobWillPosted on 2008-11-10 at 15:42:43ID: 22926810
Make sure the clients, which are likely configured using DHCP from the Sonicwall, receive only your Internal DNS server's IP for their network adapter's DNS configuration. Adding the ISP, even as an alternate/secondary DNS server can cause this problem. If possible, also add the domain suffix to the client machines. This can be done manually (see link) or through DHCP with many routers. With a Window server as a DHCP server it is done as scope option #15. dded%20Ima ges/Blog/D NS.jpg
http://www.lan-2-wan.com/A