Terminal Services test
Terminal Services test
we recently had an unexplained failure of the terminal services on one of our machines. I am trying to find a way to set up a HostMonitor test to tell me when it goes down again (if it does).
How could I maybe test terminal services? (executing external program "may" work, but I don't think mstsc will respond as hoped.
Thanx,
How could I maybe test terminal services? (executing external program "may" work, but I don't think mstsc will respond as hoped.
Thanx,
Ok, there is 1st version of TSCheck utility available at
http://www.ks-soft.net/download/tscheck.exe
This is command line utility that can be used with Shell Script test method
http://www.ks-soft.net/hostmon.eng/mfra ... m#chkShell
There is 1 mandatory parameter:
- host:<hostname>
and 2 optional parameters:
-user:<user_name>
-password:password
Any feedback will be appreciated
Regards
Alex
http://www.ks-soft.net/download/tscheck.exe
This is command line utility that can be used with Shell Script test method
http://www.ks-soft.net/hostmon.eng/mfra ... m#chkShell
There is 1 mandatory parameter:
- host:<hostname>
and 2 optional parameters:
-user:<user_name>
-password:password
Any feedback will be appreciated
Regards
Alex
Hi Alex,
When I try mstsc /v:xxx.xxx.xxx.xxx I get the Login-Screen of our Citrix and I can login.
So you are right, there is compatibility.
When I use tscheck.exe -host:xxx.xxx.xxx.xxx the session hangs "forever" (at least 2 minutes). Ctrl-C doesn't work. I have to close the DOS-Box hardly.
Our Citrix is not reachable from the Internet.
I can send two Wireshark traces (which email address ?)
mstsc is running against TCP-Port 3389
tscheck uses 445 (and 139) that request is RST by Citrix.
Is it possible to enable debug mode ?
Regards
Juergen
When I try mstsc /v:xxx.xxx.xxx.xxx I get the Login-Screen of our Citrix and I can login.
So you are right, there is compatibility.
When I use tscheck.exe -host:xxx.xxx.xxx.xxx the session hangs "forever" (at least 2 minutes). Ctrl-C doesn't work. I have to close the DOS-Box hardly.
Our Citrix is not reachable from the Internet.
I can send two Wireshark traces (which email address ?)
mstsc is running against TCP-Port 3389
tscheck uses 445 (and 139) that request is RST by Citrix.
Is it possible to enable debug mode ?
Regards
Juergen
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Actually, tscheck.exe does not use neither RDP protocol by Microsoft nor ICA protocol by Citrix because it is quite hard to implement in such small application. However, it uses Terminal Services API, that works over RDP and ICA protocols, to reach remote Terminal Service. http://msdn2.microsoft.com/en-us/library/aa383468.aspxJuergenF wrote:When I try mstsc /v:xxx.xxx.xxx.xxx I get the Login-Screen of our Citrix and I can login.
So you are right, there is compatibility.
What OS is installed on the computer, where you are trying to start tscheck.exe?JuergenF wrote:When I use tscheck.exe -host:xxx.xxx.xxx.xxx the session hangs "forever" (at least 2 minutes). Ctrl-C doesn't work. I have to close the DOS-Box hardly.
By, default Terminal services uses port 3389. tscheck.exe uses this port as well. However, tscheck.exe also uses ports 445 or 139 to resolve the Netbios name of the target machine because it is requirement of Terminal Service API. As I understand, ports 139 and 445 are blocked by the firewall in your environment, right? Could you enable such ports to be reached from your IP? It might help.JuergenF wrote:mstsc is running against TCP-Port 3389
tscheck uses 445 (and 139) that request is RST by Citrix.
If you are unable to enable ports 139 or 445 on the server, you may install RMA on the server and use Schell Script test method to start tscheck.exe localy by RMA.
Regards,
Max