Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Mounting Windows Server 2003 & NT with 10.3' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Mounting Windows Server 2003 & NT with 10.3
Authored by: stingerman on Jun 04, '04 09:40:17AM

Yep, basically this is what it comes down to:

-If your OS 9 users are using AFP to connect to Windows server then:
For OS X users to work with the OS 9 files correctly, they need to connect to the same Windows server using AFP.

-If you copy anything from OS 9 to Windows, then the only way for OS X to understand the meta data is to connect to Windows via AFP.
-If you copy anything from OS X to Windows, then your OS 9 users need to connect to windows through AFP to see the Meta data.
-Physically copying from OS X to Windows to OS 9 will lose the resource and Finder meta data, and vice versa. You need to not use WIndows as a go between.

The real solution is to use a OS X server for your Mac and Windows clients or to only connect to Windows shares using AFP. The new OS X Server (Panther) probably is the best solution as it provides a robust Open Directory with AFP, SMB along with being able to be a controller (Primary, WINS, etc) and participate in a active directory with replication. Since the Disks are formated as HFS+, you'll have no problems all around. You'll also benefit from faster File and Print sharing than even Windows servers provides its own Windows clients. (and you have the justification to buy a Xserve G5 and Xraid that you've been looking for. In fact, with unlimited clients on OS X server, it is a far cheaper though more robust solution to Windows.)



[ Reply to This | # ]
Mounting Windows Server 2003 & NT with 10.3
Authored by: osxpounder on Jun 04, '04 11:26:34AM

Like a lot of us, I connect to Windows machines and use a Mac primarily. So far, I've had few problems moving the following types of files to and from a Windows machine, then using the files later:

Photoshop, Flash and Word documents
image files of various types, incl. JPG, TGA, GIF, TIF
PDF
WAV, MP3, and AIFF
TXT
QuickTime MOV
MPG and DV video files

If I don't use Classic apps or OS9, should I expect, or look out for, problems with files that have been on a Windows volume? I use QuickTime a lot, as well as image and audio files, but so far haven't had any problems with the resource-thingies. I enjoy the ease with which I can copy files to and from my Win2k boxes; I didn't realize there were dangers afoot.

---
--
osxpounder



[ Reply to This | # ]
Mounting Windows Server 2003 & NT with 10.3
Authored by: LittleSaint on Jun 04, '04 11:46:03AM

Or you can just make sure you use file extensions and you'll have no problems no matter how you connect. I think people need to realize that as Apple becomes more commited to enterprise environments, there is a good chance metadata will become extinct much like AppleTalk. So, get used to using file extensions now.



[ Reply to This | # ]
Mounting Windows Server 2003 & NT with 10.3
Authored by: montalvd on Jun 06, '04 12:06:44PM

> I think people need to realize that as Apple becomes more
> commited to enterprise environments, there is a good chance
> metadata will become extinct much like AppleTalk. So, get
> used to using file extensions now.

with all due respect, that's absurd. afp services are part of windows 2003. macintosh users in design/production groups can NOT "simply use file extensions". the solution is to ensure afp (which NO i.t. department would have a problem with...remember, afp is NOT appletalk).

users need to be trained to recognize the difference between an afp and an smb connection dialog box. then if a user is prompted to log in via smb, he/she should raise a flag...because afp connectivity isn't working properly (whether it's a client or server issue).

the solution is to simply ensure afp services is up and that users connect via afp. "working around" the problem by using file extensions does NOT solve the problem.

don't think for a minute that afp is a problem for any competent i.t. person...on the other hand, appletalk is and always was a p.i.t.a that most i.t. departments do NOT want running on their network.

don montalvo, nyc

---
don montalvo, nyc



[ Reply to This | # ]
Mounting Windows Server 2003 & NT with 10.3
Authored by: montalvd on Jun 06, '04 12:10:50PM

> I think people need to realize that as Apple becomes more
> commited to enterprise environments, there is a good chance
> metadata will become extinct much like AppleTalk. So, get
> used to using file extensions now.

with all due respect, that's absurd. afp services are part of windows 2003. macintosh users in design/production groups can NOT "simply use file extensions". the solution is to ensure afp (which NO i.t. department would have a problem with...remember, afp is NOT appletalk) services are running.

users need to be trained to recognize the difference between an afp and an smb connection dialog box. then if a user is prompted to log in via smb, he/she should raise a flag...because afp connectivity isn't working properly (whether it's a client or server issue).

the solution is to simply ensure afp services is up and that users connect via afp. "working around" the problem by using file extensions does NOT solve the problem.

don't think for a minute that afp is a problem for any competent i.t. person...on the other hand, appletalk is and always was a p.i.t.a that most i.t. departments do NOT want running on their network.

don montalvo, nyc

---
don montalvo, nyc



[ Reply to This | # ]