Client Automation Standard Practitioners Forum
cancel

CAS 7.2 Port problem

SOLVED
Go to solution
Highlighted
sandeep mathur
Outstanding Contributor.

CAS 7.2 Port problem

Hi Guys,

When I run dissover software/hardware inventory or Application usage I am getting error like failed attemting connect to remote agent:3465.But when i try telnet 3465 from Management Agent installed node, i am not able to telnet to that port. But when I run telnet < Management node> 3465
I am able to telnet to that port. Pls tell me what might be problem.

I think this port problem is not permitting me to get software details of the managed agent from management server. Please tell me how to open the port 3465?

Pls help me out.

Regards,
Sandeep.
23 REPLIES
Karl Skelton
Acclaimed Contributor.

Re: CAS 7.2 Port problem

Page 30 of the CAS 7.2 guide has a section detailing what Ports and EXE's need to be excluded in you Firewalls both on the management server and client side.

If you need help with the exclusions then you'd be better off refering to your firewall vendor documentation.

Karl.
sandeep mathur
Outstanding Contributor.

Re: CAS 7.2 Port problem

Hi Karl,

I had installed Agent to Management server now.Now I am able to get software inventory data of Management server easily.But I am not able to get the software inventory data of agent installed remote managed clients.It is giving error like
"Failed to Notify remote device - Reason: MUMVIKHNNMS:3465 -> timed out after 3600 seconds"

Pls help me out.

Regards,
Sandeep.
Karl Skelton
Acclaimed Contributor.

Re: CAS 7.2 Port problem

As per my previous posting. Have you confirmed all the firewall setting are correct on both server and client?

Why don't you try totally disabling both firewalls - if you can do this - and run a quick test again. Maybe this would prove if you have a firewall issue or not!

Karl.
sandeep mathur
Outstanding Contributor.

Re: CAS 7.2 Port problem

Hi Karl,

I am very confident that my firewall is disabled from both ends.I have looked at it once again it is disabled from both ends.


Regards,
Sandeep.
Karl Skelton
Acclaimed Contributor.

Re: CAS 7.2 Port problem

MUMVIKHNNMS is the remote client?
Can you ping MUMVIKHNNMS from the management server?
sandeep mathur
Outstanding Contributor.

Re: CAS 7.2 Port problem

Yes, I can able to it ping it from the management server.Also 3465 port is open from both ends.I have tested it with telnet.

Regards,
Sandeep.
Karl Skelton
Acclaimed Contributor.

Re: CAS 7.2 Port problem

on the client. check that the notify daemon is running. check the radexecd.log in the Agent\log folder. This should show the service as running and it should also show the incoming notify command from the server.
sandeep mathur
Outstanding Contributor.

Re: CAS 7.2 Port problem

Yes,I have checked it.its running. I have attached radexecd.log with it.Please look at it n let me know.

Also, If i try sc\\MUMVIKHNNMS query radexecd
I got
SERVICE_NAME: radexecd
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN))
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

Regards,
Sandeep.
sandeep mathur
Outstanding Contributor.

Re: CAS 7.2 Port problem

Here is that radexecd.log

Regards,
Sandeep.
Karl Skelton
Acclaimed Contributor.

Re: CAS 7.2 Port problem

so in the log we clearly see that some remote cmds are being recieved...
CMD: radskman sname=DISCOVER_INVENTORY,dname=AUDIT,startdir=SYSTEM,rtimeout=7200,port=3464,ip=MUMVIKHCCM.godrejinds.com,cop=y,mnt=y,JOBID=N:410:411

CMD: radskman sname=CCM_USAGE_AGENT,dname=USAGE,startdir=SYSTEM,rtimeout=7200,port=3464,ip=MUMVIKHCCM.godrejinds.com,cop=y,mnt=n,JOBID=N:416:417

We also see some errors...

Data received exceeded max length of [8]

Not sure what the error refers to but it appears that both Discovery_inverntory and Usage_agent install are running.

check you Agent\log\connect.log for errors!
Karl Skelton
Acclaimed Contributor.

Re: CAS 7.2 Port problem

and what is running on IP addresses...
10.13.15.229
10.13.15.92

I see both in the notify log.
sandeep mathur
Outstanding Contributor.

Re: CAS 7.2 Port problem

Hi Karl,

I am sending you the connect.log of MUMVIKHNNMS now. Also 10.13.15.229 is Management server of HPCAS 7.2.

No Agent is installed on 10.13.15.92.

Pls check the connect.log and let me know

Regards,
sandeep.
Karl Skelton
Acclaimed Contributor.

Re: CAS 7.2 Port problem

check the log; you'll see...

Failed to connect to [tcp:MUMVIKHCCM.godrejinds.com:3464] SAP [RADIA_DEFAULT]

And...
RADCONCT [Radia was unable to perform the requested action - due to a network connection failure with the manager. Please contact your system administrator for assistance.]

Do you have a working DNS?
Can you client resolve - MUMVIKHCCM.godrejinds.com
Is port 3464 open on the management server?
Is there any other corp firewall that maybe blocking ports?
sandeep mathur
Outstanding Contributor.

Re: CAS 7.2 Port problem

HI Karl,

Not able to resolve MUMVIKHCCM.godrejinds.com.Shall I add the IP & hostname in the hosts file.?

I am able to telnet to 3464,139,445,3465 ports.My firewall is blocked.

what shall I do now.

Regards,
Sandeep.
Karl Skelton
Acclaimed Contributor.

Re: CAS 7.2 Port problem

Shall I add the IP & hostname in the hosts file.?
Well how many clients would you have to do this on. Probably not the best idea!

Sure you can do this on one machine to test... but best bet is to resolve the DNS issue.
sandeep mathur
Outstanding Contributor.

Re: CAS 7.2 Port problem

HI Karl,

I have given IP & hostname in hosts file of managed client and tested it.
But still the same error I am getting.

Regards,
Sandeep.
Karl Skelton
Acclaimed Contributor.
Solution

Re: CAS 7.2 Port problem

but can you then ping the dns host from the client?
Does it resolve?

Currently this looks like a DNS\network issue. Get that resolved first before you then go back and test with CAS.
sandeep mathur
Outstanding Contributor.

Re: CAS 7.2 Port problem

DNS has been resolved for MUMVIKHCCM.But when i run the discover software/hardware inventory it is saying like this.

I am really not getting whats happening here.


Regards,
Sandeep.
Karl Skelton
Acclaimed Contributor.

Re: CAS 7.2 Port problem

Screenshot doesn't help at all.

What did you do differently?
Are you notifying the same client?

Try restarting CAS server.

sandeep mathur
Outstanding Contributor.

Re: CAS 7.2 Port problem

Hi Karl,

Tried restarting CAS server.Nothing worked. I cannot see the invenotry reports tab now.

Please help me out.Points assured.


Regards,
Sandeep.

Karl Skelton
Acclaimed Contributor.

Re: CAS 7.2 Port problem

Hi Sandeep,

Please open a support case with HP for this one now. I think we've come to the end of what we can resolve in the forum!

Karl.
sandeep mathur
Outstanding Contributor.

Re: CAS 7.2 Port problem

Hi Karl,

After we have changed the MS to DNS configuration.The database is not able to detect the change that has happened after DNS configuration has been done.None of tabs are working now.I must open a support case for it.
Thanks for ur support.Please help me in the future also.

Regards,
Sandeep.
sandeep mathur
Outstanding Contributor.

Re: CAS 7.2 Port problem

Thanks for ur support.

Sandeep.