Quantcast
Channel: Symantec Connect - Backup and Recovery
Viewing all articles
Browse latest Browse all 6339

Job Setup To NAS net share is grayed out.

$
0
0
I need a solution

BE 12.5,  I am no longer able to select the net share, it is grayed out, this process was working without issue a month ago, no changes to the config on BE Server and NAS.

I am also not able to connect to a user defnied share by IP number. The same NAS device (DX1) is used as the backup to disk folder, and this works.

  • The "Enable selections of User Shares" has always been enabled.
  • Windows Firewall is disabled on the BE Server.
  • Beremote.exe, white listed in AntiVirus.
  • User and Pass are working, Domain Admin level.

Here is the log file:

BEREMOTE: [12/08/14 14:34:11] [2760]     [no resource for 3893]
BEREMOTE: [12/08/14 14:34:13] [5676]     FS_ResolveDevName: [\\NAS]
BEREMOTE: [12/08/14 14:34:13] [5676]     MB2-Resolve returned 1
BEREMOTE: [12/08/14 14:34:13] [5676]     Notes Agent:CLNFileSystem::ResolveDeviceName
BEREMOTE: [12/08/14 14:34:13] [5676]     ADC_ResolveDeviceName: pid = 3868, checking \\NAS
BEREMOTE: [12/08/14 14:34:13] [5676]     Inside evFileSystem::EV_ResolveDeviceName
BEREMOTE: [12/08/14 14:34:13] [5676]     Inside evFileSystem::IsGoodEVName
BEREMOTE: [12/08/14 14:34:13] [5676]     evFileSystem::IsGoodEVName: GoodEvName failed for (\\NAS)
BEREMOTE: [12/08/14 14:34:13] [5676]     evFileSystem::EV_ResolveDeviceName: IsGoodEVName failed for (\\NAS)
BEREMOTE: [12/08/14 14:34:13] [5676]       VRTSRV:DeviceName \\NAS1
BEREMOTE: [12/08/14 14:34:13] [5676]     RPCDsSession::GetLoginCredentials: Connecting to BEM API as user: DOMAIN\administrator
BESERVER: [12/08/14 14:34:13] [2988]     -1 Client requested key (1418078216).
BESERVER: [12/08/14 14:34:13] [2988]     "Cluster" key does not appear to be present in the registry
BESERVER: [12/08/14 14:34:13] [2988]     Failed to open Microsoft cluster ()
BESERVER: [12/08/14 14:34:13] [2988]     VCS cluster keys do not appear to be present in the registry
BESERVER: [12/08/14 14:34:13] [2988]     Failed to open VCS cluster ()
BESERVER: [12/08/14 14:34:13] [2988]     01 Server Configuration: Client added: 8
BESERVER: [12/08/14 14:34:13] [2988]     -1 Client 'BESERVER' connected('','DOMAIN\administrator'): 0x43d0670
BESERVER: [12/08/14 14:34:13] [2988]     01 Server Configuration: Client removed: 7
BESERVER: [12/08/14 14:34:13] [2988]     -1 Client 'BESERVER' Disconnected:0x43d0670
BEREMOTE: [12/08/14 14:34:13] [5676]     Could not resolve the "bews-ndmp" or the "ndmp" service, error code: 10109, using port 10000
BEREMOTE: [12/08/14 14:34:13] [5676]     ndmpConnectEx: Querying the neighbour advertisement cache to discover information on 'NAS' ...
BENETNS:  [12/08/14 14:34:13] [2000]     NRDS API - client connected.
BENETNS:  [12/08/14 14:34:13] [2000]     NRDS API - client disconnected.
BEREMOTE: [12/08/14 14:34:14] [5676]     @@@@@@@MyCloseSocket called with sockfd = 1912(0x778)    retval = 0
BEREMOTE: [12/08/14 14:34:14] [5676]     ndmpEstablishConnectionUsingNoSpecificAdapter: Could not connect to remote address 172.16.X.XX and port 10000 Errorno : 10061
BEREMOTE: [12/08/14 14:34:14] [5676]     ndmpConnectEx: unable to connect using NetworkOptions to NAS
BEREMOTE: [12/08/14 14:34:14] [5676]     BETCPConnection::CreateConnectionFromHostAndPort: Remote Host: "NAS": There were no addresses returned, belonging to family: IPv6.
BEREMOTE: [12/08/14 14:34:15] [5676]     BETCPConnection::LoopThroughListAndConnect: Could not connect to remote address "172.16.X.XX" Error:10061.
BEREMOTE: [12/08/14 14:34:15] [5676]     @@@@@@@MyCloseSocket called with sockfd = 1912(0x778)    retval = 0
BEREMOTE: [12/08/14 14:34:15] [5676]     BETCPConnection::CreateConectionFromHostAndPort: Could not create a connection to "NAS" because attempts with both IPv4 and IPv6 protocols failed
BEREMOTE: [12/08/14 14:34:15] [5676]     ndmpConnectEx: All attempts to connect to 'NAS' failed
BEREMOTE: [12/08/14 14:34:15] [5676]     ndmpConnectEx: failed to connect to 'NAS'
BEREMOTE: [12/08/14 14:34:16] [2760]     Failed to open Microsoft cluster (NAS)
BEREMOTE: [12/08/14 14:34:16] [2760]     Failed to open VCS cluster (NAS)
BEREMOTE: [12/08/14 14:34:18] [2760]     Failed to open Microsoft cluster (NAS)
BEREMOTE: [12/08/14 14:34:18] [2760]     Failed to open VCS cluster (NAS)
BEREMOTE: [12/08/14 14:34:18] [2760]     Error 1722 opening cluster on \\NAS
BEREMOTE: [12/08/14 14:34:18] [2760]     Error 0 on NetShareEnum of \\NAS, level 1, entries 2, total 2
BEREMOTE: [12/08/14 14:34:19] [2760]     Failed to open Microsoft cluster (NAS)
BEREMOTE: [12/08/14 14:34:19] [2760]     Failed to open VCS cluster (NAS)
BEREMOTE: [12/08/14 14:34:19] [2760]     "Cluster" key does not appear to be present in the registry
BEREMOTE: [12/08/14 14:34:19] [2760]     Failed to open Microsoft cluster ()
BEREMOTE: [12/08/14 14:34:19] [2760]     VCS cluster keys do not appear to be present in the registry
BEREMOTE: [12/08/14 14:34:19] [2760]     Failed to open VCS cluster ()
BEREMOTE: [12/08/14 14:34:19] [2760]     analyze user share -->SHARE1<--
BEREMOTE: [12/08/14 14:34:19] [2760]     adding share -->\\NAS\SHARE1<-- to the DLE list
BEREMOTE: [12/08/14 14:34:20] [2760]     Failed to open Microsoft cluster (NAS)
BEREMOTE: [12/08/14 14:34:20] [2760]     Failed to open VCS cluster (NAS)
BEREMOTE: [12/08/14 14:34:21] [2760]     Failed to open Microsoft cluster (NAS)
BEREMOTE: [12/08/14 14:34:21] [2760]     Failed to open VCS cluster (NAS)
BEREMOTE: [12/08/14 14:34:21] [2760]     [no resource for 3893]

*****I have Backup Exex 12.0 Server that connects to the same exact NAS above without issue.

Any intel on this, will be greatly appreciated.


Viewing all articles
Browse latest Browse all 6339

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>