Sounds like something at the physical layer. Try a different NIC on the server. Run some network diagnostics.
On 12/10/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Yes, it's reliable and Samba is working on another machine just fine. That > box is running Samba 3.0.20 on Slackware. This is 3.2.5 on Ubuntu. 8.10 > > I've done some further testing and it's affecting all OS's (Linux > included), not just Vista. Now it seems that if I don't use the share > for 4 or 5 minutes, it becomes inactive and I'm unable to reconnect using > the name.. however, I can reconnect via the IP. Then, after another > period of 4 or 5 minutes of inactivity, the connection is lost and I have > to reconnect via the name. > > This is really beginning to drive me nuts.. anyone have any ideas? > > Thanks! > - Matt > > > > > Jeremy Allison <[EMAIL PROTECTED]> > Sent by: [EMAIL PROTECTED] > 12/09/2008 07:55 PM > Please respond to > Jeremy Allison <[EMAIL PROTECTED]> > > > To > [EMAIL PROTECTED] > cc > [email protected] > Subject > Re: [Samba] Connectivity issues > > > > > > > On Tue, Dec 09, 2008 at 11:20:42AM -0600, [EMAIL PROTECTED] wrote: >> Samba 3.2.5 >> >> I'm running into an issue when using Vista to access Samba shares. I'm >> able to connect intermitently and it stays connected for a brief period > of >> time (under 60 seconds) before I get the following error on the Vista > box: >> >> "Network path was not found" >> >> In syslog it shows: >> >> [begin] >> [2008/12/09 11:09:03, 2] auth/auth.c:check_ntlm_password(308) >> check_ntlm_password: authentication for user [matt] -> [matt] -> > [matt] >> succeeded >> >> [2008/12/09 11:09:03, 1] smbd/service.c:make_connection_snum(1190) >> mpc (10.0.0.58) connect to service data initially as user matt >> (uid=1005, gid=1006) (pid 19637) >> >> [2008/12/09 11:11:02, 0] lib/util_sock.c:read_socket_with_timeout(939) >> >> [2008/12/09 11:11:02, 0] lib/util_sock.c:get_peer_addr_internal(1607) >> getpeername failed. Error was Transport endpoint is not connected >> read_socket_with_timeout: client 0.0.0.0 read error = Connection reset > >> by peer. > > This means the client disconnected. We (smbd) don't know > why. Do you have a reliable network ? > > Jeremy. > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > -- Sent from my mobile device -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
