• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3765
  • Last Modified:

How to use Windows 2003 as a file server for OS X

Does anyone know the best solution for this problem?

As far as my online research shows, the MAC OS file System (HFS) and Windows NTFS are incompatible. I was able to set up File Sharing for Macintosh on the Win03 server, share afolder ect. But when copying up a large folder, I get:

Can not copy the item: "file name" because the name is too long or includes characters that the disk cannot display.

I think it has something to do with the way the MAC creates it's file names or something.

I have a client that has 3 MAC OS X machines, and they bought a new Windows 2003 server, and want to use it as the file server, but I can't get their data there. This has been driving me crazy for weeks now. Any ideas or options?

Thanks all, Ken
0
kfnetworks
Asked:
kfnetworks
  • 5
  • 4
  • 3
1 Solution
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
HOW EXACTLY are the Macs connecting to the Windows server?  AFP:// or SMB://?

SMB:// is overall better but I can imagine having those problems.
AFP:// requiest Microsoft's Services for Macintosh and that feature is just not very good in the grand scheme of things.

You might try setting up NFS - since MacOS is *nix based, you can probably connect via NFS if you setup NFS on the Windows system - I'm just not sure how as the last time I tried to it was at least 6 years ago.
0
 
brettmjohnsonCommented:
If you only have Mac OS X clients, drop Windows File Services for Mac and stick with SMB file sharing.
[Mac OS X does Windows file sharing a whole lot better than Windows does Mac file sharing.]

You might also consider installing Rendezvous/Bonjour for Windows on the server.  It will help the Macs in the autodiscovery of file and print services offered by the Windows box.
http://www.apple.com/support/downloads/bonjourforwindows103.html

0
 
kfnetworksAuthor Commented:
Currently I set up access using AFP. I will try strictly SMB and let you know. The office is made up of 3 MACs and 3 PC's. I will try installing bonjour too.
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
Lee W, MVPTechnology and Business Process AdvisorCommented:
As I said, Services for Mac is not very good.  SMB should make things better.
0
 
kfnetworksAuthor Commented:
Just tried using SMB and I still get the error:

Can not copy the item: "file name" because the name is too long or includes characters that the disk cannot display.

I see all the shares I created on the Windows server fine from the MAC. The main issue is copying up these 25 gigs of MAC creative files.

So maybe this is a dead horse, and there are fundamental issues that Apple and Microsoft need to work out. I can copy the same files MAC to MAC no problem. My reasearch tells me that a FAT32 partition would work fine with a MAC but I need to set security so that is out. The only other thing I thought of was trying to format an external HD as HFS, and attaching that to the Windows server. Doubt it will work though.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Copy a few files at a time - post the name of the file(s) that are not copying.
0
 
kfnetworksAuthor Commented:
The file is balks on first is "777 C/O" There is no extension on it.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Windows cannot handle files with a "/" in it - change that.  IT will copy with a "-"

There are several reserved characters in windows - and a few reserved file names.  I may be missing one or two, but characters that cannot be in a file name:

/\:<>*?

0
 
brettmjohnsonCommented:
> Can not copy the item: "file name" ...

What exactly is "file name"?  The message is complaining about path length and/or special chars.  Mac users have this annoying habit naming files using very long names, mixed case, embedded whitespace, and every punctuation character on the keyboard:
    Fred's notes on "The DaVinci Code" (the movie, not the book) 06/12/2006 [original f*cked-up version]
You may need to modify the names of Mac files that contain characters that not valid in Windows filenames.  This is just one of the hazards of sharing files in a heterogeneous environment.


> The only other thing I thought of was trying to format an external HD as HFS, and attaching that to the Windows server.

That won't work.  Windows cannot mount HFS partitions.


Personally, I would have installed an XServe to act as a fileserver for the Macs.   Not only does support Macs seemlessly, it actually serves up files via SMB to Windows clients faster than Windows servers do.
0
 
kfnetworksAuthor Commented:
Thanks for the help. Now I just need to go thru 25 gigs of legacy MAC data to find illegal characters. Hope Automator is up to the task. Here is a link from Apple on illegal characters:

http://docs.info.apple.com/article.html?artnum=107032
0
 
brettmjohnsonCommented:
> Hope Automator is up to the task.

Better off to use the 'find' command from the Unix shell.

0
 
kfnetworksAuthor Commented:
Automater was a nightmare - I am sure it could do it, but I opted for A Better Finder Rename program ($19.99), and it took out all the illegals. Using SMB beacuse AFP on the Windows side restricts to 31 characters. Finally !!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now