This post is more than 5 years old
30 Posts
0
2282
AIX 5.3 Client. Unable to connect to host
Hi ,
I have a problem when trying to add AIX client 7.6 SP5 to Networker.
Networker server: AIX 5.3
Client AIX 5.3
-----------------------------------------------------------
When I trying to add client(IP address used as a name of client) using wizard the error message shwos me "Unable to connect to host. Please check Networker Security Settings and daemon logs on nwserver and console"
----------------------------------------------------------------------------------------------
1. Checked client. Yes, it works
| root 663582 | 1 0 18:57:51 | - 0:00 /bin/nsrexecd |
2. Tried to ping client->server, server->client. Yes, it works.
3. Tried to telnet 7937 and 7938 server->client and client ->server. Yes it works.
4. Tried to nsraddadmin -u "user=root,host=IP_address"Succesfully added.
But nothing changed.
Tried to add client manually. Added but doesnt work.
--------------------------------------------------------------------
Pls show me where I was wrong.
Thank you for your time
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
July 1st, 2014 08:00
Have you added a hosts file entry for the client on the NetWorker server and vice versa ?
bingo.1
2.4K Posts
1
July 1st, 2014 09:00
On the NW server, run "nsradmin -p nsrexec -s client" and "nsradmin -p nsrexec -s client_IP"and verify the result.
nmc2
268 Posts
1
July 1st, 2014 09:00
Try clearing nsr peer information on both server and client. Also check auth method on both server and client.
Make sure auth method is nsrauth.
Refer to this link,
http://support.emc.com/kb/169175
Regards,
Prajith
Godz2
30 Posts
0
July 1st, 2014 11:00
Thank you for the answers. I will check all advices tomorrow
Godz2
30 Posts
0
July 1st, 2014 23:00
Yep, but still unlucky with a same message
Godz2
30 Posts
0
July 2nd, 2014 01:00
C:\>ping VG-ASMOSS1
Pinging VG-ASMOSS1 [10.*.6.11] with 32 bytes of data:
Reply from 10.*.6.11: bytes=32 time=1ms TTL=253
Reply from 10.*.6.11: bytes=32 time=1ms TTL=253
Ping statistics for 10.*.6.11:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
Control-C
^C
C:\>nsradmin -p nsrexec -s VG-ASMOSS1
NetWorker administration program.
Use the "help" command for help.
nsradmin>
bingo.1
2.4K Posts
1
July 2nd, 2014 01:00
So the client daemon is busy and it answers correctly on the requested port.
Now let's see whether you are on the correct machine:
C:\>nsradmin -p nsrexec -s VG-ASMOSS1
NetWorker administration program.
Use the "help" command for help.
nsradmin> . type: nsrla
nsradmin> p
Verify the hostname and IP address.
Run nsrlookup and verify whether the result is the same.
But in general, the client must not be able answer to create a client - a 'fake' in the hosts file will already do the job (very convenient when you want to recover from de-commissioned clients).
In this case you must be able to create the resource at least with 'New Client Properties'. Please try that.
However, the client must be able to answer when you want to use the Wizard - at least when you want to browse the client's file system to select the save set(s).
Godz2
30 Posts
0
July 2nd, 2014 04:00
Thank you very much for help. The problem was in /etc/hosts on a client side