Topic: Again : AppleTalk protocol guestion

[Charles Toepoel]

I recently upgraded my SME server 5.1.2 to 5.5. No problems so far.
Unfortunately I think that there is something wrong in the appletalk protocol. Under 5.1.2 my wife's iMac had no problem connecting to a share on the server. But since the upgrade, all the picture's she opens from a share are corrupt. I also did a clean install of 5.5 but this didn't help.
I re-created the share's on the server. She still uses old shortcuts pointing to server's (old) share name's.

Anybody around who can help me sort out this problem.
Greetz,

Charles

[Maggard]

What do you mean by "all the picture's she opens from a share are corrupt"?

Pictures are pictures - simple binary files that are served up regardless of the protocol. It *is* possible that there is something wrong with the AppleShare server portion that is preventing both forks of classic Mac files (Data & Resource forks) from being served but this would then hold true for any sort of file: Pictures, documents, sound files, and most obviously applications.

Is there evidence of any other sort of file having problem? Are these picture files somehow unusual? What format are they, what application created them, what does she use to view them, and is she opening these images directly from within the Finder or is she browsing to them from within an application? Are there any Mac applications that were stored on a share previously that are not now working? How about applications added since (copying to the share then running "SimpleText" for example)?

Please give some more details, error messages, etc. Describe exactly how these files are being opened, how they are corrupt, and if there are any other files that do or don't open properly. Also if this is true of only pre-5.5 files or is it true for newly added files also?

[Julian Luton]

Hi
This looks similar to a thread running on dev-info recently.
Try this (cut and pasted from dev-info)
..............................................................................................
1.
SME 5.5 related behaviour after upgrading from 5.1.2
---


Hello all,

Problem: an EOF error occurs while opening an Photoshop (Mac) Image file from our SME 5.5 fileserver.

It only happens using Photoshop on Mac, not on any other Software (yet) nor on a PC Version and it is not OS related.

After searching some Netatalk related mailing lists i found out that this behaviour is know and the current release notes shows it is fixed
in 1.5.3.1

I can´t find a RPM yet *sigh*, RedHat latest one is a 1.5.2.x ... Any other sources to search for?

best regards from South Germany
Anton Pirnat

2.
> Or, probably even better for you:
>
> ftp://ftp.e-smith.org/pub/e-smith/contrib/CharlieBrady/RPMS/i386/
>
Hello Charly,

i just tried using your source, thanks for pointing me there i wasn´t sure wich ones at rpmfind.net are redhat based or not. The Redhat ones been older than yours.

After upgrading netatalk using the file above the netatalk config files
/etc/atalk)  been set back to default values.
So i did a /sbin/e-smith/signal-event console-save (guess i´ll get back the e-smith templates thsi way, but i may be wrong but it didn´t work the way expected. After a deeper look (wich is hard to do before the 2.nd cup of coffee at this time of the day)  at the config dir at /etc/atalk i found the right files at /etc/atalk/netatalk, copied them to /etc/atalk, rebooted ..and et voila all works well now.

I also did open some Photoshop files from different places now and all works well there also.

Thanks for helping

Anton Pirnat
.......................................................................................................

Hope this helps,
Julian Luton

[Maggard]

Possibly related:

There's a long-running issue with Photoshop files becoming corrupted, not-opening, funky-behavior on AppleShare volumes where the client doesn't have write access to the root of the volume.

This may have been fixed in some versions of aTalk, it may have also been fixed in some versions of Photoshop, it still pops up regularly as a problem for Wintel folks running AppleShare servers.

[Charles Toepoel]

Actually Julian's solution worked! Thanx again Julian.

Have phun, all of you

Greetz,


Charles