I have installed the trial version of 24x7 on my W2K server through a Terminal Services client.

When I try to connect to an instance of 24x7 running in a Terminal Server client session from my machine using Remote Control, I get a "Requested Server Not Active Message" even though I have 24x7 running in the Terminal Server session.

Do I need to do anything special to get this to work?

Is 24x7 running in the Master or Remote Agent modes?
If not, it does not listen for network connections, if yes, verify settings in the Tools/Options,Network, make sure you have there the same protocol and port number as the connecting piece.

: I have installed the trial version of 24x7 on my W2K server through a
: Terminal Services client.

: When I try to connect to an instance of 24x7 running in a Terminal Server
: client session from my machine using Remote Control, I get a
: "Requested Server Not Active Message" even though I have 24x7
: running in the Terminal Server session.

: Do I need to do anything special to get this to work?

: Is 24x7 running in the Master or Remote Agent modes?
: If not, it does not listen for network connections, if yes, verify settings
: in the Tools/Options,Network, make sure you have there the same protocol
: and port number as the connecting piece.

In the Tools/Options dialog box in the Network tab, I did not have the "Distributed Server Mode enabled" checkbox checked. When I checked this I was able to successfully connect remotely.

As a suggestion, you might want to make it a little clearer in the help topic that this option needs to be checked in order for you to use the Remote Connect functionality.

Thank you for your patience.

: In the Tools/Options dialog box in the Network tab, I did not have the
: "Distributed Server Mode enabled" checkbox checked. When I
: checked this I was able to successfully connect remotely.

: As a suggestion, you might want to make it a little clearer in the help topic
: that this option needs to be checked in order for you to use the Remote
: Connect functionality.

: Thank you for your patience.

Having successfully connected to 24x7 running in my terminal service session, I have changed 24x7 to run as a service on the server. I have set it to run under the LocalSystem account and rebooted the server. I have verified that the 24x7 service is started on the server.

But now when I try to connect to the 24x7 service on the server using Remote Control I get a message "Host PACCARESDEV not found. Requested server not active". I have not changed anything in my Remote Host Profile Setup for PACCARESDEV which worked when I ran 24x7 as an application instead of a service.

Is there something else I need to configure to connect to the 24x7 service using Remote Control?

LocalSystem does NOT have access to the network, that's why you cannot connect to the server. Either run the service using domain admin account or run don't run 24x7 (Mater or Remote Agent) as a service and start it after you manually logon to the network.

Please note that this is Windows networking limitation, and not 24x7 limitation.

: Having successfully connected to 24x7 running in my terminal service session,
: I have changed 24x7 to run as a service on the server. I have set it to
: run under the LocalSystem account and rebooted the server. I have verified
: that the 24x7 service is started on the server.

: But now when I try to connect to the 24x7 service on the server using Remote
: Control I get a message "Host PACCARESDEV not found. Requested server
: not active". I have not changed anything in my Remote Host Profile
: Setup for PACCARESDEV which worked when I ran 24x7 as an application
: instead of a service.

: Is there something else I need to configure to connect to the 24x7 service
: using Remote Control?

: LocalSystem does NOT have access to the network, that's why you cannot
: connect to the server. Either run the service using domain admin account
: or run don't run 24x7 (Mater or Remote Agent) as a service and start it
: after you manually logon to the network.

: Please note that this is Windows networking limitation, and not 24x7
: limitation.

I had one of the domain administrators come over and change the 24x7 service to login under a domain admin account on the server but I still cannot connect to the service using Remote Control from my desktop. I can access 24x7 on the server from my desktop using Remote Control when I run it in interactive mode.

A couple of questions:
- I am running the evaluation copy of 24x7. I think I had read in one of the postings that you needed to run the service under LocalSystem since it displays the message box upon startup but if I run under LocalSystem, you are saying I can't see the service. Is this issue going to go away when I use a licenced copy of 24x7 that I can run the service under a domain account (which I then should be able to see from my desktop)?

- I am hoping I do not actually need to run the 24x7 service under a domain administrator account since this is a potential security risk - using an account with domain admin priviledges which can do just about anything. I should be able to run the service under a domain account with just the network resources it should need and no more - please confirm.

- If my connectivity problem is not due to the fact I'm running an evaluation copy of 24x7, is there something else I should try since I've tried running the service with a domain admin account and I couldn't connect?

Thank you for you continued help

The evaluation version must be run under LocalSystem otherwise you cannot start the service. You need to the Evaluation Reminder screen which Windows can show only for LocalSystem services.
That's why you cannot connect because the service is not really started. It is waiting for someone to click the Continue button on the Reminder.
The licensed copy does not show the interactive Reminder or any other screen on startup.

: I had one of the domain administrators come over and change the 24x7 service
: to login under a domain admin account on the server but I still cannot
: connect to the service using Remote Control from my desktop. I can access
: 24x7 on the server from my desktop using Remote Control when I run it in
: interactive mode.

: A couple of questions: - I am running the evaluation copy of 24x7. I think I
: had read in one of the postings that you needed to run the service under
: LocalSystem since it displays the message box upon startup but if I run
: under LocalSystem, you are saying I can't see the service. Is this issue
: going to go away when I use a licenced copy of 24x7 that I can run the
: service under a domain account (which I then should be able to see from my
: desktop)?

: - I am hoping I do not actually need to run the 24x7 service under a domain
: administrator account since this is a potential security risk - using an
: account with domain admin priviledges which can do just about anything. I
: should be able to run the service under a domain account with just the
: network resources it should need and no more - please confirm.

: - If my connectivity problem is not due to the fact I'm running an evaluation
: copy of 24x7, is there something else I should try since I've tried
: running the service with a domain admin account and I couldn't connect?

: Thank you for you continued help