Hello list,
I have been using "smb ports = 445" to get rid of the dreaded
"Transport
endpoint is not connected" error, and it seemed to be working fine for
Windows XP, on SerNet's samba3-3.3.9-40.el5 build.
We recently introduced Windows 7 to our network - and the "Transport
endpoint" errors are back:
Nov 25 17:21:41 experimental smbd[13018]: [2009/11/25 17:21:41, 0]
lib/util_sock.c:read_socket_with_timeout(939)
Nov 25 17:21:41 experimental smbd[13018]: [2009/11/25 17:21:41, 0]
lib/util_sock.c:get_peer_addr_internal(1676)
Nov 25 17:21:41 experimental smbd[13018]: getpeername failed. Error
was Transport endpoint is not connected
Nov 25 17:21:41 experimental smbd[13018]: read_socket_with_timeout:
client 0.0.0.0 read error = Connection reset by peer.
Anyone know what Windows 7 is trying to do here?
I'm also seeing some other errors generated by Win 7:
Nov 25 17:21:18 experimental smbd[13018]: [2009/11/25 17:21:18, 0]
rpc_server/srv_netlog_nt.c:_netr_ServerAuthenticate2(555)
Nov 25 17:21:18 experimental smbd[13018]: _netr_ServerAuthenticate2:
netlogon_creds_server_check failed. Rejecting auth request from client
MEEPO machine account MEEPO$
It all works - I've joined the domain and can log in and access the
shares, so obviously it does manage to authenticate somehow, so is there
any way of stopping those messages appearing?
Moray
"To err is human; to purr, feline."
