- This topic has 0 replies, 1 voice, and was last updated 19 years, 2 months ago by
.
-
Posts
-
Hi
I’m new here as a poster and was hoping to pick some people’s brains about my concerns.
We have a company with multiple locations that will need to share files.
Our NY location works off a OS X Server 10.4 and connect to it by afp.
Our Connecticut location has art and typesetting departments. Typesetting mainly work off an win2000 server with services for macintosh running due to the fact that they are still on OS 9. In the process of their migration I need to know the proper and most efficient way for our typesetting clients to connect to their win2000 server either AFP, SMB or Admitmac’s CIFS/SMB. Keep in mind that they will occasionally need to connect to our NY OS X server to share files.
Using native SMB we run into the issue of resource forks and problems with links in quark. AFP is real slow in connecting, file transfers and listing files on shares. Admittmac seems like a nice solution because of having clients join the domain, security and a cure for resource forks. Finally ExtremeZ-IP with it’s single sign on and Kerberos and newer afp.
Right now in a mixed environment of OS 9 and OS X we are going to see issues with files and sharing. EXAMPLE – a file modified in quark 6.5 on OSX with Admitmac installed saved to the win2000 server does not show as being modified on an OS 9 machine connecting with AFP. I’m aware of that and I’m pretty confident if we use admitmac when everyone is on OSX there will no longer be an issue with these kinds of problems.
The part that I’m not to sure about it what about the people in NY that need to share files from an OSX server connected by afp to the typesetting department that is using admitmac’s smb. Will they be able to share files without any issue?
What option is the best. Curious to see what everyone else is doing
- You must be logged in to reply to this topic.