Re: Mac OS9 and accessing existing shares on Server 2003/2000 at login

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Jim Seifert [MSFT] (jimsei_at_online.microsoft.com)
Date: 03/25/04 

Date: Thu, 25 Mar 2004 15:48:48 -0800

Each Macfile share must be created in one of two ways, in Computer Manager
by creating a new share or using the command - macfile volume /add.
The syntax of this command is:

    MACFILE VOLUME /ADD
        [/SERVER:\\computername] The default is local.
        /NAME:volumename
        /PATH:root directory path
        [/READONLY:TRUE|FALSE] The default is True. (There is a
bug here - the in build help says false.)
        [/PASSWORD:password] The default is no password.
        [/MAXUSERS:number|UNLIMTED] The default is unlimited. 

-- 
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Maurice" <mve@fastmail.fm> wrote in message
news:2602221e.0403242140.41e43579@posting.google.com...
> Hello
>
> I have Windows Server 2003 and a Mac OS9 client.  I can login
> successfully but the only volume that comes up is the Microsoft UAM
> volume,
> which I have copied into the AppleShare folder (with Chooser, etc
> closed).
>
> However none of the shares on Server 2003 are visible. In
> particular, we have a "Personal" directory (with numerous domain-user
> subfolders)  and a "Lab_data" directory for
> example, which are accessible by users on Windows and Mac OS X
> computers
> (using SMB).  There seem to be no options for exposing the existing
> shares on the Server 2003 computer to the Mac OS 9 clients under
> Computer Management -> Shared Folders -> Shares.  I know that NEW
> shares can be created and have a Macintosh-enablement option.  I can't
> help but think I am missing something obvious. Searching "macfile" in
> help suggests though that if you have have shared folders under
> Shares, that those will just be naturally shared under mac file
> services, which is indeed installed and running.
>
> Strangely, our old NT4 Server allows one to create Mac volumes from
> existing shares, so there's got to be a way to do it under Server 2003
> I'd think. When you login to the NT4 machine from a Mac OS9 computer,
> you get volumes "Personal" and "Lab_data" as ones that can be
> accessed.
>
>
> If anyone has any insight on this issue, it'd be appreciated.

Relevant Pages

  • Re: Network printing from Mac OSX 10.4.9
    ... file servers to which Macs are successfully accessing shares. ... thinging that would allow the Mac ... I used RSOP to verify that the server was using the expected settings. ... You also say that you applied a test policy that overrides the SMB signing ...
    (microsoft.public.windows.server.general)
  • Re: OS X Clients had connectivity...Now they lost it
    ... See if Appletalk is still set to accept inbound connections on the ... Try connecting from a Mac using afp://serverIP ... >I have a W2k3sp1 server with Mac Shares on it. ... > and now after a reboot the clients can't connect to any of the shares. ...
    (microsoft.public.windows.server.networking)
  • Mac OS9 and accessing existing shares on Server 2003/2000 at login
    ... I have Windows Server 2003 and a Mac OS9 client. ... However none of the shares on Server 2003 are visible. ... When you login to the NT4 machine from a Mac OS9 computer, ...
    (microsoft.public.win2000.macintosh)
  • Re: Mac clienst cant see all shares on Win 2000 server
    ... > Mac clients that access 10 shares on this server. ... Try deleting the Mac volumes and then recreating them. ...
    (microsoft.public.win2000.macintosh)
  • APPLE-SA-2011-10-12-3 OS X Lion v10.7.2 and Security Update 2011-006
    ... Mac OS X v10.6.8, Mac OS X Server v10.6.8, ... CVE-2011-0419 does not affect OS X Lion systems. ... A signedness issue existed in ATS' handling of Type 1 ...
    (Bugtraq)