Re: Re: tshoot (WAS:Fails to spawn command line process)
"Ian Stocks" <[email protected]> Wed, 9 Mar 2005 21:06:13 -0000
| Newsgroups | gmane.comp.security.zebedee.general |
|---|---|
| Message-ID | <014701c524eb$d3f96aa0$2c99a8c0@blue> |
It's not clear (at least not to me) from your descriptions if you have all the bits in place. Do you have a two copies of zebedee running, one needs to be a server, and one needs to be a client. Your Terminal Services client on the Client end (call it Machine A), connects to the client verson of Zebedee on a port you can define (using the tunnel keyword in the config file). The Client version of Zebedee then connects to the Server version of Zebedee (on machine B), this connection is the encrypted and compressed portion. The Client to Server connection (zebedee to zebedee) is on another port number you can define (using the serverport keyword), it defaults to 11965 (0x2ebd). The server version of Zebedee then connects to the listening port of the Terminal Services service, as defined on the server end (using the target keyword). Your original post had 'serverport 3389', which is very wrong, this is the definition of the zebedee to zebedee connection. 3389 is used for Terminal services connections. Try re-reading the html help file example for VNC connection, replacing 5901 with 3389. Get back to us with any futher questions. Ian. ----- Original Message ----- From: "Tim Clark" <[email protected]> To: <[email protected]> Sent: Wednesday, March 09, 2005 8:24 PM Subject: [Zebedee-talk] 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 > _______________________________________________ > Zebedee-talk mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/zebedee-talk ------------------------------------------------------- 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