All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
my PC is running Windows XP SP2 all patches, Firewall active
I'm using Checkpoint SecureRemote to connect to company LAN.
Maybe that blocks something although the TS test was successful and only the Citrix test failed.
I've tried from a W2K3 SP1 Server (where HM is running) in the LAN. That works - with and without specifying a user
So let me do some more tests in January from within the LAN.
I'll let you know the results.
For the moment it seems, that I'm happy with that test.
Many thanks for your support - even during christmas time.
JuergenF wrote:I've tried from a W2K3 SP1 Server (where HM is running) in the LAN. That works - with and without specifying a user
If you do not specify particular user, it uses context of the user, who started the process. So, does it work with Citrix or not?
I was logged in as domain admin at a W2K3 SP1 Server within the LAN and opened a DOS Box and tried to connect to Citrix
tscheck.exe -host:xxx.xxx.xxx.xxx
That worked
After that I used
tscheck.exe -host:xxx.xxx.xxx.xxx -user:domain\MyUser -password:Mypassword
That worked too.
What didn't work was using my XP PC connected to company LAN using Checkpoit VPN. That may have other reasons we don't have to find out.
JuergenF wrote:What didn't work was using my XP PC connected to company LAN using Checkpoit VPN. That may have other reasons we don't have to find out.
The first possible reason might be a firewall, that requires ports 145 or 139 to be opened. On the other hand, it might be some policy settings. I will try to find more information regarding this issue.
JuergenF wrote: So let me do some more tests in January from within the LAN. I'll let you know the results.
I am looking forward to hearing from you.
Hi Max,
I tested a bit more. The test is working fine.
But it doesn't show an error when we have that special issue with our Citrix server.
All active session can work with Citrix.
No new sessions can be established. But no error is shown. It's seems to hang during the login process or may be during building the Desktop.
That's not a problem of your test. That's our problem.
We will rebuild that Server soon.
JuergenF wrote:I tested a bit more. The test is working fine.
Great!
JuergenF wrote:But it doesn't show an error when we have that special issue with our Citrix server.
All active session can work with Citrix.
No new sessions can be established. But no error is shown. It's seems to hang during the login process or may be during building the Desktop.
Actually, our utility does not build Desktop, just logins. Could you explain what does mean "hangs", please? It never gets back? No output? Other issues?
JuergenF wrote:That's not a problem of your test. That's our problem.
We will rebuild that Server soon.
It might have been issued by security setings of Citrix server.
- The Server is running NT4 Terminal Services
- The Server is working well for all active User-Connections
- It is responding to ping
- New connections get the blue (or is it green) background screen from Windows NT4
- No Wallpaper or any Icons are shown.
- No LoginScript is displayed. (That is normally done during login)
- That situation keeps "forever"
- When we try to remotely reboot using psshutdown \\TerminalServer -f -r no error is shown, but reboot is not performed.
- We have to switch off that machine to reboot
- After reboot it's working well ... at least for a while
As I said, we will rebuild that machine soon - don't waste your time.
In field "start cmd" I type: "c:\program files\hostmonitor5\scripts\tscheck.exe"
In field "params" I type: -host:testserver
(I tried just leaving blank to provoke "unknown: server name is required" response, but also did not work)
I can run the script FINE from the command line:
"c:\program files\hostmonitor5\scripts\tscheck.exe -host:testserver"
(or without param to get "unknown: server name is required" response)
I also tried just typing in the path + params in the "start cmd" field, but I still get "unable to start script" error.
Server name you may specify into "Params" input box of "Test Properties" window. If you do not need username and password, you should not specify them at all. Just type "testserver" into "Params" input box.
I've noticed that when we disable a specific instance of the svchost process on the target machine that this test fails. Using the terminal services manager to connect to that machine fails as well. But the standard Remote Desktop (mstsc) still works fine. It's not a big deal as we would typically have all "svchost"s running, but I was curious if there might be an easy way to get this script to work even when svchost process is off. Thanks,
Actually, Remote Desktop (mstsc) uses RDP protocol to access Terminal Service. tscheck.exe utility does not use RDP protocol, but it uses Terminal Service API, that requires additional services started on the target machine ( http://msdn2.microsoft.com/en-us/library/aa383494.aspx ). I do not think we will implement functionality you requested soon.
