samba - May 2005 - Problems with Tiger SMB connections

I came across this message on another mailing list, I was hoping people 
here may have some ideas?

Thanks,
Trevor

---

Is anybody else having problems connecting to SMB shares with Tiger?
I appear to authenticate ok, but then I get this error.

The Finder cannot complete the operation because some data in "smb://
<theserver/theshare>" could not be read or written. (Error code -36).

I check the logs and found these two entries every time I've tried to
connect.

May  3 12:43:49 Nugget kernel[0]: smb_maperr32: no direct map for 32
bit server error (0xc00000bd)
May  3 12:43:49 Nugget kernel[0]: smb_maperror: Unmapped DOS error 1:52

I also did a tcpdump while trying to connect and can see that
successful connections are occurring between me and the server on 137/
UDP, 139/TCP, and 500/UDP.

If anybody has any ideas on this one, I'd love to hear them.

thanks,
-Mike

There are apparently API changes in Tiger (a.k.a. Mac OS X 10.4,
released last Friday, April 29, 2005) that broke other things -- for
example, Cisco's VPN client (and most others).
   Does anyone from samba.org know whether or not Samba is affected?
--
Will Enestvedt
UNIX System Administrator
Johnson & Wales University -- Providence, RI
>
> Sent: Tuesday, May 03, 2005 2:04 PM
> To: samba@lists.samba.org
> Subject: [Samba] Problems with Tiger SMB connections
> 
> 
> I came across this message on another mailing list, I was 
> hoping people here may have some ideas?
> 
> Thanks,
> Trevor
> 
> ---
> 
> Is anybody else having problems connecting to SMB shares with Tiger?
> I appear to authenticate ok, but then I get this error.
> 
> The Finder cannot complete the operation because some data in "smb://
> <theserver/theshare>" could not be read or written. (Error code
-36).
> 
> I check the logs and found these two entries every time I've tried to
> connect.
> 
> May  3 12:43:49 Nugget kernel[0]: smb_maperr32: no direct map for 32
> bit server error (0xc00000bd)
> May  3 12:43:49 Nugget kernel[0]: smb_maperror: Unmapped DOS 
> error 1:52
> 
> I also did a tcpdump while trying to connect and can see that
> successful connections are occurring between me and the server on 137/
> UDP, 139/TCP, and 500/UDP.
> 
> If anybody has any ideas on this one, I'd love to hear them.
> 
> thanks,
> -Mike
>