Agent Communication Fails

Question

$(UI've installed NSM on Netware 6.5 SP7 and NFR on OES2 SP2 64bit in an eDirectory
Environment. I've installed the NFR agent on an OES2 SP2 64bit system. The agent is correctly configured with the IP address of the NFR engine server. The Agent shows up in the NFR Admin Console with a current heartbeat time. I have scheduled a scan of the server, but it always fails.
When I right-click the resource in the resource list and choose "Scan
now" I get the following error message:
Agent Not Available
The agent for APPS/APPS: does not appear to be active.
Check the agent status and try running again.

Answer 1

Chip,
1. You need to upgrade your NSM to version 3.0.2.
2. On your OES servers verify that the alternate server name in the
agent is a case sensitive match to the ncpserver name, and not FDN of
the server.
thanks,
NFR Development
On 8/18/2011 10:46 AM, carneyc wrote:
>
> I am having this same issue.
>
> I have Storage manager and File reporter 3.0.0.129 and File Report
> 1.0.2.99 running on OES2 sp2a. The file reporter agents installled on
> our Netware 6.5 sp7 servers scan fine. The first OES sp3 64 bit server
> that has the file reporter agent for NCP installed fine and displays
> running. I have stopped and started, disabled and enabled the agent and
> I am still getting this Agent Not Available error.
>
> The agent for server_name/volume_name: does not appear to be active.
> Check the agent status and try running the scan again.
>
> Any assistance on this would be greatly appreciated.
>
> Chip
>
>