445 is used for KRB requests. You (to my knowledge) cannot get CIFS + KRB in a Windows environment without being in an AD forest. I don't believe there is any way to force the filer to use 445 without being in an AD forest.
(I'd assume you can get Linux to run SAMBA with KRB outside of an AD forest, but that's a completely different story.)
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Jack Lyons Sent: Wednesday, December 12, 2007 8:50 PM To: toasters@mathworks.com Subject: making filer listen for smb requests on TCP/445
From what I can find, if a filer is not part of an AD forest, it will not listen on port 445 for SMB requests. Is there a way to change so that it WILL listen on port 445?
I know there is a way to turn it off, but not to force it. We have a process that attempts to contact the windows servers on 445 first and then falls back to 139 if it doesn't work on 445. It causes a small delay, but we have thousands of attempts an hour and even a small delay adds up. We have currently hacked a perl module to get around the issue, but I was hoping there was something we could do on the netapp side.
Thanks Jack