Re: Problem accessing user machine.

Hello Scott,

Thank you for your update.

By default, the local administrators members will have full control NTFS
permission on the local folders. However, we need to check the Shared
permission too. Only when you have both NTFS write permission and shared
write permission, you can write to the shared folder.

Another, if you do use the connectcomputer wizard to join client computer
to domain, the domain admins will add to client computer local
administrators group. This will make things easy.

Anyhow, I'm glad to hear that things are working correctly for you now.

I'd like to make a summary for this post:

Issue:
=============
unable to write to the shared folder on one client computer

Cause:
=============
Write permission is not properly set on the shared folder

Resolutions:
=============
a. On the problematic client computer, right click the shared folder,
select properties
b. Select Sharing tab, click Permissions button
c. Click Add button to add your domain account in the list, then, give it
'Change' permissions. Click OK
d. Select Security tab
e. Click Add button to add your domain account in the list, then, give it
'Modify' permissions. Click OK

Please do not hesitate to post in SBS newsgroup if you need any assistance
in the future. I look forward to working with you again.

Thank you and have a nice day,

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| From: "Not Really Me" <scott@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <eqwdxUwVIHA.4684@xxxxxxxxxxxxxxxxxxxx>
<eSuqDLzVIHA.5596@xxxxxxxxxxxxxxxxxxxx>
<#JSBbBJWIHA.4684@xxxxxxxxxxxxxxxxxxxx>
<dMfcFxOWIHA.5204@xxxxxxxxxxxxxxxxxxxxxx>
| Subject: Re: Problem accessing user machine.
| Date: Fri, 18 Jan 2008 08:01:47 -0700
| Lines: 193
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
| Message-ID: <ujZd8MeWIHA.4548@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: 71.216.221.2
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:87443
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Terence, Your first suggestion worked fine when I added my personal
domain
| account to the c-drive share properties and security. I still find it
| confusing that I needed to do so on that machine, but not on any other.
I
| thought being a member of administrators, engineering (a group we
created)
| and at least one other group would have worked. All of these other
groups
| had "full control" permissions to the share.
|
| It's fixed now though, thanks for your help.
|
| Scott
|
| "Terence Liu [MSFT]" <v-terliu@xxxxxxxxxxxxxxxxxxxx> wrote in message
| news:dMfcFxOWIHA.5204@xxxxxxxxxxxxxxxxxxxxxxxxx
| > Hello Scott,
| >
| > Thank you for posting here. Let's also thank Cris for the input.
| >
| > According to your description, I understand that you unable to write to
| > the
| > shared folder on one client computer. If I have misunderstood the
problem,
| > please don't hesitate to let me know.
| >
| > Based on my research, I suggest we try the following steps to see if we
| > can
| > resolve this issue:
| >
| > 1. Please ensure your domain account has shared permission and NTFS
| > permission of the shared folder:
| >
| > a. On the problematic client computer, right click the shared folder,
| > select properties
| > b. Select Sharing tab, click Permissions button
| > c. Click Add button to add your domain account in the list, then, give
it
| > 'Change' permissions. Click OK
| > d. Select Security tab
| > e. Click Add button to add your domain account in the list, then, give
it
| > 'Modify' permissions. Click OK
| >
| > Then, logon another computer with your domain account, access the shared
| > folder, and try to write to the folder.
| >
| > 2. If the above steps unable to resolve this issue, I suggest you rejoin
| > the problematic client to SBS domain:
| >
| > a. Disjoin domain: Right click My Computer->Properties->Computer Name
| > tab->Change button->Select Workgroup->click OK twice and reboot it.
| > b. Create user account and computer account thru the Add User Wizard:
| > SBS->Server Management console->Users->Add a User
| > c. Rejoin domain thru connectcomputer wizard on client: On the client,
| > access http://SBSname/connectcomputer/. Finish the wizard and reboot it.
| >
| > Then, logon SBS with domain administrator account and access the shared
| > folder on the client.
| >
| > 3. If the issue persists, I suggest we do clean boot on the problematic
| > client to narrow down this issue:
| >
| > To clean boot the problematic computer, please use the steps below:
| > a. Click Start, click Run, and then in the Open box, type "MSCONFIG"
| > (without the quotation marks). Click OK.
| >
| > b. In the System Configuration Utility (MSConfig) window, click to
select
| > the Selective Startup button.
| >
| > c. Click to clear the check mark from the "Load startup items" below
| > Selective Startup.
| >
| > d. Click the Services tab, click to check the "Hide All Microsoft
| > Services"
| > box, and remove all the check marks from the remained Non-Microsoft
| > Services.
| >
| > e. Click OK to close the MSConfig window. Click Yes when you are asked
to
| > restart your computer in order to enable the changes.
| >
| > f. After restarting, please check whether this issue will reoccur.
| >
| > If we cannot resolve the issue after we perform the above steps, please
| > help me collect some information for further investigation:
| >
| > 1. Can you write to other shared folder on this problematic client?
| >
| > 2. Can you write to other client computer's shared folder?
| >
| > 3. What error do you get when you try to write to the shared folder?
| > Please
| > capture screenshots on the error messages and send the pictures to me at
| > v-terliu@xxxxxxxxxxxxx
| >
| > 4. What's edition of your SBS? The problematic client is XP or Vista?
| >
| > I hope these steps will give you some help.
| >
| > Thanks and have a nice day!
| >
| > Best regards,
| >
| > Terence Liu(MSFT)
| >
| > Microsoft CSS Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| >
| > =====================================================
| > This newsgroup only focuses on SBS technical issues. If you have issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
| > the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
| > doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > =====================================================
| >
| > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| >
| > --------------------
| > | From: "Not Really Me" <scott@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
| > | References: <eqwdxUwVIHA.4684@xxxxxxxxxxxxxxxxxxxx>
| > <eSuqDLzVIHA.5596@xxxxxxxxxxxxxxxxxxxx>
| > | Subject: Re: Problem accessing user machine.
| > | Date: Wed, 16 Jan 2008 15:37:19 -0700
| > | Lines: 133
| > | MIME-Version: 1.0
| > | Content-Type: multipart/alternative;
| > | boundary="----=_NextPart_000_000A_01C85855.ADC89F90"
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
| > | Message-ID: <#JSBbBJWIHA.4684@xxxxxxxxxxxxxxxxxxxx>
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | NNTP-Posting-Host: 71.216.221.2
| > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:87073
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | The c-drive is shared and I have permissions as administrator and at
| > least 2 other groups in the share.
| > | This is a small domain and we use the write to pass files around.
Tend
| > to be files that aren't under source control (yet). Probably in
violation
| > of SBS good practices, we do not keep all of the users data on the
server.
| > We tend to keep most things local to the ws.
| > | FWIW, this machine was orginally in a stand alone workgroup. It was
| > added to the domain and the workgroup isn't used any more. The machine
| > has
| > access to other resources and when logged in as myself, I can pass files
| > back to my main ws, but haven't been able to write to the c-drive.
| > | Scott
| > | "Cris Hanna [SBS-MVP]" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxx>
wrote
| > in
| > message news:eSuqDLzVIHA.5596@xxxxxxxxxxxxxxxxxxxxxxx
| > | Is the C drive shared? Does your user account in the domain have
| > permissions to that Share?
| > | Can't imagine why you'd need to write anything to a workstation
drive
| > remotely anyway, but...
| > | --
| > | Cris Hanna [SBS - MVP]
| > | -----------------------------------------------------------
| > | MVPs Do Not Work for Microsoft
| > | Please do not contact me directly regarding issues
| > | "Not Really Me" <scott@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
| > message news:eqwdxUwVIHA.4684@xxxxxxxxxxxxxxxxxxxxxxx
| > | <Head hung in shame> I think I used the wizard to add a new
machine
| > to the
| > | domain. Was a couple months ago.
| > | Now as the admin I can not write to the drive on that machine
from
| > my
| > own
| > | machine. Read fine, but no write privilages.
| > | I've tried everything I know of, but no luck.
| > | Any suggestions?
| > | Scott
| > |
| >
|
|
|

.