Re: tshoot (WAS:Fails to spawn command line process)

Sean

I get the idea. No, the rdp client app doesn't take parameters. The file 
being launched is an rdp configuration file, so I changed the address it is 
set to connect to and added the port number: now it reads 
aaa.bbb.ccc.ddd:11965. I think this achieves the intended effect, but it 
still doesn't work. The server IS listening on 11965, but as soon as the rdp 
client is launched it immediately returns the  error "the client could not 
connect to the remote computer". Zedebee just hangs in there waiting for the 
client to connect, and the process has to be manually killed.

Tim

PS: could an operator please cover up/delete the IP address I accidentally 
left exposed in my last msg?

From: Sean Covel <seanecovel@co...>
Re: Re: tshoot (WAS:Fails to spawn command line process)
2005-03-09 08:43
Tim,

take a look at the vncviewer zbd file.  zebedee is probably redirecting
a local port (%d in the vncviewer) to the remote port through the
tunnel.  You need to tell your remote desktop app the port to connect to
instead of the usual port.

Does mstsc take a command-line parameter for port?  If it does than
you"ll need to specify it.  Again, see the vncviewer zbd file for an
example.  Its the %d parameter.

Its probably:

mstsc /v:localhost:%d

Sean




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click