Share Permission Issue on Windows Server 2003 Appliance Edt, How can I fix the access to the \\computername\ADMIN$ share?

I hade same thing... this is client side problem, run “sfc /scannow” may be able to solve the problem.

My understanding is that edition is meant to be a NAS. It might not have a admin$ share, have you verified it exists by looking at the shares?

You could attempt to create (recreate) the admin$ share: http://support.microsoft.com/kb/816113

I will attempt to recreate it, i definitely verified that the shares exists and the path is there as well which leads to c:\Windows. I'll recreate and post results.

hey guys, the recreation of the share did not work, i'm still getting the same message, this is everything i have verified so far:


* Check DNS settings
Incorrect DNS settings are the most common cause of this problem. Use the ping -a command to confirm name resolution and to confirm the accuracy of the DNS suffix.

* Check environmental variables
Confirm that the correct shares are set up on the target computer.

To confirm and set up shares
At a command prompt, type the following command:

net share

If you do not see the ADMIN$ and <OS Drive>$ shares, create them.
To create the shares, type the following commands:

net share ADMIN$
net share C$=C:\

* Check Distributed COM properties
Incorrect Distributed COM properties can cause this problem.

To confirm Distributed COM properties
On the Windows taskbar, click Start > Run.
In the Open box, type the following text:

dcomcnfg

Click OK.

Do one of the following, depending on your version of Windows:

In Windows XP/2003, click Component Services > Computers > My Computer. Then right-click My Computer and click Properties.
In all other versions of Windows, go on to the next step.
On the Default Security or Default COM Security tab, under Default Access Permissions, click Edit Default.
The resultant window is normally blank. If it is not blank, then confirm that Administrators, Interactive, and System accounts are set to Allow Access, and then click OK.
Under Default Launch Permissions, click Edit Default.
Confirm that the Administrators, Interactive, and System accounts are set to Allow Launch, and click OK.
Do one of the following, depending on your version of Windows:
In Windows XP/2003, skip the two following steps.
In all other versions of Windows, go on to the next step.
In the Default Configuration Permissions section, click Edit Default.
In the Registry Key Permissions window, confirm that the following are set to Full Control, and then click OK:

CREATOR OWNER
...\Administrators
SYSTEM

Can you check the following registry key on the target machines:

Hive: HKEY_LOCAL_MACHINE Key: SYSTEM\CurrentControlSet\Services\LanManServer\Parameters Name: AutoShareWks Data

if it is a server OS

Hive: HKEY_LOCAL_MACHINE Key: SYSTEM\CurrentControlSet\Services\LanManServer\Parameters Name: AutoShareServer Data

The value should be 1 - if not change it - and reboot

joerghermanns:


I navigated to that location on the server via regedit and I do not have an AutoShareServer Data entry. Laso, the LanManServer folder is in all lower case, does it matter?

sorry about the typo up top I meant to type Also, not Laso.

Strange ... what entries do you have under "Lanmanserver\Parameters" ?

just to make sure: the problem occurs on the clients, right?
so you will have to lookup the entry on the clients!
also check if any type of client firewall ist active!

No only on the server, the problem is the AV application accessing the ADMIN$ share or c:\windows directory. i will check the parameters and post asap.

currently i have on the server:

adjustednullsessionpipes
autodisconnect
disabledownleveltimewarp
enableforcedlogoff
enablesecuritysignature
guid
irpstacksize
lmannounce
nullsessionpipes
nullsessionshares
requiresecuritysignatures
restrictnullsessaccess
servicedll
size

these are the only one in there, the one mentioned ealier is not in that folder.

This qiestion is being closed, the problem resided in the version of OS i was using on the NAS server. the NAS server is not meant to be used for aplications but as a storage device. thank you all for your help.

agreed, i did not look at previous post by you. thank you, you are absolutely correct about that version