Re: Mac connecting to shared folder on Windows server
by William Smith <mecklists@[EMAIL PROTECTED]
>
Jun 26, 2008 at 10:13 PM
MelPhoto@[EMAIL PROTECTED]
wrote:
> I work in a small office of all Mac users (Leopard). We recently had
> an IT company set up a windows server in our new office. When we
> connect to our shared folder in the data folder on the server we are
> limited to only being able to copy 1 gig of data to it even though
> the IT company said there should be no limit. When I connect to the
> folder remotely through ftp I am not limited by file size but it
> takes much longer to copy. Is there something on the Mac side that is
> creating this limitation? Any advice is appreciated.
Did your contractor use Windows Server's built-in File Services for
Macintosh? If so, shame on them.
The File Services for Macintosh software on Windows Server has not been
updated in years. It's limited to 31 character file names, 64,000 files
per volume and prone to connectivity issues with a modern Mac OS.
I suggest one of these options:
1. Use SMB (Windows file sharing protocol) instead of AFP (Apple's file
sharing protocol).
I have not tested if Leopard has improved its SMB connectivity but Tiger
and earlier are slow IMHO and leave hidden files that can be made
visible to Windows users connecting to your server.
A good SMB client is Dave or ADmitMac from <http://www.thursby.com>.
It's not free but it's very well sup****ted and very well done.
2. Use ExtremeZ-IP from <http://www.grouplogic.com>.
It's expensive but worth it if you have several Macs connecting to your
server.
Given comparable costs between Dave/ADmitMac and ExtremeZ-IP I would go
with ExtremeZ-IP simply because it is an AFP server and AFP is the
native file sharing protocol of the Mac.
Hope this helps!
--
bill
William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>