Secure Path Manager problem with v4.0a agent

[Lawrence Bowen]

Hi all,

I have a server that is running Secure Path Agent 4.0a. I have added my management workstation in "Securepathcfg" on the 4.0a server as an authorised client. I have checked that the passwords match that in my SP Manager profile for that server. However I get this message when trying to view it:

"Wrong password or current client running SPM in NOT authorised to access Secure Path Agent on XXXXXXX!"

I have tried rebooting the server after adding the authorised client. I am using v3.1 build 024d of the Secure Path Manager.

Also, is Secure Path Agent 4.0a compatible with SWCC v2.2.0.213 ?

Any help much appreciated.
lawrence bowen

[Lawrence Bowen]

Hi, an update to the above problem...

In the meantime I have installed SPM v4.0a, which uses a web based GUI. I have managed to add all the other servers' Secure Path Agents to this GUI without a problem, simply by adding the SPM host name as an authorized client and then restarting the Secure Path Agent on the selected server. However, on the server mentioned above I still have the same problem!! The message I get when i try to add the agent is "unauthorized client: connection refused -1". This is after adding every type of name for the SPM host to the "authorized clients" box of the server's SP Agent configurer, and restarting the SP Agent in the Services applet. The clients.ini file has the host name in it.

Please Help!!!!

thanks - lawrence bowen

[Peter Lindblom]

Lawrence,

How have you authorised access for the SPM server?
Some times it seems to be a problem with name resolution.

So try the below to if it's help.

1. Add the IP address of the SPM server in the Secure Path Agent.
2. Add the host name of the SPM server in the Secure Path Agent.
3. Add the FQDN (Fully Qulified Domain Name i.e. host.domain.com).

>Also, is Secure Path Agent 4.0a compatible
>with SWCC v2.2.0.213 ?
No it's not compatible with SWCC.

Regards,

Peter

[Lawrence Bowen]

Hi, thanks for the suggestions but I have already done this! And still, "unauthorised client". I'm at a complete loss! I can ping the SPM server from the machine in question, and it's name resolves fine. I've added all three types of name/IP and restarted the SP agent, without success!

-lawrence bowen

[Ronald Hendriks]

are you sure hostname resolution works for that host? otherwise fix the names in the host file on the host and sma.

Next try : reinstall SP agent (in 4.X called server)

[Lawrence Bowen]

Ok, I got it going. It was my mistake as I made a typo in the host name, I'm very ashamed....

By the way, what version of SWCC should be used along with Secure Path v4.0a and where can it be obtained?

thanks, sorry for wasting time with this one.