Checking RDC Connectivity

[Cosmic Cruizer]

I need to find out if the RDC connection I am testing is actually working.
I'm using telnet to connect to port 3389. It's fine that it does not return
an error, but I'm interested in sending a string of text and getting a
response.

What string does RDC understand and what should be returned? If I can get
it to respond to a telnet probe, then I can figure out how to program a
scripting language to test the port.

 

[CTOS]

I need to find out if the RDC connection I am testing is actually working.

So what happens when to try to connect with the RDC client?

I'm using telnet to connect to port 3389. It's fine that it does not return
an error, but I'm interested in sending a string of text and getting a
response.

What string does RDC understand and what should be returned? If I can get
it to respond to a telnet probe, then I can figure out how to program a
scripting language to test the port.

Some MS tools you might be interested in:

"Terminal Services Application Compatibility
http://blogs.technet.com/vikasma/archive/2008/06/24/terminal-services-application-compatibility.aspx

or

"PortQry Command Line Port Scanner Version 2.0
http://www.microsoft.com/downloads/...47-C74B-4638-A2D5-AC828BDC6983&displaylang=en

C:\PortQryV2>PortQry.exe -n localhost -e 3389

Querying target system called:

localhost

Attempting to resolve name to IP address...

Name resolved to 127.0.0.1

querying...

TCP port 3389 (ms-wbt-server service): LISTENING

 

[Cosmic Cruizer]

So what happens when to try to connect with the RDC client?


Some MS tools you might be interested in:

"Terminal Services Application Compatibility "
http://blogs.technet.com/vikasma/archive/2008/06/24/terminal-services-a
pplication-compatibility.aspx

or

"PortQry Command Line Port Scanner Version 2.0"
http://www.microsoft.com/downloads/details.aspx?familyid=89811747-C74B-
4638-A2D5-AC828BDC6983&displaylang=en

C:\PortQryV2>PortQry.exe -n localhost -e 3389

Querying target system called:

localhost

Attempting to resolve name to IP address...

Name resolved to 127.0.0.1

querying...

TCP port 3389 (ms-wbt-server service): LISTENING

Thanks for your suggestions, but they are not going to help me. I'm
trying to create a test monitor to see if the port is actually
responding. I can do a GET on port 80, which returns information. This is
basically what I want to do with port 3389. (There is quite a bit more I
am actually doing, but right now I want to solve the issue with getting a
response on port 3389.)