Hi Amanda,
My company makes ExtremeZ-IP File Server (EZ-IP), a replacement for
Microsoft Services for Macintosh (SFM) that Josh mentioned.
We are very familiar with the issues that you describe, both technical and
political.
Please let me know if I can answer any questions for you or arrange for
someone to visit you in the UK.
- Reid
T. Reid Lewis
President
Group Logic, Inc.
1110 N. Glebe Rd, Suite 450, Arlington, VA 22201 USA
Tel: +1.703.528.1555 Dir: +1.703.527.7979x2440 Fax: +1.703.528.3296
Bus Email: email@hidden
Skype: reidlewis AIM: Reid Lewis ichat: reidlewis
Personal Email: email@hidden
Web: www.grouplogic.com
Creators and publishers of:
ExtremeZ-IP File Server: Macintosh file server for Windows 2003/XP/2000/NT
ExtremeZ-IP Print Server: Macintosh print server for Windows 2003/XP/2000/NT
MassTransit: automated file transfer solution for Windows & Macintosh
Installation, integration and professional services for our products
On 4/27/05 7:08, "Josh Wisenbaker" <email@hidden> wrote:
>
> On Apr 27, 2005, at 4:51 AM, Clark, Amanda (Harcourt Ed) wrote:
>
>> Hi there
>> I'm having a fight with the PC tecs that support the PC Servers
>> that the
>> Macs have to store there files on.
>>
>> They want us to connect using SMB rather than AFP
>>
>> But with SMB the files all lose there associations and we get strange
>> gremlins creeping into the file and folder names so the links in
>> documents
>> no longer work.
>>
>> This is OSX.3 and Win2K servers and we are connecting by going to
>> Apple +K and typing in smb://server/share
>>
>> Any clues? - do we just have to live with this with SMB problem?
>> Has anyone come across it and found a solution?
>
> The problem you are seeing is that you copied the files up via SFM
> and when you view them with SMB they have no forks. This is because
> SMF stuffs the fork away in a NTFS stream while the Finder separates
> the fork out into a ._ file on non-fork aware volumes.
>
> My order of preference for dealing with Windows servers is:
>
> 1. EZIP
> 2. SMB
> 3. Anything I can think of that's not SFM
> 4. SFM
>
> Once you pick one way to connect you should stick with it. Otherwise
> you get the fork and name length inconsistencies.
>
> The only way to migrate really is to copy the data from the SFM share
> to a SMB share via a Mac.
>
> Josh
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Client-management mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/client-management/email@hidden
This email sent to email@hidden