Unable to connect to the NETLOGON share

http://support.microsoft.com/kb/887303

I think you should read this link over. I believe it's related and contains a few possible resolutions. If not DNS it's probably related to SMB signing.

Sounds like you have some hosed SRV records in DNS:

Here is how to verify your SRV records.
http://support.microsoft.com/?kbid=241515

When the netlogon service is restarted it will register the SRV records in DNS. However, if you have a Multihomed domain controller, there is a quirk in a 2003 server service pack that will register the SRV records of both NICs regardless of the option to prevent one NIC from registering the SRV records. If both NICs have SRV records in DNS, the server can confuse the logon/authentication process.

To prevent this from happening, there is a patch to this as well.
 -- http://support.microsoft.com/?id=832478

Plausible solutions to your problem:
What you might have to do is:
1) apply the 2003 server hotfix that prevents both NICs from registering SRV records regardless of the option to disable the registration
2) disable one nic from registering the SRV records
3) remove the SRV records that don't belong

_____________________________________________________

For further troubleshooting, can you answer a couple questions:

How many DC's do you have and what are their OS?
Can you provide a DCdiag report?

I tried these methods but without any result. Here I am presenting the results the dcdiag on the server.

additional information, is that this server was prepared in a location other than where you are today. now was moved from location where is visisbles are  all servers.

omain Controller Diagnosis
 
Performing initial setup:
   Done gathering initial info.
 
Doing initial required tests
 
   Testing server: Default-First-Site-Name\W2KAAS1
      Starting test: Connectivity
         ......................... W2KAAS1 passed test Connectivity
 
Doing primary tests
 
   Testing server: Default-First-Site-Name\W2KAAS1
      Starting test: Replications
         ......................... W2KAAS1 passed test Replications
      Starting test: NCSecDesc
         ......................... W2KAAS1 passed test NCSecDesc
      Starting test: NetLogons
         Unable to connect to the NETLOGON share! (\\W2KAAS1\netlogon)
         [W2KAAS1] An net use or LsaPolicy operation failed with error 1203, No
network provider accepted the given network path..
         ......................... W2KAAS1 failed test NetLogons
      Starting test: Advertising
         ......................... W2KAAS1 passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... W2KAAS1 passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... W2KAAS1 passed test RidManager
      Starting test: MachineAccount
         ......................... W2KAAS1 passed test MachineAccount
      Starting test: Services
         ......................... W2KAAS1 passed test Services
      Starting test: ObjectsReplicated
         ......................... W2KAAS1 passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... W2KAAS1 passed test frssysvol
      Starting test: frsevent
         ......................... W2KAAS1 passed test frsevent
      Starting test: kccevent
         ......................... W2KAAS1 passed test kccevent
      Starting test: systemlog
         An Error Event occured.  EventID: 0x0000164A
            Time Generated: 05/10/2008   09:51:20
            Event String: The Netlogon service could not create server
         ......................... W2KAAS1 failed test systemlog
      Starting test: VerifyReferences
         ......................... W2KAAS1 passed test VerifyReferences
 
   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation
 
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
 
   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation
 
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
 
   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
 
   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
 
   Running partition tests on : AACXA
      Starting test: CrossRefValidation
         ......................... AACXA passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... AACXA passed test CheckSDRefDom
 
   Running enterprise tests on : AACXA.LOCAL
      Starting test: Intersite
         ......................... AACXA.LOCAL passed test Intersite
      Starting test: FsmoCheck
         ......................... AACXA.LOCAL passed test FsmoCheck

Select allOpen in new window

Now that you have prevented your multihomed NIC from registering its SRV records, your ready for the second stage to this fix. Follow the fix to this post and you should have your issues resolved.

You just brought up a new server and need to straighten out DNS in order to communicate with it. This includes communicating with itself.

https://www.experts-exchange.com/questions/23356031/There-are-currently-no-logon-servers-available-to-service-the-logon-request.html

NOTE: Don't forget to force replicate FROM your PDCe TO this server. How to is found in the discussion following the solution provided.

PDCe = PDC emulator.


IN YOUR CASE:
Not being able to connect to a netlogon share means your Host A record can't resolve to the server.

It can also mean the netlogon share is in a subdirectory of itself.

Example:

%system32%netlogon\netlogon

I have seen both.

If this doesn't resolve the problem, I would go to the command prompt and Ping the server by name to see what IP it is trying to resolve. If no reply, DNS is still not resolving the server.

and I realize these procedures but without results. that is exactly what I do with this root:

%system32%netlogon\netlogon

the dns resolve  and ping the server.

thank everyone , I review the event in the EventViewer, and the server was trying to find a policy folder sysvol not existed,I to re-create the folder which tried to find and immediately stop receiving this error.