Solved

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

Posted on 2010-08-27
14
712 Views
Last Modified: 2013-12-04
good day everyone,

i have a DELL power vault 745n that has windows server 2003 appliance edition installed on it. i made this server an app server, one of the application i installed is BitDefender SBS Edition. When i go to deploy the agent to workstations i get a message that is similar to the pic attached. to that end when i test the access permissions on the server i am met with the "No Network provider accepted the given network path" message.

I'm gathering my AV issue is due to some policy or permission issue on this box, hopefully someone has seen this before and can help point me in the right direction to solving this matter. any help on this would be deeply appreciated. thank you all. (see attached screenshot) Screenshot of admin$ share message
0
Comment
Question by:GridLock137
  • 8
  • 3
  • 2
  • +1
14 Comments
 
LVL 5

Expert Comment

by:vaska94
ID: 33545487
I hade same thing... this is client side problem, run “sfc /scannow” may be able to solve the problem.
0
 
LVL 9

Expert Comment

by:BDoellefeld
ID: 33545515
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
0
 
LVL 7

Author Comment

by:GridLock137
ID: 33545787
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.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 7

Author Comment

by:GridLock137
ID: 33545983
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
0
 
LVL 3

Expert Comment

by:joerghermanns
ID: 33548704
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
0
 
LVL 7

Author Comment

by:GridLock137
ID: 33549527
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?
0
 
LVL 7

Author Comment

by:GridLock137
ID: 33549535
sorry about the typo up top I meant to type Also, not Laso.
0
 
LVL 3

Expert Comment

by:joerghermanns
ID: 33550021
Strange ... what entries do you have under "Lanmanserver\Parameters" ?
0
 
LVL 3

Expert Comment

by:joerghermanns
ID: 33550027
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!
0
 
LVL 7

Author Comment

by:GridLock137
ID: 33550179
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.
0
 
LVL 7

Author Comment

by:GridLock137
ID: 33550216
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.
0
 
LVL 7

Author Comment

by:GridLock137
ID: 33581595
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.
0
 
LVL 9

Accepted Solution

by:
BDoellefeld earned 500 total points
ID: 33581913
Hello, my reply to this question matches the final conclusion.

That this edition was intended to be used as a NAS, but that you could attempt a unsupported method to get the result.
0
 
LVL 7

Author Closing Comment

by:GridLock137
ID: 33582834
agreed, i did not look at previous post by you. thank you, you are absolutely correct about that version
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Thin secure Windows 10 5 93
Backup DHCP Server 8 104
User profile Size Report 3 72
DHCP server 6 61
Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
The term "Bad USB" is a buzz word that is usually used when talking about attacks on computer systems that involve USB devices. In this article, I will show what possibilities modern windows systems (win8.x and win10) offer to fight these attacks wi…
Internet Business Fax to Email Made Easy - With eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, fr…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

805 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question