i found something in mac os x console.log:
Sep 6 22:36:53 mescal kernel: smb_iod_recvall: tran return NULL without error
Sep 6 22:36:53 mescal last message repeated 7 times


regards,
jens

On 06.09.2004, at 22:01, Jens Francke wrote:

Hi hans,

i can mount the shares from a gentoo box just fine.
i also checked the logs of the debian box. nothing special found there. from the debian side it seems the user is perfectly logged in. but both of my os x boxes (Powerbook and a G5) have problems mountng the shares.
The same Macs can jsut mount find the samba 3.0.5 share from the gentoo box.
what you mean by " that the name-resolution is not working as before." . no changes in dns have been made. all boxes have reverse lookups.


i tried another thing: i can mount the samba share in os x using mount_smbfs in cli. i can even browse the share in cli.
the moment i try to access the same shares in finder i get a spinning beachball aka the finder.


what are these .__files all over the place if i look at the shares in cli. resource/finderinfo īs ? maybe they are the cause ?!

thanks for add. hints !

regards ,
jens

On 06.09.2004, at 20:36, Hans-Georg Bork wrote:

Hi Jens,

On Mon, Sep 06, 2004 at 08:01:13PM +0200, Jens Francke wrote:
[...]
right after auth and mounting my shares i simply just get the "spinning
beachball" aka finder is locked.
this wont stop until i stop samba on the debian box or restart my os x
client mac.

to check the config (and other things), try to mount the shares directly
on the debian-box using smbmount (same user as on os x).
If that goes without any trouble, it seems, that os x tries to mount them
in a way, the updated smbd does not (anymore) understand or that the name-
resolution is not working as before.


Did you already check the samba-logs (and the syslog) for any traces of
these trials? If not, check them before the mounts above and immediately
after them to get an idea what happens.


HTH

Regards
        -- hgb


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]








Reply via email to