Hmmm. If you get to the RDP login prompt, and *then* it fails,
it suggests that you're not running the EchoVNC application as a
registered service, but rather only as a user-space application. Is
that the case? If not, does it all work when you run the service on
the default port, TCP 3389?-Scott On Mar 25, 2008, at 1:45 AM, Jimmy E. Kongskov - DATAJEK wrote: > > Hello! > > I have a Windows 2003 server with a 2.32 client where I can't connect > through RDP (VNC works). > > I can see that the incoming request is forwarded to the server but > it just > times out after I enter my username and password. > > EchoVNC says the RDP service is active and I can also connect to the > server > "directly" not using EchoVNC. > > I'm not using the standard 3389 port but 4000 but I don't think that > is the > culprit. > > How do I troubleshoot this? > > Jimmy ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Echovnc-users mailing list Echovnc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/echovnc-users
