Samba and OS4.1 Udate 6

[sandpiper]

I recently made a clean install of OS4.1 update 6. After everything was setup, almost immediately I started experiencing system freezes, sometimes right after boot-up but sometimes later seemingly at random. It took me quite a while to narrow down the cause but it appears to be Samba, namely nmbd, the netbios name server. Since I disabled nmbd and smbd in Internet preferences ('de-activated' in the Severs section) the system has been very stable with no freezes.

I have been using Samba on this machine (micro A1, 512MB) since 2004 without issue, so this is something new. For now I'll just stick to smbfs to access my other machines. Anyone else experience this issue?

[Spectre660]

I had some random freezes with Samba with earlier OS4.1 updates on a Sam440ep-Flex. I traced these down to runing Dockies in Amidock.

I recently made a clean install of OS4.1 update 6. After everything was setup, almost immediately I started experiencing system freezes, sometimes right after boot-up but sometimes later seemingly at random. It took me quite a while to narrow down the cause but it appears to be Samba, namely nmbd, the netbios name server. Since I disabled nmbd and smbd in Internet preferences ('de-activated' in the Severs section) the system has been very stable with no freezes.

I have been using Samba on this machine (micro A1, 512MB) since 2004 without issue, so this is something new. For now I'll just stick to smbfs to access my other machines. Anyone else experience this issue?

[Christopher Follett]

I had some random freezes with Samba with earlier OS4.1 updates on a Sam440ep-Flex. I traced these down to runing Dockies in Amidock.

I recently made a clean install of OS4.1 update 6. After everything was setup, almost immediately I started experiencing system freezes, sometimes right after boot-up but sometimes later seemingly at random. It took me quite a while to narrow down the cause but it appears to be Samba, namely nmbd, the netbios name server. Since I disabled nmbd and smbd in Internet preferences ('de-activated' in the Severs section) the system has been very stable with no freezes.

I have been using Samba on this machine (micro A1, 512MB) since 2004 without issue, so this is something new. For now I'll just stick to smbfs to access my other machines. Anyone else experience this issue?

Thats interesting. I have been having trouble since update 5, after update, samba would mount 1 drive and ignore all others. Before it would see them all.
I have'nt had freeze ups, but will check dockies, see if it solves mounting issue.

[abalaban]

@Christopher

If you only want to mount remote drives on your Amiga then don't spend time on installing/configuring/etc. Samba. What you really want is 'smbfs' this is a simple handler that will do the trick of mounting on your Amiga any amount of NetBios drives.

[Christopher Follett]

@Christopher

If you only want to mount remote drives on your Amiga then don't spend time on installing/configuring/etc. Samba. What you really want is 'smbfs' this is a simple handler that will do the trick of mounting on your Amiga any amount of NetBios drives.

Im using smbfs mounter.

[abalaban]

@Christopher

I don't know how smbmounter works, however I'm using smbfs in a custom script (the script mount 3 drives) called from network-startup on my own X1000 and A1XE since age and never had any problem of partially mounted drives...
Strange, maybe it worth investigating with smbmounter author?

[cha05e90]

All my AmigaOS systems run Samba (except the A1000), all of them use SMBMounter/smbfs to connect to the shares. Mounting more than one share isn't problem, so I think it should'nt be a Update5 or 6 problem. I only had one occasion where the nmbd ran amok because I had accidentally two Samba machines with the same IP in my network.

@abalaban

SMBMounter is a frontend for smbfs (and Samba for some minor functions if it is available).

[Joeled]

I m using sambafs and smbmounter but i never managed to get it to automount my nsa210. I choosed "automount on startup" but i have to mount it manually. Oterwise is working really nice.

[Christopher Follett]

Might be coinsidence. I have it mounting all now, but it refuses to auto mount since update 5.
I tried altering the position in WBStartup as it had moved, but doesnt help, I just get smbmounter has'nt returned and it pops up gui even though it set to no gui (auto mount).

[Spectre660]

I dont normaly use automount but I just tested it starting SMBMounter from WBStartup as the last item in WBstartup and it mounted the single Windows XP share that I had set to automount ok on bootup.

On app that has caused me some problems with WbSstartup is Limpidclock, I have it set to start first with a start priority of 2 .

Might be coinsidence. I have it mounting all now, but it refuses to auto mount since update 5.
I tried altering the position in WBStartup as it had moved, but doesnt help, I just get smbmounter has'nt returned and it pops up gui even though it set to no gui (auto mount).