[Samba] Samba disconnect problem
I have a persistant problem at a client site. This is the error I am getting in /var/log/messages: Dec 10 09:03:41 fileserver smbd[7652]: [2003/12/10 09:03:41, 0] lib/ util_sock.c:read_data(436) Dec 10 09:03:41 fileserver smbd[7652]: read_data: read failure for 4. Error = Connection reset by peer No errors in log.smbd Here is the Layout: Three clients: Win2000 Win2000 WinXP Pro Server: Mandrake 9.2 Samba Verion 2.28 All current patches and updates installed Network card: 3Com 3c905b PII-450 256Mb SDRAM 40Gb Hard Drive (IDE) Network: 10/100 switched (U.S. Robotics SOHO 8 port Switch) Cat-5 Wiring All PCs have 10/100 network cards in them. Primary use of server is to share Quickbooks files to the other computers. This is where the problem is. Once or twice a day they get booted out of the client file that they are in. This corresponds with the error in the log. This is a big problem for the customer. The main user was gone last week; and no errors occurred for the other users all week. Her machine was on but not used during this time. Here are the steps I have taken: *ALL new hardware in server with the exception of the hard drive *Replaced Switch *Ran new cable to machine with most issues *Replaced Network card in machine that was unoccupied last week. *Checked network settings on clients - removed extra protocal (netbeui, etc) *Mapped clients directly to Server IP address to exclude name resolution issues. *Made TCPDUMP log - during errors there is no unusal messages in this *Played with smb.conf setting - including trying different locking things and such. Bear in mind that the clients are NOT working within the same account file - so there should be no locking or sharing issue there I REALLY need to get this fixed - it is a big problem. Let me know if more info is needed. Here is my smb.conf: # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options (perhaps too # many!) most of which are not shown in this example # # Any line which starts with a ; (semi-colon) or a # (hash) # is a comment and is ignored. In this example we will use a # # for commentry and a ; for parts of the config file that you # may wish to enable # # NOTE: Whenever you modify this file you should run the command testparm # to check that you have not made any basic syntactic errors. # #=== Global Settings = [global] encrypt passwords = yes os level = 20 map to guest = bad user printing = cups preferred master = no security = user load printers = yes printer admin = @adm dns proxy = no smb passwd file = /etc/samba/smbpasswd log file = /var/log/samba/log.%m server string = Samba Server %v printcap name = cups socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 workgroup = MDKGROUP max log size = 50 [homes] comment = Home Directories browseable = no writable = yes # You can enable VFS recycle bin on a per share basis: # Uncomment the next 2 lines (make sure you create a # .recycle folder in the base of the share and ensure # all users will have write access to it. See # examples/VFS/recycle/REAME in samba-doc for details ; vfs object = /usr/lib/samba/vfs/recycle.so ; vfs options= /etc/samba/recycle.conf # You may want to prevent abuse of your server disk space, and spread of virii ; veto files = /*.eml/*.nws/*.dll/*.mp3/*.MP3/*.mpg/*.MPG/*.vbs/*.VBS/ # Un-comment the following and create the netlogon directory for Domain Logons ; [netlogon] ; comment = Network Logon Service ; path = /var/lib/samba/netlogon ; guest ok = yes ; writable = no #Uncomment the following 2 lines if you would like your login scripts to #be created dynamically by ntlogon (check that you have it in the correct #location (the default of the ntlogon rpm available in contribs) ;root preexec = /usr/bin/ntlogon -u %U -g %G -o %a -d /var/lib/samba/netlogon/ ;root postexec = rm -f /var/lib/samba/netlogon/%U.bat # Un-comment the following to provide a specific roving profile share # the default is to use the user's home directory ;[Profiles] ;path = /var/lib/samba/profiles ;browseable = no ;guest ok = yes ;writable = yes # This script can be enabled to create profile directories on the fly # You may want to turn off guest acces if you enable this, as it # hasn't been thoroughly tested. ;root preexec = PROFILE=/var/lib/samba/profiles/%u; if [ ! -e $PROFILE ]; \ ;then mkdir -pm700 $PROFILE; chown %u.%g $PROFILE;fi # NOTE: If you have a CUPS print system there is no need to # specifically define each individual printer. # You must configure the samba printers with the appropriate Windows # drivers on your Windows clients. On the Samba server no filtering is # done. If you wish that the
Re: [Samba] Disconnect problem
Cantisan, What type or NIC and HUB doe you have? Ethernet cable quality? We have thousands of sites running samba on all varietles of Red Hat. You should make sure your hardware is all OK. We are seeing an incredible number of instances of bad hardware that causes similar problems. On Sat, 30 Nov 2002, cantisan wrote: Samba and Win2k just don't seem to want to work together. I get disconnects after about 13MB of data transfer, and the Win2k box just loses the share as if it were disconnected. Re-establishing the share works, but data transfer of large files or working with large amounts of data is impossible. From the amount of traffic on this newsgroup regarding WinXP and Win2K problems with Samba, I think this problem is common - although a solution hasn't cropped up, or I haven't found one in my travels. What is abundantly common is that folks are still learning how to manage WinXP! - John T. Here's my contribution to finding the problem: I put a sniffer on the net and see that when this disconnect occurs, the Samba server sends a set of 5 or 6 data packets to the Win2K box, and the Win2k box sends back ACK packets for them. [all normal so far..] However, the Linux (RedHat 7.3) box doesn't appear to get the last ACK packet (or isn't processing it - since tcpdump is picking it up it IS being received...), as it resends the last data packet (same tcp seq number). The Windows box ACKS that packet again, and this is repeated about 6 or 7 times before the Windows box decides that it's not worth the trouble and just stops communicating (no attempt to FIN the connection either...) Now I don't know why the ACKs just aren't getting through to the data handler for Samba, or why Windows doesn't bother to try to send a FIN packet (no obligation...it's a timed-out tcp connection as far as Win2k cares..), but I'd like to know how to fix this. I have the tcpdump output if anyone would care to look at it.. The problem has been with me since RedHat 7.0 and Samba that came with it - I'm on RedHat 7.3 and Samba 2.2.6 now and the problem is still here -- 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
Re: [Samba] Disconnect problem
Cantisan, What type or NIC and HUB doe you have? Ethernet cable quality? ALL 3COM (3 HUB 24 ports and 1 Swtich 8 Ports to servers, ethernet 3com 10/100), I just finish a b We have thousands of sites running samba on all varietles of Red Hat. You should make sure your hardware is all OK. We are seeing an incredible number of instances of bad hardware that causes similar problems. Do you have any program that need to keep the connection with a server all time ? Do you use net use on your login script to map a letter ? Did you see any red-cross on a map driver letter ? All my clients are Wk2. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Disconnect problem
Anyone had disconnect problems with WK2 boxs and samba servers ? Any fix ? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
