cancel
Showing results for 
Search instead for 
Did you mean: 

Need to change ip ipdress in client

madhuri
Level 4
 
Hi Folks In my enviornment we are failling with 58 cannot connect to client
I have ping from nb console cannot load host properites
 
When am pinging client it was pinging,showing different ip adress and differnt client name can u see the 
 
 
C:\Documents and Settings\knarra>ping xxxx
 

Pinging XXXXXXX [11111111] with     Here we are getting different name with ip adress

 
Reply from XXXXX: bytes=32 time=37ms TTL=118
Reply from XXXXX: bytes=32 time=37ms TTL=118
Reply from XXXXX: bytes=32 time=37ms TTL=118
Reply from XXXXX: bytes=32 time=37ms TTL=118
 
Ping statistics for 135.11.66.121:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% lo
Approximate round trip times in milli-seconds:
    Minimum = 37ms, Maximum = 37ms, Average = 37ms
 
So i have searched  in my ticketing tool  i got the correct ip adress and i have ping with ip adress it was showing correct name 
 
When i was ping with ip adress below convesation
 

C:\Documents and Settings\knarra>ping -a 222222 here am trying to ping with original ip adress  getting same name 

 
Pinging YYYYY[00000] with 32 bytes of data:
 
Reply from ZZZZZZ: bytes=32 time<1ms TTL=124
Reply from ZZZZZZ: bytes=32 time<1ms TTL=124
Reply from ZZZZZZ: bytes=32 time<1ms TTL=124
 
 
I need the solution how can we trouble shoot this issue 
 
1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

When ping gives you incorrect IP address, you need to check OS-level config.

You first of all need to determine if hostname lookup on NBU master and media servers is via hosts files or DNS.

If hosts files, you need to update it in all hosts files where this client is specified (master and media server(s).

If DNS, you need to check that DNS is indeed updated and that DNS cache has been flushed. Use nslookup to test forward and reverse lookup.

Once all of the above has been checked and confirmed, you need to flush NBU host cache with:
bpclntcmd -clear_host_cache 
on master and all media servers.

See:

When and how to clear the NetBackup host cache 
 http://www.symantec.com/docs/TECH136792 

 

PS: In future, please tell us what OS on the NBU master. 
I doubt that it is Windows 7....

 

**** EDIT **** 

Is this issue related to yesterday's post? 
https://www-secure.symantec.com/connect/forums/cannot-connect-client 

Please provide feedback to that post as well?
 

View solution in original post

2 REPLIES 2

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

so you have name resolution Problem

1) confirm the what is the correct IP of the server by checking on the client network interface

2) are you using DNS or hosts file for name resolutions?

if DNS,

make sure DNS is resolving the correct name and IP, if not update the DNS entires.. ( DNS admin/OS admin task)

nslookup <clientname>

nslookup <client IP>

make sure both are giving the correct names..

if you are etc/hosts

update the etc/hosts file with correct IP address and client name

then test the ping communication.

if it looks fine

do bpclntcmd -clear_host_cache and then try for backup.

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

When ping gives you incorrect IP address, you need to check OS-level config.

You first of all need to determine if hostname lookup on NBU master and media servers is via hosts files or DNS.

If hosts files, you need to update it in all hosts files where this client is specified (master and media server(s).

If DNS, you need to check that DNS is indeed updated and that DNS cache has been flushed. Use nslookup to test forward and reverse lookup.

Once all of the above has been checked and confirmed, you need to flush NBU host cache with:
bpclntcmd -clear_host_cache 
on master and all media servers.

See:

When and how to clear the NetBackup host cache 
 http://www.symantec.com/docs/TECH136792 

 

PS: In future, please tell us what OS on the NBU master. 
I doubt that it is Windows 7....

 

**** EDIT **** 

Is this issue related to yesterday's post? 
https://www-secure.symantec.com/connect/forums/cannot-connect-client 

Please provide feedback to that post as well?