SMB vs Appletalk

I have a Windows 2000 server that is acting as a file server for 5
macs and 5 mixed Windows machines. Currently we are using TCP/IP as
well as Appletalk. When we connect via Appletalk from the Macs all is
well with the only exception being the Appletalk version that comes
with Windows 2000 does not support filenames longer than 32
characters.

We have been getting by in the past by just shortening the names but
it is becoming a problem as more and more of our customers supply
longer filenames.

We can connect via SMB from the mac side and store files on our file
server. This works fine for all data files, (Indesign, Quark,
Photoshop, etc.) but does not work on fonts.

If my research is up to snuff the fonts carry data in the resource
fork that SMB does not see correctly.

If I use Open Type fonts they seem to work but any of the older
postscript fonts with no extensions will not read properly from and
SMB file share.

Does anyone have suggestions for a work around? Is anything I have
stated incorrect?

I was going to install a Linux server with a newer version of
Appletalk that will support filenames longer than 32 characters but
everything I read tells me that the easiest way to fix this is to just
go to SMB.

Any thoughts or suggestions appreciated.

John

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
>I have a Windows 2000 server that is acting as a file server for 5
> macs and 5 mixed Windows machines. Currently we are using TCP/IP as
> well as Appletalk. When we connect via Appletalk from the Macs all is
> well with the only exception being the Appletalk version that comes
> with Windows 2000 does not support filenames longer than 32
> characters.
>
> We have been getting by in the past by just shortening the names but
> it is becoming a problem as more and more of our customers supply
> longer filenames.
>
> We can connect via SMB from the mac side and store files on our file
> server. This works fine for all data files, (Indesign, Quark,
> Photoshop, etc.) but does not work on fonts.
>
> If my research is up to snuff the fonts carry data in the resource
> fork that SMB does not see correctly.
>
> If I use Open Type fonts they seem to work but any of the older
> postscript fonts with no extensions will not read properly from and
> SMB file share.
>
> Does anyone have suggestions for a work around? Is anything I have
> stated incorrect?
>
> I was going to install a Linux server with a newer version of
> Appletalk that will support filenames longer than 32 characters but
> everything I read tells me that the easiest way to fix this is to just
> go to SMB.
>
> Any thoughts or suggestions appreciated.
>
> John
>

I'm not an expert but to add, one of my previous clients is a Win/Mac shop
that had a similar issue with filenames without extensions. Windows users or
customers with Windows could not open the files. This became a real issue
not jsut for customers, but for the staff. We finally settles on using only
SMB and getting rid of APD all together, but we had to do something wth all
the files. To fix it, we found that we had to open each individual file with
the original app, then save it again but this time giving it an extension.
This forced the data and resource forks together so Windows apps could see
them. There were over 12,000, possibly more files. They had to hire someone
to handle this task.

Maybe someone else can help you better with the 32 limit, but I'm not sure
that is possible without upgrading. Good luck!


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Having difficulty reading or finding responses to your post?
Try using Outlook Express or any other newsreader, configure a news
account, and point it to news.microsoft.com. Anonymous access. It's
easy and it's free:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

"Life isn't like a box of chocolates or a bowl of cherries or
peaches... Life is more like a jar of jalapenos. What you do today
may burn your butt tomorrow." - Garfield

"Ace Fekay [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...

The following statement:
"We finally settles on using only SMB and getting rid of APD"

Should have read:
"We finally settles on using only SMB and getting rid of AFP"

Sorry about that...

On Oct 30, 9:10 pm, "Ace Fekay [MVP]" <PleaseAs...@SomeDomain.com>
wrote:
> "Ace Fekay [MVP]" <PleaseAs...@SomeDomain.com> wrote in messagenews:(E-Mail Removed). ..
>
> The following statement:
> "We finally settles on using only SMB and getting rid of APD"
>
> Should have read:
> "We finally settles on using only SMB and getting rid of AFP"
>
> Sorry about that...

If I understand the font issue correctly, Most of the font
information is kept in the resource fork.

Also I am not sure what you mean by upgrading. Are you referring to
upgrading the Macs or Upgrading my server to a Linux box with a newer
version of Appletalk AFP? I am currently using Macs with 10.3.

Thanks for any assistance. As you can see I am not sure if there are
a lot of people that know about this topic. I could find very little
information when I did a Usenet search. I guess it hasn't come up
much.

John

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ps.com...
> On Oct 30, 9:10 pm, "Ace Fekay [MVP]" <PleaseAs...@SomeDomain.com>
> wrote:

> If I understand the font issue correctly, Most of the font
> information is kept in the resource fork.
>
> Also I am not sure what you mean by upgrading. Are you referring to
> upgrading the Macs or Upgrading my server to a Linux box with a newer
> version of Appletalk AFP? I am currently using Macs with 10.3.
>
> Thanks for any assistance. As you can see I am not sure if there are
> a lot of people that know about this topic. I could find very little
> information when I did a Usenet search. I guess it hasn't come up
> much.
>
> John

Not really. It's a pretty niche issue. Many I guess have figured it out and
silently fixed it.

Concerning upgrading, to upgrade to Win2003, which I previously assumed to
support filenames longer than 32 characters, however when I found this
article, it made me realize it was a Mac issue:
http://www.grouplogic.com/knowledge/...w_Bug/docID/79

But as far as the forks, the 9only reference I found is, however our answer
is to open it with AFP and force an extension on it, then open it with a
Windows app:
http://docs.info.apple.com/article.html?artnum=107325

I would search Apple's support site for more info
http://www.apple.com/support/

Good luck!

Ace