CIFS Client TimeOuts

[Alzhy]

We're experiencing mount hangups on Windows shares accross a fairly fast (DS3 - 40mbps) and lighly used WAN link. We're using A.01.08. Any ideas as to tweaks we could use in cifsclient.cfg? We've already doubled all timeout values but we're still getting the hangups. We've doubled up again and increased nfsRetransmission from 3 to 6 -- the mounts are holding but here've been less activity and we think it willhang up again..

Any "proper" settings to give stability to CIFS mounts accross WAN links?

[Michael Steele_2]

SAMBA does not use NFS, but you can copy and time large files over NFS and FTP as a comparison.

Here are some SAMBA perfornace tweaks.

Log level: Higher logging will slow performance so use logging when you need to but set to 0 when done.

Socket Options with smb.conf.
TCP_NODELAY - Translates to send as much as possible.

IPTOS_LOWDELAY - Used inconjuction with TCP_NODELAY. If you use one then also use the other.

SO_SNDBUF and SO_RCVBUF - a higher value is better.

SO_KEEPALIVE - Returns unused memory and process-table entries after check fo disappearance of a client.

Note: These options will vary between vendors.

Also try increasing your MTU from HP-UX.

[Steven E. Protter]

You probably want to upgrade but be aware there is a security bulletin on these products.

CIFS/9000 Server
http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=B8725AA

CIFS/9000 Client
https://payment.ecommerce.hp.com/cgi-bin/swdepot_parser.cgi/cgi/try.pl?productNumber=B8724AA&date=

Your issue may be resolved,based on my reading of the docs.

Have you run some ping tests to make sure the WAN is reliable.

I would send some 64K packets with ping and make sure the transit times are consistent.

ping hostname 64000

If those times vary, it could be network:
1) Wiring
2) Router IOS
3) lanadmin -x lan# check that you really are getting 100 BaseT Full duplex, or whatever your top speed is. You might want to hardcode speed settings into /etc/rc.config.d/hpbtlanconf
4) Your NIC card might be flakey.

SEP