[Samba] Samba, VPN, and Mac OSX 10.4.2

[Brian Daniels]

We're having an odd problem with connecting to Samba shares over a VPN 
with a Mac client.

We have several Mac clients connecting to a Samba 3.0.10-1.fc2 
installation.  Prior to upgrading them to Tiger, everything worked fine 
both local and over an IPSec VPN.

After upgrading to Tiger, they still work fine when on our LAN.  But if 
they try to connect to a share over the VPN, Finder hangs.  The Mac logs 
the following messages in /var/log/system.log during the hang:

Jul 29 09:59:46 brian-daniels-powerbook-g4-15 kernel[0]: bug: ecnt = 32, 
but m_len = 0 and m_next = 0 (please report)
Jul 29 09:59:46 brian-daniels-powerbook-g4-15 kernel[0]: bug: ecnt = 33, 
but m_len = 0 and m_next = 0 (please report)
Jul 29 09:59:46 brian-daniels-powerbook-g4-15 kernel[0]: bug: ecnt = 32, 
but m_len = 0 and m_next = 0 (please report)
Jul 29 09:59:46 brian-daniels-powerbook-g4-15 kernel[0]: bug: ecnt = 33, 
but m_len = 0 and m_next = 0 (please report)
Jul 29 09:59:46 brian-daniels-powerbook-g4-15 kernel[0]: bug: ecnt = 32, 
but m_len = 0 and m_next = 0 (please report)
Jul 29 09:59:46 brian-daniels-powerbook-g4-15 kernel[0]: bug: ecnt = 33, 
but m_len = 0 and m_next = 0 (please report)
Jul 29 09:59:46 brian-daniels-powerbook-g4-15 kernel[0]: bug: ecnt = 32, 
but m_len = 0 and m_next = 0 (please report)
Jul 29 09:59:46 brian-daniels-powerbook-g4-15 kernel[0]: bug: ecnt = 33, 
but m_len = 0 and m_next = 0 (please report)
Jul 29 09:59:46 brian-daniels-powerbook-g4-15 kernel[0]: bug: ecnt = 32, 
but m_len = 0 and m_next = 0 (please report)
Jul 29 09:59:47 brian-daniels-powerbook-g4-15 kernel[0]: t)
Jul 29 09:59:47 brian-daniels-powerbook-g4-15 kernel[0]: bug: ecnt = 32, 
but m_len = 0 and m_next = 0 (please report)

It keeps logging these errors until Finder is forced to quit.
Interestingly, if the server connected to has only a few files (<~30) in 
the root directory, then the hang does not occur.  But if the user then 
tries to cd to a dir containing more files, the above problem appears.

Other actions over the VPN (ssh, VNC, etc) work without problems.

I'd appreciate any suggestions.

Thanks,
Brian

-- 
Brian Daniels