Terminal Services test

Steven · Post by **Steven** » Mon Apr 03, 2006 9:09 am

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,

KS-Soft · Post by **KS-Soft** » Mon Apr 03, 2006 10:56 am

What about simple TCP test?

Regards
Alex

Steven · Post by **Steven** » Mon Apr 03, 2006 11:07 am

That may be what we end up doing, but that would still only show if that tcp port is open, not if tsc is working properly.
Thanx,

Steven · Post by **Steven** » Wed Nov 15, 2006 1:04 pm

Any chance of making a TSC test with actual username/password to verify that TSC is working correctly?

KS-Soft · Post by **KS-Soft** » Wed Nov 15, 2006 8:36 pm

We have this task in "to do" list. Low priority

Regards
Alex

JuergenF · Post by **JuergenF** » Wed Nov 15, 2006 10:55 pm

Steven wrote:Any chance of making a TSC test with actual username/password to verify that TSC is working correctly?

I am interested in such test too.
Maybe that can raise priority a little bit

Steven · Post by **Steven** » Fri Nov 17, 2006 8:52 am

Thanks

KS-Soft · Post by **KS-Soft** » Fri Nov 17, 2006 12:53 pm

Ok

Regards
Alex

Nadir · Post by **Nadir** » Mon Nov 20, 2006 8:25 am

I am interested too.
Maybe that can raise priority a little more

KS-Soft · Post by **KS-Soft** » Thu Dec 21, 2006 2:06 pm

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

JuergenF · Post by **JuergenF** » Fri Dec 22, 2006 1:52 pm

Works fine, many thanks Alex

Please don't hit me. What I really wanted to request is a Login test for
Citrix Terminal Server.

I mixed that up.

Do you see a chance to implement such a test too ?

KS-Soft · Post by **KS-Soft** » Fri Dec 22, 2006 9:46 pm

Citrix? Yes, it should be usefull. May be in version 7...

Regards
Alex

KS-Soft · Post by **KS-Soft** » Mon Dec 25, 2006 9:24 pm

Looks like Citrix compatible with Windows Terminal Server API.
Our tscheck.exe does not work with Citrix properly?

Regards
Alex

JuergenF · Post by **JuergenF** » Tue Dec 26, 2006 12:56 am

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

KS-Soft Europe · Post by **KS-Soft Europe** » Tue Dec 26, 2006 5:10 am

JuergenF 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.

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.aspx

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.

What OS is installed on the computer, where you are trying to start tscheck.exe?

JuergenF wrote:mstsc is running against TCP-Port 3389
tscheck uses 445 (and 139) that request is RST by Citrix.

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.

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