[Samba] Dropouts
Hello I just want to ask you if you solve the problem with a drops I have the same problem and im totaly frustrated….. HELP PLEASE :- Lukas VECHET MARK DISTRI s.r.o. Na Flore 2/1302 143 00 PRAHA 4 CZECH REPUBLIC phone : +420 244 401 993-6 fax : +420 244 402 041 email : [EMAIL PROTECTED] mobil : +420 602 127 082 --- Odchozí zpráva neobsahuje viry. Zkontrolováno antivirovým systémem AVG (http://www.grisoft.cz). Verze: 6.0.719 / Virová báze: 475 - datum vydání: 12.7.2004 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Dropouts
hi there, we are using samba 3.0.4 with ldap as primary domain controler and as wins server, which provides windows xp clients. the ldap server is running on a separate machine. it works great. after boot the users can logon and connect to all shares very fast. but during a long session (1h or more) if the user wants to reconnect to shares, it take a very long time (5-10s) to get a response from the server. after this "dropout" there are no connection problems again for a while. this problem causes that word or outlook hangs and the user are very frustrated. for this problem i have no solution, because during the clients try to reconnect there are no log entries in the samba log till the connection succeed with: esmt-00078 (192.168.80.108) connect to service preuss initially as user preuss (uid=20113, gid=100) (pid 15669) any ideas thx tom esmt-00078 (192.168.80.108) connect to service public initially as user preuss (uid=20113, gid=100) (pid 15930) [2004/06/04 15:06:31, 0] smbd/connection.c:register_message_flags(220) register_message_flags: tdb_fetch failed [2004/06/04 15:07:01, 0] smbd/connection.c:register_message_flags(220) register_message_flags: tdb_fetch failed [2004/06/04 15:07:02, 1] smbd/service.c:close_cnum(801) esmt-00096 (192.168.80.215) closed connection to service profile$ [2004/06/04 15:07:02, 1] smbd/service.c:close_cnum(801) esmt-00096 (192.168.80.215) closed connection to service system$ [2004/06/04 15:10:00, 0] rpc_server/srv_pipe.c:api_pipe_netsec_process(1397) failed to decode PDU [2004/06/04 15:10:00, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(605) process_request_pdu: failed to do schannel processing. [2004/06/04 15:15:13, 1] smbd/service.c:make_connection_snum(619) esmt-00078 (192.168.80.108) connect to service preuss initially as user preuss (uid=20113, gid=100) (pid 15669) [2004/06/04 15:15:13, 1] smbd/service.c:close_cnum(801) esmt-00078 (192.168.80.108) closed connection to service preuss [2004/06/04 15:15:13, 1] smbd/service.c:close_cnum(801) esmt-00078 (192.168.80.108) closed connection to service public [2004/06/04 15:21:54, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected [2004/06/04 15:21:54, 0] lib/util_sock.c:write_socket_data(413) write_socket_data: write failure. Error = Connection reset by peer [2004/06/04 15:21:54, 0] lib/util_sock.c:write_socket(438) write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer [2004/06/04 15:21:54, 0] lib/util_sock.c:send_smb(630) Error writing 4 bytes to client. -1. (Connection reset by peer) [2004/06/04 15:22:35, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected [2004/06/04 15:22:36, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected [2004/06/04 15:22:36, 0] lib/util_sock.c:write_socket_data(413) write_socket_data: write failure. Error = Connection reset by peer [2004/06/04 15:22:36, 0] lib/util_sock.c:write_socket(438) write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer [2004/06/04 15:22:36, 0] lib/util_sock.c:send_smb(630) Error writing 4 bytes to client. -1. (Connection reset by peer) [2004/06/04 15:24:14, 1] smbd/service.c:make_connection_snum(619) esmt-00097 (192.168.80.137) connect to service netlogon initially as user schroeder (uid=20240, gid=100) (pid 15570) [2004/06/04 15:24:21, 1] smbd/service.c:make_connection_snum(619) esmt-00073 (192.168.80.103) connect to service prn_00019 initially as user werner (uid=20133, gid=100) (pid 15623) [2004/06/04 15:24:23, 0] smbd/connection.c:register_message_flags(220) register_message_flags: tdb_fetch failed [2004/06/04 15:24:23, 0] smbd/connection.c:register_message_flags(220) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Dropouts...
On Tue, Jun 03, 2003 at 10:55:52AM -0500, Andrew Holland wrote: > On Sunday 01 June 2003 12:51 am, you wrote: > > On Sat, May 31, 2003 at 10:30:05PM -0500, theSyClops wrote: > > > I admit that I am a linux-server newbie... How do I do the ethereal > > > trace, I have not had to do it before and I wouldent know what to look > > > for or how to do it > > > > The linux box should have a command called 'ethereal'. Run as root, > > and get it to capture packets on the relevent ethernet interface > > and filter the capture to only capture packets from and to the > > client. > > > > If you've ever used the Microsoft Netmon application, ethereal > > should be very easy. If you haven't used a network sniffer before, > > I suggest you read up on the subject. > > > > Jeremy. > > Ok, after a quick crash course in ethereal including compiling and > installing it, Here is the capture, This log has been filtered by time > before and after where the drop out occured as well as source and dest IP's > > (frame.time_relative >= 343 && frame.time_relative <= 347.2) && (ip.src == > 10.0.0.224 || ip.dst == 10.0.0.224) > > Then saved (this info here for making sure I didnt screw up the logs) > > The error occures @ time 2 seconds after beginning of capture > > attachment available upon request, the list wont let me post it and I dont > have a reliable space to throw it up on the net I took a quick look at this but the file is truncated at pakcet 360 (ethereal reports it as corrupt). Can you load it in your ethereal binary ? Also, can you remind me of the issue we're tracking here :-) (Sorry, I'm concurrently tracking a lot of stuff, and context in an email helps). Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Dropouts...
On Sunday 01 June 2003 12:51 am, you wrote: > On Sat, May 31, 2003 at 10:30:05PM -0500, theSyClops wrote: > > I admit that I am a linux-server newbie... How do I do the ethereal > > trace, I have not had to do it before and I wouldent know what to look > > for or how to do it > > The linux box should have a command called 'ethereal'. Run as root, > and get it to capture packets on the relevent ethernet interface > and filter the capture to only capture packets from and to the > client. > > If you've ever used the Microsoft Netmon application, ethereal > should be very easy. If you haven't used a network sniffer before, > I suggest you read up on the subject. > > Jeremy. Ok, after a quick crash course in ethereal including compiling and installing it, Here is the capture, This log has been filtered by time before and after where the drop out occured as well as source and dest IP's (frame.time_relative >= 343 && frame.time_relative <= 347.2) && (ip.src == 10.0.0.224 || ip.dst == 10.0.0.224) Then saved (this info here for making sure I didnt screw up the logs) The error occures @ time 2 seconds after beginning of capture attachment available upon request, the list wont let me post it and I dont have a reliable space to throw it up on the net Andrew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Dropouts...
On Thu, May 29, 2003 at 10:47:16PM -0500, Andrew Holland wrote: > > We have a samba server (2.2.8 then 2.2.8a) running on top of a 320 GB raid > ATA-raid array with a FastTrack controller. Both the server and workstations > are running through Gigabit NIC's. Every five or so minutes the workstations > loose communications with the server, Then it takes 10-15 seconds for the > workstations to reconnect to the server. The times are not specific, for > example it can take anywhere from 1 minute to 3 hours between drop outs, but > when we put a workstation under load it is (approx) 5-7 minutes between drop > outs. Sometimes all stations loose the connection at once, sometimes it is > only one workstation. It does not occur in any other program except Samba. > If I don't get this fixed soon my boss is going to make me go back to > (shutters) windows Can you get an ethereal trace between a client and server when this happens ? This will help to debug the problem. Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Dropouts...
On Thu, 29 May 2003, Andrew Holland wrote: > OK, I have been banging my head into the wall on this now for two or more > weeks > > We have a samba server (2.2.8 then 2.2.8a) running on top of a 320 GB raid > ATA-raid array with a FastTrack controller. Both the server and workstations > are running through Gigabit NIC's. Every five or so minutes the workstations > loose communications with the server, Then it takes 10-15 seconds for the > workstations to reconnect to the server. The times are not specific, for > example it can take anywhere from 1 minute to 3 hours between drop outs, but > when we put a workstation under load it is (approx) 5-7 minutes between drop > outs. Sometimes all stations loose the connection at once, sometimes it is > only one workstation. It does not occur in any other program except Samba. > If I don't get this fixed soon my boss is going to make me go back to > (shutters) windows This sounds VERY suspiciously like a network hardware problem. What NICs? What HUBs? Are you running in duplex mode? What error rates on the ethernet interfaces? What collision activity on the HUBs? This does not sound like a Samba problem. - John T. -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Dropouts...
OK, I have been banging my head into the wall on this now for two or more weeks We have a samba server (2.2.8 then 2.2.8a) running on top of a 320 GB raid ATA-raid array with a FastTrack controller. Both the server and workstations are running through Gigabit NIC's. Every five or so minutes the workstations loose communications with the server, Then it takes 10-15 seconds for the workstations to reconnect to the server. The times are not specific, for example it can take anywhere from 1 minute to 3 hours between drop outs, but when we put a workstation under load it is (approx) 5-7 minutes between drop outs. Sometimes all stations loose the connection at once, sometimes it is only one workstation. It does not occur in any other program except Samba. If I don't get this fixed soon my boss is going to make me go back to (shutters) windows Globals section of the smb.conf file goes something like --- #Server Identification workgroup = GENESIS netbios name = EXODUS netbios aliases = INSTALLERS server string = Fedler studio Samba Server #Server Settings log file = /data/system/samba/logs/%m.log log level = 1 max log size = 5000 OS level = 99 #Security Settings security = user smb passwd file = /data/system/samba/smbpasswd encrypt passwords = yes pam password change = yes #Networking settings #interfaces = 10.0.0.16/24 #dns proxy = no wins support = yes preferred master = yes #Domain Controller propertys domain logons = yes logon drive = y: logon home = \\EXODUS\%U logon script = logon.bat domain admin group = @dAdmin [netlogon] path = /data/system/samba/netlogon comment = network Logon Share guest ok = yes writable = no share modes = no --- Any help whatsoever would be appreciated Andrew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
