inconsistent drive mappings + many other errors

[Jeremy Allison]

On Thu, Jul 15, 2004 at 11:34:17AM -0500, Grimes, David wrote:
> I have searched the web and mailing lists for a couple weeks on this one and
> have come up empty handed on this one, I appreciate and thoughts or
> insights. Or ideas. Or suggestions. Or comments. Empathy is welcome....
> We have recently migrated to an 2003 AD and I have been tasked with
> upgrading the samba servers to 3.0. I've received new hardware (Dell 2650)
> and slapped ES 3.0 with all the latest updates. As it stands we have problem
> with 2000 machines being unable to access shares (authentication fails)
> using the UNC. They can however open the share and authenticate successfully
> by IP. If I tail the log on the samba server I get these errors....
> [2004/07/15 10:21:52, 1] smbd/sesssetup.c:reply_spnego_kerberos(173)
>   Failed to verify incoming ticket!

Ok, you have a kerberos problem. Common problems here are wrong enc type,
and clock skew. Not enough info in this message to diagnose.

> Users on XP don't exhibit this problem. However, we all have an intermittent
> problem getting a drive mapped on log in. Sometimes it just doesn't show up.
> If we  log out and back in then the drive gets mapped. Tailing the logs
> shows this error in /var/log/messages..
> Jul 15 11:16:17 bifs2 pam_winbind[19990]: user 'ADDOMAIN+aduser' granted
> acces
> Jul 15 11:16:17 bifs2 pam_winbind[19990]: pam_parse: unknown option;
> service=system-auth
> Jul 15 11:16:52 bifs2 smbd[19991]: [2004/07/15 11:16:52, 0]
> lib/util_sock.c:get_peer_addr(952) 
> Jul 15 11:16:52 bifs2 smbd[19991]:   getpeername failed. Error was Transport
> endpoint is not connected 
> Jul 15 11:16:52 bifs2 smbd[19991]: [2004/07/15 11:16:52, 0]
> lib/util_sock.c:write_socket_data(388) 
> Jul 15 11:16:52 bifs2 smbd[19991]:   write_socket_data: write failure. Error
> = Connection reset by peer 

Looks like clients dropping connections. Check your network hardware.

Jeremy.