Re: Trying to be a RDP client over Zebedee on a RDP server

"Ian Stocks" <[email protected]> Fri, 8 Apr 2005 21:37:35 +0100
Newsgroups gmane.comp.security.zebedee.general
Message-ID <099201c53c7a$cbd667f0$2c99a8c0@blue>
----- Original Message ----- 
From: "Tim Clark" <[email protected]>
To: <[email protected]>
Sent: Friday, April 08, 2005 9:13 PM
Subject: [Zebedee-talk] Trying to be a RDP client over Zebedee on a 
RDP server


> I've had RDP over Zebedee working fine for a while now using the 
> config below:
>
> tunnel 3389:a.b.c.d:3389
> command "mstsc c:\zebedee_DHS.rdp"
>
> I use to connect from an XP SP1 box (A) to a server (B). When I 
> enable remote access services on the A machine (it starts listening 
> on 3389), the zebedee connection I was using before to connect to B 
> stops working. the log says:
>
> ERROR: listener bind failed
> ERROR: can't create listener socket: (Unknown error)
>
> I tried to do tunnel "a.b.c.d:3389" instead of "tunnel 
> 3389:a.b.c.d:3389", but that doesn't work even when remote access 
> services is off.
>
> Any help is appreciated. Thanks.

The local remote access service on box (A) is using port 3389, so 
Zebedee cant use it, so you need to specify a different port number. 
Something like :-

tunnel 3390:a.b.c.d:3389

and then need to specify that the Remote access client (mstsc) connect 
to the new port, something like :-

mstsc localhost:3390

HTH,
Ian. 



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