Hi Robert. Are you saying that you can then just see the remote console or actually do remote control over port 80? Do you have any generic information on this technique that you could share?

>Thanks for the tip, was not aware of the console mode...
>
>I have been using VNC, but wrote a little fox app that allows it's use without open ports (on the client side). Several way to accomplish this using a polling technique using a common port (http/FTP) to request the client push his screen to you (easy with a fixed IP)
>
>Just FYI
>
>Bob
>
>>Finally! I've been trying to find this for years. For an application that I develop and manage, I need to have console access to the server to run the app. I've been using PCAnywhere and VNC which work perfectly well, but was starting to get push back from corporate system admins who didn't want to open the VNC and PCAnywhere ports. As of today, one of the admins simply refused to open any port except 3389 (remote desktop). Googling I manage to find a switch for remote desktop that forces the session to be a console session instead of a virtual session. The command line is mstsc /console
>>
>>So basically I start the server app, and it runs 24/7. Periodically I will sign in to the same sessiona and check for any errors or do a custom query.
>>
>>Anyone had any problems running an application logged in with terminal services in this way vs VNC/PCAnywhere?
>>
>>BTW, here is the link to the solution http://firechewy.com/blog/archive/2005/10/18/926.aspx