Hi,
yes we do use AD. I have thought of tracing a little bit domain traffic.
The problem only occurs when netapp is the server. But as i heared from the users right now (after increasing the cifs_maxpmx) everythin seems to be better.
Rgds
Jochen
-----Original Message----- From: Sandeep Cariapa [mailto:cariapa@yahoo.com] Sent: Friday, October 12, 2007 8:24 PM To: Willeke, Jochen; Adam McDougall Cc: toasters@mathworks.com Subject: RE: weird cifs problem
Could be another dumb question, but have you looked at your Active Directory server? Otherwise, how do you do authentication?
Have you mapped a CIFS share from another Windows box to your client? Do you still see this weird slowness or is it just when the NetApp is the server?
Sandeep Cariapa
--- "Willeke, Jochen" Jochen.Willeke@wincor-nixdorf.com wrote:
Hi,
Possibly a stupid question, but has someone ran
wireshark/tcpdump/windump
on the client side to verify that it is actually
the client waiting after
a filer response, and not just network latency?
Yes i did a tracing. And you see that the client is not waiting. Here some output
No time SRC DEST Protocol Info 282 0.000145 client nafiler SMB Write AndX Request, FID: 0x026b, 36 bytes at offset 0
283 0.001178 nafiler client SMB Write AndX Response, FID: 0x026b, 36 bytes
284 0.056002 client nafiler SMB Close Request, FID: 0x026b
285 0.000391 nafiler client SMB Close Response, FID: 0x026b
This is only one examlpe. The filer seems to be the faster part within this connection, doesn't it? But what causes the client to wait so long?? I was only creating a file from my client on that share.
Rgds
Jochen