Hi all Thanks to David Collier-Brown for the mail on Friday - we are looking into it right now. Our setup is: RedHat 6.1, Samba 2.0.5a, on a HP LH3 NetServer - 256 MB, 5x9GB RAID 5, also running Apache and the Intranet. Cisco Catalyst 2900 (24 port) switch, and a mix of HP and NetGear hubs. PCs are connected to the hubs and then upload to the switch, the servers are straight onto the switch. Hubs and NICs 98% 3Com 3C900, 3C950 or thereabouts 10Mbps the server runs a 10/100. The switch is autosensing for speed and duplex. These problems only seem to have started in the last month or so - about a week after going on to the switch from 10-base 2. If the connections drop in the middle of opening a file or saving it, the file gets corrupted and lost. And I get it in the neck! I do have some more info on the situation - there seem to be between 5 and 7 PCs with this problem. One is a laptop running Win2k, the rest are Win 95 PCs. The laptop is being used to run tests since he seems to be able to reproduce the problems regulary. Using netstat to monitor connections, the port that the laptop is connected to keeps changing - 7 times in 10 minutes and it's doing it while he's accessing the file, I know that samba 2.0.7 deals with Win 2k better, but it's also happening on Win 95 machines too. I've set keep alive = 30 as suggested, but we still get problems. I've just swapped the laptop to a different hub to see if the hub is having a problem. Nope - still there. The ports go from 1048, 1050, 1052, 1054, 1056, 1059, 1060 - incrementing in 2's. This is becoming perplexing. I've set up netstat to run every 20 mins and print the output for comparison. Any ideas anyone? Matt Unless otherwise agreed expressly in writing by Fesa UK Limited, this communication should be treated as confidential and the information contained therein may not be used or disclosed except for the purpose for which it was sent. If you are not the intended recipient of this communication please contact the sender immediately. WARNING: Computer viruses can be transmitted by e-mail. The recipient should check this e-mail and any attachments for the presence of viruses. Fesa UK Limited accepts no liability for any damage caused by any virus transmitted by this e-mail. This e-mail and and attachments may not be copied and forwarded without the written consent of Fesa UK Limited . In the event of copying or forwarding, the recipient will be required to idemnify Fesa UK Limited against any claim for loss or damage caused by any virus or otherwise.
Can anyone help ?
I have installed SAMBA on a local DELL machine - Samba version 2.2.2 running
under RedHat 6.2.
I have configured SAMBA using SWAT and 2 Linux directories are made
accessible to Windows users as NT shares - and they map each share to a
drive letter - the Linux box acts purely as an NT file-server. All
authentication is done locally - each user has an entry in /etc/smbpasswd
and well as in /etc/passwd. The machine sits on a sub-net of a HUGE network
that is primarily a Windows network but has many other UNIX and Linux boxes
attached. My sub-net has a 10Mbit link onto the main network which is mainly
100 and 1000MBit with 20Mbit links to regional offices. I have users in
London, Bristol, Birmingham and Belfast all on various sub-nets of a HUGE
network. In total there are about 50 users connected during the day with a
total of between 2 and 8 files open at any one time - so you can see its not
exactly hammered. Most of the machines on the network are either Windows PCs
(desktop machines) or NT servers - all the servers being managed by a huge
IT department. I needed an NT file share that could be accessed by my users
from PCs and Macs. Sadly corporate IT do not offer a Mac file-serving
service - they consider Macs to be a security risk as they cannot enforce a
login name/password security mechanism on Macs. So I decided to host the
share on a Linux box running SAMBA and Netatalk to "export" Linux
directories to PCs and Macs.....
Its nearly been successful......but......users (PC users) complain of the
SAMBA shares disconnecting from their PCs. Typically they would be working
on, say, an Excel spreadsheet that they have loaded from the server and when
they come to save it says that the server has disconnected. They then have
to save the document on their local disk. They then re-connect
("exploring"
the "Mapped" drive seems to be enough for the PC to re-connect) and
then
they can load the spreadsheet from the local file and save it back onto the
server. I've not had this problem myself so I am relying on rather woolly
user feed-back.....
In the file(s) /var/log/samba/log.pc-?????? (all the PCs have names like
pc-132485) I get error messages saying something like:
[2001/12/04 13:04:45, 0] lib/util_sock.c:read_socket_data(478)
read_socket_data: recv failure for 4. Error = Connection timed out
or:
[2001/12/04 16:28:25, 0] lib/util_sock.c:read_socket_data(478)
read_socket_data: recv failure for 4. Error = Connection reset by peer
which seem to coincide with that particular PC getting disconnected.
Can anybody help ? I'm getting alot of hassle from senior management about
the ineffectiveness of the system......
All users have an NT hosted share mapped all the time - they NEVER get the
NT server disconnecting.....
I get other errors reported in /var/log/samba/log.smbd like this:
[2001/12/04 23:12:50, 0] smbd/connection.c:yield_connection(63)
yield_connection: tdb_delete for name failed with error Record does not
exist.
but these seem to coincide with my own machine opening the NT share - but
WHY my machine ? its an ordinary W98 desktop like everyone
else's......surely SAMBA doesn't know that it was me who installed/set
up
the Linux/SAMBA box ?????? That would be extraordinary......
Any help appreciated......
I can send /etc/smb.conf and any other info if it would help.......
I have noticed a couple of things:
Setting the socket options - the default option seems to be TCP_NODELAY - I
have tried TCP_NODELAY, IPTOS_LOWDELAY and SO_KEEPALIVE in all possible
combinations - when I have SO_KEEPALIVE set I set "keepalive" = 0,
otherwise
"keepalive" is set to its default of 300. When SO_KEEPALIVE is set the
problem gets worse - about twice as many users get "disconnected".....
The users with most problems are the "power" users who have several
files
open most of the day and the users who are at the "far-end" of the
network -
those in Belfast and those who have "RAS"ed in....
Hoping someone can help,
Cheers,
Jerry
> Jerry Clark
> Manager, Design Systems
> BBC MediaArc
>
> * Room LG692 Television Centre, Wood Lane, London, W12 7RJ
> * Work: 020 8225 6707
> * Mobile: 07710 350190
> * Fax: 020 8576 8727
>
> * mailto:jerry.clark@bbc.co.uk
> * http://www.bbcmediaarc.com
>
This e-mail, and any attachment, is confidential. If you have received
it in error, please delete it from your system, do not use or disclose
the information in any way, and notify me immediately. The contents of
this message may contain personal views which are not the views of the
BBC, unless specifically stated.