[Samba] Mac OSX Tiger 10.4.2 SMB

Neil Wilson neil at dcdata.co.za
Thu Aug 4 12:20:07 GMT 2005


Hi Guys and girls,

I'm having exactly the same error as this person in the post below had.
Only differences is we are running Slackware 10.1 with Samba 3.0.14a, and 
the Mac connecting is using 10.4.2

Does anyone know of a work around, or a solution to the problem?

Any help would be appreciated.

Thanks.

Neil Wilson
Powered by Linux, Driven by Passion !

[Samba] OS X 10.4.1 ( Tiger ) client borked
cliff white cliffw at easystreet.com
Mon May 23 20:31:38 GMT 2005

Previous message: [Samba] OS X 10.4.1 ( Tiger ) client borked
Next message: [Samba] Configuration on Sun Solaris 9/Sun SPAARC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mon, 23 May 2005 07:53:42 -0500
"Gerald (Jerry) Carter" <jerry at samba.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> cliffw wrote:
> | Appears Apple messed something up in 10.4,and 10.4.1.
> |
> | Attempting to connect to a 3.0.14a server (debian unstable)
> | from an OS X client causes OS X Finder to hang, and puts
> | these errors in the samba server logs:
> |
> | [2005/05/22 21:48:20, 0] rpc_parse/parse_prs.c:prs_mem_get(537)
> |   prs_mem_get: reading data of size 2 would overrun buffer.
> | [2005/05/22 21:48:20, 0] rpc_server/srv_pipe.c:api_pipe_bind_req(919)
> |     api_pipe_bind_req: unable to unmarshall RPC_HDR_RB struct.
> |
> | Apparently it's also causing breakage in some NAS boxes
> | ( Adaptec's Snap is mentioned )
> |
> |>From a 'level 2' guy on Apple's support forum ( re: a Snap report ):
> |
> | "Tiger does a kind of authentication called NTLMv2,
> | which Panther did not attempt to do. NTLMv2 is more secure than
> | the kind of authentication Panther did, but Snap may not support
> | it correctly. Snap grants Tiger only "guest" access instead of the
> | full user access requested, and "guest" access is not sufficient
> | to even get a list of the files. Panther works OK with Snap because
> | it doesn't attempt MTLMv2 authentication. "
> |
> |
> | Any chance this is the same problem i'm seeing?
>
> Possibly.  Can you send me a level 10 debug log from
> smbd and a raw ethereal trace file?  tcpdump is fine
> if you use this following command:
>
> tcpdump -w dump.pcap -s 0 -i eth0 port 139 or port 445
>

I did two tests for you, but nothing captured on port 445.
Two tarballs of test logs, and one tcpdump file enclosed
cliffw

>
>
>
> cheers, jerry 



More information about the samba mailing list