Cannot access remote shares

  • Thread starter Thread starter H
  • Start date Start date
H

H

Hi,

We have a problem where users in our head office are unable to access the
fileshares of servers located in remote offices. When you try to browse to
the share you get the error "No network provider accepted the given path".
Users in the remote offices CAN access fileshares in the head office.

Running netdiag on a DC in the remote office I get the following errors.....

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.

WINS service test. . . . . : Failed
The test failed. We were unable to query the WINS servers.

NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Service', <03> 'Messenger Service', <20> 'WINS' names defined.

Trust relationship test. . . . . . : Failed
[FATAL] Secure channel to domain 'MYDOMAIN' is broken.
[ERROR_NO_LOGON_SERVERS]

Looking at the event log on the remote office DC I also notice error 5719 in
the event log - source NETLOGON

This computer was not able to set up a secure session with a domain
controller in domain MYDOMAIN due to the following:

There are currently no logon servers available to service the logon request.

This may lead to authentication problems. Make sure that this computer is
connected to the network. If the problem persists, please contact your
domain administrator.


I don't really know how to troubleshoot this any further - any help is very
welcome! I plan to reset the secure channel using netdom tonight (it
requires a server reboot).

-H
 
I have had the exact problem with one of my remote offices. The remote office is in a child domain of the main office and the same error occurs when trying to access shares. I was never able to resolve this issue but a workaround that worked for me was to create a DFS in the domain at the main office and plug the remote share into it. This seems to work very well.

Bradley Fox
Sr. Network Administrator
 
OK thanks for the tip. I may log a call with MS tech support tomorrow, so if I get a resolution from them I will let you know.
I have had the exact problem with one of my remote offices. The remote office is in a child domain of the main office and the same error occurs when trying to access shares. I was never able to resolve this issue but a workaround that worked for me was to create a DFS in the domain at the main office and plug the remote share into it. This seems to work very well.

Bradley Fox
Sr. Network Administrator
 
Back
Top