Video Screencast Help

NrdsAdvertiserThread: connect to target=BACKUP-SRV port=6101 failed

Created: 29 Jun 2011 • Updated: 23 Nov 2012 | 6 comments
Masood Asif's picture
This issue has been solved. See solution.

HI,

 

step Breif:

i have windows 2003 server running symantec backup exec 2010 R3 

i have 2 linux machines running REHL 5.5 64 bit 

i installed the ralus on booth of the machine 

now after the installtion i can see one RHEL machine in my linux/UNIX clients but second machine is not comming on there however the beremote is running 

i tried to start the the beremote on the 2nd node which is not connecting to my Backserevr it is giving following error

 

42ec6940 Wed Jun 29 16:15:38 2011 : NrdsAdvertiserThread: connect to target=192.168.120.90 port=6101 failed
42ec6940 Wed Jun 29 16:15:38 2011 : NrdsAdvertiserThread: Security is enabled!!!
42ec6940 Wed Jun 29 16:15:38 2011 : This instance of BETCPListener was not requested to install a signal handler and hence will not install one!
42ec6940 Wed Jun 29 16:15:38 2011 : BENetConfigEx: Successfully refreshed adapter information.
42ec6940 Wed Jun 29 16:15:38 2011 : NrdsAdvertiserThread: connect to target=BACKUP-SRV port=6101 failed
42ec6940 Wed Jun 29 16:15:38 2011 : NrdsAdvertiserThread: Retrying in 60 seconds
42ec6940 Wed Jun 29 16:16:38 2011 : NrdsAdvertiserThread: Security is enabled!!!
42ec6940 Wed Jun 29 16:16:38 2011 : This instance of BETCPListener was not requested to install a signal handler and hence will not install one!
42ec6940 Wed Jun 29 16:16:38 2011 : BENetConfigEx: Successfully refreshed adapter information.
42ec6940 Wed Jun 29 16:16:38 2011 : NrdsAdvertiserThread: connect to target=192.168.120.90 port=6101 failed
42ec6940 Wed Jun 29 16:16:38 2011 : NrdsAdvertiserThread: Security is enabled!!!
42ec6940 Wed Jun 29 16:16:38 2011 : This instance of BETCPListener was not requested to install a signal handler and hence will not install one!
42ec6940 Wed Jun 29 16:16:38 2011 : BENetConfigEx: Successfully refreshed adapter information.
42ec6940 Wed Jun 29 16:16:38 2011 : NrdsAdvertiserThread: connect to target=BACKUP-SRV port=6101 failed
42ec6940 Wed Jun 29 16:16:38 2011 : NrdsAdvertiserThread: Retrying in 60 seconds
 
 
a quick response is highly appreciable 
regards
Masood Asif

Comments 6 CommentsJump to latest comment

AmolZeroCool's picture

Is IPV6 disabled on the remote server?

Amol

MCITP | STS | SCP 
______________________________________________________________
If this response answers your query, do mark it as a solution
Joseph Marton's picture

I tried the hotfix in my environment which is experiencing the same error but it had no effect.

My environment: Windows 2003 running BE 2010 R3 SP1, Linux is Novell OES2 SP3 running on SLES 10 SP3 x86_64.

Even though I was already on SP1 on the main BE server side, it appears from article 161270 that the contents of that hotfix aren't in SP1.  I applied the hotfix to both BE & RALUS.  No effect.  I then saw there was an SP1 patch for RALUS sitting on the BE server, so I pushed that to the Linux box and applied the patch.  Still the same error.

41802940 Sun Sep 25 18:04:35 2011 : NrdsAdvertiserThread: Security is enabled!!!
41802940 Sun Sep 25 18:04:35 2011 : This instance of BETCPListener was not requested to install a signal handler and hence will not install one!
41802940 Sun Sep 25 18:04:35 2011 : BENetConfigEx: Successfully refreshed adapter information.
41802940 Sun Sep 25 18:04:35 2011 : NrdsAdvertiserThread: connect to target=[server] port=6101 failed
 
In ralus.cfg I've tried specifying multiple names for the media server
 
server
server.domain
IP
 
Nothing seems to help.  The server itself is definitely listening on por 6101 so it appears to be some sort of handshake problem which is documented in various Symantec KB articles.  All point back to 161270 which isn't doing anything for me.
 
Joe
Muhammad Nazakat's picture

Try reinstalled rules on both of the machine.

Regards,

Muhammad.

Joseph Marton's picture

I'm not sure what that means, but I finally found a solution.  I still had an older version of the BE 2010 RALUS (build 2896.9), so I installed it.  That worked.  I didn't see any errors manually running beremote with that version, and the Novell OES2 server finally showed up on the main Backup Exec server.  I was able to successfully perform a backup, though of course it threw out a warning that I was running an older agent.  I then upgraded it to the R3 RALUS (5204.4) and I could still connect.  I was able to also then establish a trust relationship.  Finally, I applied the R3 SP1 patch to the agent, ran a test backup, and everything is working.

Not sure why a fresh install of the R3 agent doesn't work, but upgrades to it work and that's good enough for me.

Joe