Ok, the common workaround that people seem to have accepted as a 'fix' is disabling packet signing on the server. Now, if I were a user that was sitting at a single desk in a single company all the time, I might try and convince the sysop that it ain't such a bad idea.
However, I roam, my desk is whereever my work takes me and my apple is my office. Now the Apple tauts interoperabillity, and usually lives up to the claim. In this case however I am stumped. Samba3 supports packet signing, some of my colleagues use linux distro's on their laptops and connect without a sweat to the same machines that I get bounced off. So, Samba should be capable, OS X 10.4. are we at 6 alread? is not capable.
Now, to get back to my question, has anybody here the knowledge to fix this? Logically I would say manually updating Samba. I've tried using the samba3 package from darwinports, which installs fine, but how do I tell mount_smbfs to use the somewhat new(ish) samba 3.0.20b binary instead of the crippled and outdated 3.0.10 that comes packaged with OSX. Or do you have a different idea to crack this egg. (And no fiddling with the server, I can't be bothered to request someone to 'fix' their server every time I walk into a different company).