Does this mean Yosemite resolves the problem ? There were several posts here before which suggested that this was not the case. It would be good to know that the issue has been resolved. I simply don't dare to upgrade in order not to get into more troubles.
BTW, I resolved the SMB problem in my case, may be someone would be interested. My working environment consists of one MS Server 2008 R2 wich offers shares used by workstations in the local network. Actually the iMacs didn't need the shares, there are VMs, Parallels 10, that are using them. However, the iMacs were causing SMB2 traffic to the server which, as I believe originates from NETBIOSD and server mounts if someone was trying to access the shares from within the iMac. In this situation I had the whole network down for 5-15 min when the machines were powered on. Then everything settled down but the connection to the server was very unstable. There was a lot of SMB2 traffic, absolutely useless in my case, floating between the iMacs and the server.
What I have done on the iMacs was to disable the NETBIOSD by using this command in the terminal:
sudo launchctl unload -w /Library/LaunchAgents/com.apple.netbiosd.plist
I removed all server definitions in Finder > Go > Connect to server. Also created a nsmb.conf file in ~/Library/Preferences/ with the entry:
smb_neg=smb1_only
I made sure that all shared resources are checked off. Also checked the mounted file systems and unmounted those who were SMB driven. Having done that I checked the network traffick from the iMac and didn't register any SMB2 packets. The I ran the Parallels VMs and let the SMB flow between the MS Windows clients and the server which wouldn't cause a problem.
I guess this is not the typical working environment for all but wanted to share the results of my 2 weeks struggle with the Maverick - SMB problem.
Best !