macintosh, 2003 SBS share permissions

microsoft.public.win2000.macintosh - Microsoft Windows 2000


macintosh >> 2003 SBS share permissions

by Jon Jones » Fri, 10 Feb 2006 20:45:21 GMT

>> I have a client with Windows Server 2003 SBS installed. They have a
>> directory shared that is accessed by both Windows 2000, Windows XP and
>> Macintosh clients for production files.
>> The problem they are having is that they cannot change file or folder
>> names. They can create new ones and change existing data in them, but
>> they cannot rename them if they try these are the errors they get:
>>
>> Macintosh - You do not have sufficient access priveleges to rename the
>> item
>>
>> PC - Error renaming the file or folder. Cannot rename " ": access is
>> denied
>>
>> I have checked the permission and the security on the share and
>> nothing is out of whack. They should be able to rename the files and
>> folders. The last time this happened I removed the share and then
>> reshared the folder. This allowed them to rename items, but the share
>> has again stopped allowing them to rename.
>>
>> I am at a loss as to what is happening. None of the users are making
>> changes to the security or share settings, unless it is happening by
>> accident on the mac side.
>>
>> I am hoping that someone has seen this before and has a solution. Any
>> help will be greatly appreciated.



Top

macintosh >> 2003 SBS share permissions

by William Smith » Sat, 11 Feb 2006 12:12:04 GMT


In article <NS%Gf.2195$ XXXX@XXXXX.COM >,




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
--
William M. Smith
(Microsoft Interop MVP - Mac/Windows)


Top

macintosh >> 2003 SBS share permissions

by Jon Jones » Sun, 12 Feb 2006 22:25:43 GMT

"William Smith" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...


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



Top

2003 SBS share permissions

by William Smith » Mon, 13 Feb 2006 12:37:16 GMT

In article <VwHHf.6015$ XXXX@XXXXX.COM >,



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
--
William M. Smith
(Microsoft Interop MVP - Mac/Windows)

Top

2003 SBS share permissions

by Jon Jones » Mon, 13 Feb 2006 21:42:20 GMT



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



Top

2003 SBS share permissions

by William Smith » Tue, 14 Feb 2006 12:13:23 GMT

In article <c_%Hf.19006$ XXXX@XXXXX.COM >,



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
--
William M. Smith
(Microsoft Interop MVP - Mac/Windows)

Top
Similar Threads

1. Strange permission problems when accessing SBS 2003 network share 

I've got some very strange permission problems on a Vista Laptop. In fact 2 
Laptops, both with a fresh Vista install. The laptops are the only Vista 
machines in the network, and the only machines experiencing this problem.. It 
boils down to the fact that I can do some things which require 
read/write/execute permissions, while other things don't work. I really don't 
have a clue what else I can try, so hopefully someone is able to help me.

This is the environment:

- Vista Business on a Laptop, integrated in a Domain with Windows Small 
Business Server 2003
- All available updates are installed on the client and server.
- Client is logged on with a Domain User account that is in the Local 
Administrators Group.

Here are some of the things I am able to do on the network share:

- I can see all files and directories.
- I can copy a file to the network share.
- I can open text files, change and save them.
- I can open PDF files in Adobe Reader.
- I can create a new document in Word and save it.

And here are the things where I have permission problems:

- I cannot open a Word document (I also tried other Office formats). The 
error message says "Permission denied. Please contact administrator" 
(translated from German, may not be accurate)
- I cannot make a copy of a file on the network share - Permission denied.
- I cannot copy a file from a network share to another one - Permission 
denied.

Of course I have checked all the obvious things (and also some not so 
obvious ones) like:

- Share permissions are set correctly.
- NTFS permissions are set correctly.
- 3rd party virus software is removed from the laptop.
- UAC and Windows Defender are disabled.
- All accounts on the client and server have passwords.

I even tried to change the LAN Manager authentication level on the client. I 
also tried logging in with the Domain Admin account on the client, but the 
problems are the same.

Any ideas?

2. Share permissions: SBS and Windows 2003 in the same domain

3. SBS 2003 Folder Share Permissions / Rights 

I am stuck on a permission/rights problem that I just escapes me....  I 
suspect that I am just being really thick about it.  Your insight would be 
greatly appreciated.

I am trying to create a folder on my new SBS 2003 machine that all users can 
see and that contains sub folders which have different group rights.
Specifically I want a folder called "Apps" that I will have workstations map 
to as the "S" drive.  In this "Apps" folder I want sub-folders such as 
"Accounting", "Word processing", "Etc" that are each assigned different 
group rights.

I have assigned the local User group Read/Change Permissions to the Apps 
folder an it can indeed be seen by the users.  I have assigned the 
sub-folder "Accounting" full control Permission for Administrators and the 
Accounting Group and have also assigned full control Security rights for the 
same groups.  I even disabled inherited rights to the sub-folder and copied 
all settings down the tree (because I do not what all users to be able to 
even have read permissions to the contents of the sub-folder).  When I test 
the users effective permissions at the Accounting folder level it says that 
the user has full control.  However, the users does not have full control 
from the workstation.  I believe that my problem is that I am connecting to 
the share at the top folder level and so the user is only being given the 
read rights from the top level folder and everything below that folder.  It 
seems to disregard the rights assigned to the Accounting sub-folder.

Please tell me what I am missing here, or more simply, what is the correct 
way to do this.

I have also observe that the Permission settings and the Security rights are 
not consistent when viewed in Windows Explorer vs. when viewed in the Server 
Manager.  Should I be working exclusively in Server Manager?  I have updated 
the Permissions and Security via both methods to no avail.

Many thanks.

4. Share permissions: SBS and WIndows 2003 R2 in the same domain - Windows Small Business Server(SBS)

5. Shared Printer Permission Problem in SBS 2003 

I'm sharing an HP 1200 Network Inkjet printer on a clean installation of 
Small Business Server 2003.

I've performed a standard install of the drivers provided with the printer 
and I can print from any machine as long as the user has Administrative 
rights. 

Any other user fails to print and there's a "3003: A startPrinterDoc command 
was not issued." in the logs.

I'm hoping it's a simple permission problem but I can't see what to change 
to allow all users to print. The rpinter itself looks to be available to 
"everyone" to print on and the printer$ seems not to be the problem either.

HP don't want to know - Any Ideas????

6. SBS 2003 Incoming Fax Shared Folder Permissions - Windows Small Business Server(SBS)

7. SBS 2003 - tidying up share permissions 

I've been asked to tidy up the share permissions on an SBS 2003 server which 
has been set up by various user administrators along the way. All users have 
a shared folder mounted as a network drive on their desktops. They have 
access to all the folders and sub-folders in this share, but the permissions 
have been granted in an ad-hoc way, some via groups, some by giving 
individual permissions, and some by straight-forward inheritance. What I'd 
like to do is set up the permissions via a single group (e.g. office) which 
can be applied to the shared folder,  add all permitted users to this group 
and then remove all the previous groups and shares (excepting critical admin 
and domain rights) I'd prefer not to work through every folder by hand to 
remove the old permissions and to inherit the new permissions - is there a 
simpler way of doing this?

After I've done that, I want to exclude two folders in this share from the 
user group I added above, and then just allow a specific group to access each 
folder (e.g. only finance group have access to the finance folder and only HR 
groups have access to the personnel folder.  Users in the finance and HR 
groups will also be in the office group. Am I correct to turn off inheritance 
in the finance and HR folders and then just add the appropriate group to the 
folder permissions or do I need to add group to the share permissions too?

Thanks

Brian
Warwickshire (Shakespear's County)
UK

8. Office 2008 permissions failure to a 2003 server share