I am currently trying out v3 before deciding on whether or not to upgrade from v2.4.11. I have tried to set up a remote agent but when I test this, I get an error claiming that the remote server has not been started. The trace is below.

A netstat on the remote machine confirms that the Remote is listening on the specified port number.

I wondered whether this feature does not work on "30 Day Trial" instances.

TRACE INFO
===========
DPB01 Connection(013FEA58): ConnectToServer : application(10095), location(DBGM)
, driver(WinSock). ... (00000000)
SMI02 Connection(08132910): ERROR OCCURRED: Distributed Service Error: E20 The c
onnection request has been refused by the server. (user name 'Scheduler'). (8004
2013)
DPB01 Connection(013FEA58): ConnectToServer : application(10095), location(DBGM)
, driver(WinSock). FAILED (80042013)

From the trace "The connection request has been refused by the server".

Have you enabled the security on the Agent? If yes, what kind of security is setup: by user name/password or by IP address?

: I am currently trying out v3 before deciding on whether or not to upgrade
: from v2.4.11. I have tried to set up a remote agent but when I test this,
: I get an error claiming that the remote server has not been started. The
: trace is below.

: A netstat on the remote machine confirms that the Remote is listening on the
: specified port number.

: I wondered whether this feature does not work on "30 Day Trial"
: instances.

: TRACE INFO
: ===========
: DPB01 Connection(013FEA58): ConnectToServer : application(10095),
: location(DBGM)
: , driver(WinSock). ... (00000000)
: SMI02 Connection(08132910): ERROR OCCURRED: Distributed Service Error: E20
: The c
: onnection request has been refused by the server. (user name 'Scheduler').
: (8004
: 2013)
: DPB01 Connection(013FEA58): ConnectToServer : application(10095),
: location(DBGM)
: , driver(WinSock). FAILED (80042013)

No security is set up. Here is the trace from the Agent. It contains a failure message:

Starting distributed service...
SMI10 Listener (013FDCF8): Start Listening: computerName(), serviceName(10095),
driverName(WinSock). ... (00000000)
SMI Property: __DriverName='WinSock'
SMI Property: __ApplicationName='10095'
SMI Property: __Options='Dedicated=1'
SMI Property: Dedicated='1'
SMI AddRef SMI_TRACE(013FDAE8) refCount(2)
WSD11 AddRef: RefCount for listener object = 1
SMI10 Listener (013FDCF8): Start Listening: computerName(), serviceName(10095),
driverName(WinSock). SUCCEEDED (00000000)
DPB30 Listener (013FDA28): Start Listening : application(10095), location(), dr
iver(WinSock). FAILED (80004005)
WSD11 AddRef: RefCount for listener object = 2
DPB55 Memory Session : (00000000) count(3205), total(466944), alloc(360829)
, free(93688)
WSD11 AddRef: RefCount for listener object = 3
WSD11 AddRef: RefCount for listener object = 4
DPB56 Memory Proc Common : count(1089), total(86016), alloc(60566), free(20165)

WSD11 AddRef: RefCount for listener object = 5

: From the trace "The connection request has been refused by the
: server".

: Have you enabled the security on the Agent? If yes, what kind of security is
: setup: by user name/password or by IP address?

Do you have 24x7 v2 or 24x7 service already running on that computer. The message in the trace indicates that the Agent could not start listening on 10095 port. This is mostly caused by the port being used by another application.

: No security is set up. Here is the trace from the Agent. It contains a
: failure message: Starting distributed service...
: SMI10 Listener (013FDCF8): Start Listening: computerName(),
: serviceName(10095),
: driverName(WinSock). ... (00000000)
: SMI Property: __DriverName='WinSock'
: SMI Property: __ApplicationName='10095'
: SMI Property: __Options='Dedicated=1'
: SMI Property: Dedicated='1'
: SMI AddRef SMI_TRACE(013FDAE8) refCount(2)
: WSD11 AddRef: RefCount for listener object = 1
: SMI10 Listener (013FDCF8): Start Listening: computerName(),
: serviceName(10095),
: driverName(WinSock). SUCCEEDED (00000000)
: DPB30 Listener (013FDA28): Start Listening : application(10095), location(),
: dr
: iver(WinSock). FAILED (80004005)
: WSD11 AddRef: RefCount for listener object = 2
: DPB55 Memory Session : (00000000) count(3205), total(466944), alloc(360829)
: , free(93688)
: WSD11 AddRef: RefCount for listener object = 3
: WSD11 AddRef: RefCount for listener object = 4
: DPB56 Memory Proc Common : count(1089), total(86016), alloc(60566),
: free(20165)

: WSD11 AddRef: RefCount for listener object = 5

A netstat when the Remote is not running shows that port 10095 is not being used. I also tried starting up the Remote using a few different port numbers and I always get the same error in the trace.

: Do you have 24x7 v2 or 24x7 service already running on that computer. The
: message in the trace indicates that the Agent could not start listening on
: 10095 port. This is mostly caused by the port being used by another
: application.

Try starting Remote Agent on port 1096. In the Options property put "Retry=3"
After agent is started, make sure "Enable remote access Security" is not checked in the Tools/Security/Remote Agent Access menu.
Also check that you don't have RESTRICT.LST file on the Agent's computer.

Test Connection to the Agent using "Test Connect" button in the Agent Profile dialog on the computer from where you connect to it.

: A netstat when the Remote is not running shows that port 10095 is not being
: used. I also tried starting up the Remote using a few different port
: numbers and I always get the same error in the trace.

Did all of these and still it would not work. However, I did finally get it working. Here is how:

On remote, added a new user and assigned it to the Administrators group. I then turned When testing the connection from the Master, I used the details of this new user and it worked. It seems that the Security is used regardless of whether the "Enable Remote Access security" checkbox is checked or not.

Thanks
Greig

: Try starting Remote Agent on port 1096. In the Options property put
: "Retry=3"
: After agent is started, make sure "Enable remote access Security"
: is not checked in the Tools/Security/Remote Agent Access menu.
: Also check that you don't have RESTRICT.LST file on the Agent's computer.

: Test Connection to the Agent using "Test Connect" button in the
: Agent Profile dialog on the computer from where you connect to it.