2003 SBS share permissions

[Jon Jones]

I have a client with Windows Server 2003 SBS installed. They have a

 

[William Smith]

[/QUOTE]


Hi Jon!

Based on your description, I would guess that you have Mac OS X machines
connecting to an SBS server that's running the built-in File Services
for Macintosh. Correct?

If so, then you may want to look into a third party AFP server such as
Group Logic's ExtremeZ-IP (http://www.grouplogic.com). Mac OS X uses AFP
3.x whereas Microsoft's File Services for Macintosh still uses AFP 2.2.
AFP is the Mac's native file sharing protocol and the difference between
the two versions can cause the symptoms you're seeing. Group Logic
offers a 30-day trial for you to test.

If your Macs are connecting via SMB (Windows file sharing), then I would
suggest using another SMB client such as Dave or ADmitMac from
http://www.thursby.com. These are far better and more robust SMB clients
than what's built in to Mac OS X. Thursby also offers 30-day trials of
its software.

Hope this helps! bill

 

[Jon Jones]

Hi Jon!

Based on your description, I would guess that you have Mac OS X machines
connecting to an SBS server that's running the built-in File Services
for Macintosh. Correct?

If so, then you may want to look into a third party AFP server such as
Group Logic's ExtremeZ-IP (http://www.grouplogic.com). Mac OS X uses AFP
3.x whereas Microsoft's File Services for Macintosh still uses AFP 2.2.
AFP is the Mac's native file sharing protocol and the difference between
the two versions can cause the symptoms you're seeing. Group Logic
offers a 30-day trial for you to test.

If your Macs are connecting via SMB (Windows file sharing), then I would
suggest using another SMB client such as Dave or ADmitMac from
http://www.thursby.com. These are far better and more robust SMB clients
than what's built in to Mac OS X. Thursby also offers 30-day trials of
its software.

Hope this helps! bill[/QUOTE]


Bill,

That does explain our setup. The Macs are up to the latest OS X release and
the 2003 SBS is updated with all the latest patches. We are using the built
in Macintosh services on the Server. But to tell you the truth I'm not sure
which way we are connecting.

The Macs use their network connect and then enter the ip network name for
the server and the share they want to connect to (\\server\macshare) and
when that connects they enter the user name and password assigned to them on
the server. This creates the connection and leaves a shortcut to the share
on their desctop.

With this new information which service that you suggested would be the best
one to use?

Thank you,
Jonathan F. Jones

 

[William Smith]

That does explain our setup. The Macs are up to the latest OS X release and
the 2003 SBS is updated with all the latest patches. We are using the built
in Macintosh services on the Server. But to tell you the truth I'm not sure
which way we are connecting.

The Macs use their network connect and then enter the ip network name for
the server and the share they want to connect to (\\server\macshare) and
when that connects they enter the user name and password assigned to them on
the server. This creates the connection and leaves a shortcut to the share
on their desctop.

With this new information which service that you suggested would be the best
one to use?

Hi Jonathan!

You can tell if your users are connecting via SMB if they are also asked
to supply your Windows domain name. If they're only asked to provide
their names and passwords then they're connecting via AFP.

I suggest the ExtremeZ-IP option only when you have multiple Macs
connecting to your Windows server or you know you must connect via AFP.
(For example, you should use AFP when sharing files with Mac OS 9
users.) This puts the burden of administration in one location, on the
server, but it is also additional administrative overhead for your
server.

I suggest the Thursby products for when you have relatively few Macs
connecting to your Windows server. This puts the burden of the
connection on them and spares the server from the extra administrative
overhead of running additional software.

Hope this helps! bill

 

[Jon Jones]

Hi Jonathan!

You can tell if your users are connecting via SMB if they are also asked
to supply your Windows domain name. If they're only asked to provide
their names and passwords then they're connecting via AFP.

I suggest the ExtremeZ-IP option only when you have multiple Macs
connecting to your Windows server or you know you must connect via AFP.
(For example, you should use AFP when sharing files with Mac OS 9
users.) This puts the burden of administration in one location, on the
server, but it is also additional administrative overhead for your
server.

I suggest the Thursby products for when you have relatively few Macs
connecting to your Windows server. This puts the burden of the
connection on them and spares the server from the extra administrative
overhead of running additional software.

Hope this helps! bill

Good Morning Bill,

Thanks for all the help. I believe one of these will solve the problem. We
currently only have about four Macs connecting to the server. And usually
only two of those connect every day. I am going to try the Thursby products
first and see if that clears up the problem.

Do you know if I should remove the share and re-share it again, or will
putting the new protocol on Macs repair the existing share?

Thank you again,

Jonathan F. Jones

 

[William Smith]

Do you know if I should remove the share and re-share it again, or will
putting the new protocol on Macs repair the existing share?

Hi Jonathan!

Dave will take advantage of any existing Windows "share" you have.
Microsoft's best practices for shares are to share them with full
control to "Everyone" and then control their contents with permissions.
Have a look at this page on Microsoft's website for detailed steps
<http://support.microsoft.com/?scid=kb;en-us;301281&spid=1131&sid=516>

Hope this helps! bill