similar to: AppleTalk(netatalk)+Samba

Hello, Anyone out there running a production network supporting PC and Macintosh clients using samba and netatalk. we are currently using NT 4.0 with AppleTalk-IP software. Sharing the same files with the Macs and the pc is a must. I read someplace that samba 2.2.2 supports Appletalk. Is this true? Thanks, Joe

Hi, I've really tried a lot of things but can't work it out.... I've got a Apple Laserwriter 630 working through appletalk/netatalk. Using lp/lpr I'm able to print, no problem. However, when using samba through Windows ME, the printer will print my pages but also throws out an additional blank page and a page with: ERROR: undefined OFFENDING COMMAND: STACK: This is my

Hello! [Cc to stable@, for wider audience] The plan is two axe two old networking protocols from FreeBSD head/, meaning that FreeBSD 11.0-RELEASE, available in couple of years would be shipped without them. 1) AppleTalk Last time claimed to be supported by vendor in 2007[1]. In practice had very little use since 90th. Discontinued by major routing equipment vendors since 2009[2].

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [please cc to my address] Dear Samba and Netatalk experts, I've got a server running both samba 2.2.3a as PDC and netatalk (1.5pre7 as supplied by SuSE73). Samba machine accounts are added to /etc/passwd automatically by the command add user script = /usr/sbin/useradd -d /dev/null -g 90 -s /bin/false -M %u when a NT machine is added to the

Hi, Is it from my eyes, or Centos (or for that matters, RHEL) doesn't include netatalk ???? If not, does it bring something else for the same porpous ? Any help would be appreciated. Warm regards, M?rio Gamito

I suppose this has already been asked and someone is going to tell me what chapter of the HOWTO to read but has anyone configured a Linux server to link up Windows whatever(say ME) and Mac OS X. Is this the best(highest speed and cheapest we are talking small non-profit.org here) way to do it? That is have a Linux machine doing everything a server does-this way dont have to waste G4 on server

Take a look at this output from lsof: smbd 11490 0 8u REG 3,3 55296 1136647 Maintenanc.fp5 afpd 31010 0 2u REG 3,3 3207 1136655 auction - envelope.rtf afpd 31010 0 5u REG 3,3 4156 1136656 Word Work File L 1 afpd 31010 0 8u REG 3,3 55296 1136647 Maintenanc.fp5 smbd 31386 0 9u REG 3,3 4156 1136656 Word Work

Hi all, Looking for a "best practices" way to share out to both Mac and PC easily. I know Windoze enables the same sharepoint for both the mac and pc shares and there don't seem to be any real "problems" by doing that. However I work in an environment which forces us to utilize Win9x through XP as well as OS 9 through 10.x on the mac side. I need a user friendly way to

since "ea = samba" was only added to very recent netatalk versions and so don't apply to files with a history of many years what is the way to go get rid of netatalk these days? is there still no tool to read/write the existing netatalk appladouble extended attributes which are *not* compatible with samba and write them back in the new format? afp.conf: appledouble = ea ea = samba

I recently took over a x86_64 CentOS 4.0 server running an "unsupported" kernel. On examining the box it seems that perhaps it is because of the use of xfs and netatalk. I would like to update the box to 4.3. I think I can do away with the netatalk, but doing away with xfs would require a substantial amount of work. Questions: 1: In reading the archive of this list there was a post

On Thu, May 17, 2018 at 04:49:11PM +0200, Reindl Harald via samba wrote: > > > Am 17.05.2018 um 16:17 schrieb Ralph Böhme: > > On Thu, May 17, 2018 at 03:44:12PM +0200, Reindl Harald via samba wrote: > >> Am 17.05.2018 um 14:22 schrieb Ralph Böhme: > >>> iirc the only thing that is currently not working is cross-protocol xattrs for > >>> xattrs

On Thu, May 17, 2018 at 05:01:57PM +0200, Reindl Harald via samba wrote: > > > Am 17.05.2018 um 16:56 schrieb Ralph Böhme: > > On Thu, May 17, 2018 at 04:49:11PM +0200, Reindl Harald via samba wrote: > >> > >> Am 17.05.2018 um 16:17 schrieb Ralph Böhme: > >>> On Thu, May 17, 2018 at 03:44:12PM +0200, Reindl Harald via samba wrote: >

On Sun, Dec 27, 2015 at 02:33:10AM +0900, HAT wrote: > Sat, 26 Dec 2015 17:22:56 +0000, Rowland penny <rpenny at samba.org>: > > On 26/12/15 17:08, HAT wrote: > >> Hi, > >> I'm testing samba 4.3.3 vfs_fruit on Fedora rawhide. > >> > >> The EAs are not seen from clients yet. > >> > >> smb.conf: > >> path =

Hi. I'm testing samba 4.2.0 vfs_fruit on Fedora Server 22-alpha. I confirmed that ResourceFork and FinderInfo are compatible with Netatalk 3.1.7. However, EAs are incompatible. The character ":" in EA name is wrong. The EAs are not seen from clients. smb.conf: [test2] path = /export/test2 writable = yes vfs objects = catia fruit streams_xattr fruit:locking =

Hi, I've got a SuSE 9.0 running Samba 3.0.1 and Netatalk 1.6.3 Samba is a member server of a win2k domain, I'm using winbind to authnticate my users. Well, with the Windows users, everything is ok. But not with the Mac users I'd like to setup Netatalk to authenticate my Macs against the win2k domain as with Windows. Is this possible? I've sarched the web all around and

Hi all, I'm have a Linux Box running samba and netatalk, and a file system shared with Mac and Windows users. My problem is that when a user in Windows delete a file that have a Macintosh label (color), and later the Windows user put another version of the file with the same name, the Macintosh label still apear (and this is not the behavior that i need). I view in the file system that

On Fri, Dec 18, 2015 at 01:14:25AM +0900, HAT wrote: > Hi, > > >> not sure, but the colon in xattr names is probably not handled > >> correctly at this point. Can you please file a bugreport so we can > >> track this? > > > > Bug 11162 > > https://bugzilla.samba.org/show_bug.cgi?id=11162 > > I tested samba 4.3.1 on Fedora 23 and rawhide.

On 26/12/15 17:08, HAT wrote: > Hi, > I'm testing samba 4.3.3 vfs_fruit on Fedora rawhide. > > The EAs are not seen from clients yet. > > smb.conf: > path = /export/test1/ > writable = yes > vfs objects = catia fruit streams_xattr > fruit:locking = netatalk > fruit:encoding = native > streams_xattr:prefix = user.

Client: Dual 1GHz G4 OSX 10.2 Gig-Ethernet Server: Dual 2GHz P4 Linux 2.4.18 Raid-5 1TB Gig-Ethernet With netatalk 1.5.5 I get sustained writes of 66MB/s (yes, megabytes) With samba 2.2.7a I get sustained writes of 15MB/s I've tweaked the settings and ended up with these: socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 IPTOS_LOWDELAY SO_KEEPALIVE read raw =

hi@all i'm using netatalk and samba as fileserver for different clients (OS9,X,WinNT/2K/XP) to create shares, that are visible and accessible for all clients (via afp/smb) i created a folder and made it public in all daemons (atalk, samba) to get a better file handling i'm using the samba feature: vfs object = netatalk but there are still some problems files that are created via afp