RE: [Echovnc-users] Echovnc on Windows Server 2003

[Alexander Alekseev]

I tried running echowinvncpre03 on the remote 2k3s box I’m trying to access, and got the same problem where the connection would start to happen on my home box, and then nothing. Here are my logs if they're any help:   (Please note that I through I had it working for a minute as follows: working physically at 2k3s box, used MS Remote Desktop to connect to home XP box, then used echovnc to connect to 2k3s box. This allowed echovnc viewer on home xp box to see the 2k3s box screen for a moment, but started to cascade the screens, like when you point a camcorder into a TV, LOL)     ===echoserverlog 06/02/2006 18:02:56.656 06/02/2006 18:02:56.656 Get MSG_PROXY_FIND_PARTNER,  sockfd=532 06/02/2006 18:02:56.656 PartnerEmailId=rlserver, sockfd=532 06/02/2006 18:02:56.656 FindAuthConnectionByEmailId: pPartnerConnection=0xa57fe8, foundItemCount=1 06/02/2006 18:02:56.656 FindAuthConnectionByEmailId returned ok 06/02/2006 18:02:56.656 These connections are in the same group 06/02/2006 18:02:56.656 Reply with MSG_PROXY_PARTNERFOUND, sockfd=532 06/02/2006 18:02:56.656 Reply buffer: partnerIp=66.238.196.82 06/02/2006 18:02:56.734 Get MSG_CONNECT_TO_PEER,  sockfd=532 06/02/2006 18:02:56.734 PartnerEmailId=rlserver, sockfd=532 06/02/2006 18:02:56.750 Found only 1 partner auth connection, sockfd=532 06/02/2006 18:02:56.750 Send partner with MSG_CONNECT_TO_PEER (channelcode/InitiatorEmail,DhPart1), using partner sockfd=388 06/02/2006 18:02:56.750 Reply with MSG_CHANNEL_CODE (channelcode),  sockfd=532 06/02/2006 18:02:57.203 Get MSG_PEER_KEY,  sockfd=388 06/02/2006 18:02:57.203 PartnerEmailId =alex,  sockfd=388 06/02/2006 18:02:57.218 Find ChannelCode in Server GlobalChannelCodeList 06/02/2006 18:02:57.218 channelCode=0000556235, authId=66.238.196.82.1420, partnerChannelCode=00003bdf31, partnerAuthId=192.168.1.2.3938 06/02/2006 18:02:57.218 PartnerConnection->m_userEmail=alex,  pPartnerConnection->m_authId=192.168.1.2.3938 06/02/2006 18:02:57.218 Found a partner, send MSG_PEER_KEY (channelcode/dhpart2) to partner via sockfd=532 06/02/2006 18:02:57.281 ------------------------------- 06/02/2006 18:02:57.281 Add new cconnection: sockfd=412 from 192.168.1.2:4010 06/02/2006 18:02:57.281 Get MSG_DATA_CHANNEL_CONNECT,  sockfd=412 06/02/2006 18:02:57.296 clientEmailId=alex, sockfd=412 06/02/2006 18:02:57.296 Mark this as a RELAY connection, sockfd=412 06/02/2006 18:02:57.296 Relay connection, no more block on recv 06/02/2006 18:02:57.484 ------------------------------- 06/02/2006 18:02:57.484 Add new cconnection: sockfd=280 from 66.238.196.82:1422 06/02/2006 18:02:57.500 Get MSG_DATA_CHANNEL_CONNECT,  sockfd=280 06/02/2006 18:02:57.500 clientEmailId=rlserver, sockfd=280 06/02/2006 18:02:57.500 Mark this as a RELAY connection, sockfd=280 06/02/2006 18:02:57.500 Relay connection, no more block on recv 06/02/2006 18:02:57.515 Found a pair of relay cconnections: sockfd=(412<->280) 06/02/2006 18:02:57.515 RelayBufferPair::Process Begins 06/02/2006 18:02:57.515 RelayDataProcess: m_partner1Sockfd=412, m_partner2Sockfd=280 06/02/2006 18:02:57.515 HCBufferData: P1(412): No data 06/02/2006 18:02:57.515 HCBufferData: P2(280): No data 06/02/2006 18:10:58.062 [Unregisterred Version]Delete relay connection 412 after 8 mins 06/02/2006 18:10:58.062 P1(412): recv failed, -1 bytes, break 06/02/2006 18:10:58.062 CRelayBufferPair (P1=412<->P2=280): status =-1, P1 close/error. 06/02/2006 18:10:58.062 RelayBufferPair::Process Ends 06/02/2006 18:10:58.062 [Unregisterred Version]Delete relay connection 280 after 8 mins 06/02/2006 18:10:58.078 Not found a matching connection to mark delete, it may be already deleted  412 06/02/2006 18:10:58.078 Not found a matching connection to mark delete, it may be already deleted  280   ===echovnclog 06/02/2006 17:57:27.437 echowarelog is ON 06/02/2006 18:01:41.750 LoginToEchoServer begins 06/02/2006 18:01:41.750 =>CreateProxyInfoClassObject 06/02/2006 18:01:41.765 <=CreateProxyInfoClassObject returned 3bf680 06/02/2006 18:01:41.765 SetIP=192.168.1.2, SetPort=1328, SetMyID=alex, SetMyPwd=275madison 06/02/2006 18:01:41.765 SetEncryptionLevel ON 06/02/2006 18:01:41.781 =>SetPortForOffLoadingData 06/02/2006 18:01:41.781 <=SetPortForOffLoadingData returned 1 06/02/2006 18:01:41.781 =>ConnectProxy 06/02/2006 18:01:42.750 <=ConnectProxy returned 0 06/02/2006 18:01:42.750 ConnectProxy was OK 06/02/2006 18:01:42.750 LoginToEchoServer ends 06/02/2006 18:02:56.640 ConnectionThread begins 06/02/2006 18:02:56.640 CONNECT_VIA_ECHOSERVER 06/02/2006 18:02:56.640 Connect2Partner begins 06/02/2006 18:02:56.640 Use the proxy 192.168.1.2:1328 06/02/2006 18:02:56.656 =>lpfnEstablishNewDataChannel 06/02/2006 18:02:57.421 <=lpfnEstablishNewDataChannel returned 4011 06/02/2006 18:02:58.921 StartVNCViewer: 127.0.0.1:4011 06/02/2006 18:02:58.921 ConnectionThread ends   ===proxylog ==============!!New Proxy Connection!!============== [02/06/06-18:01:41] Dll : DetectConnectionMethod begins [02/06/06-18:01:41] Dll : DetectConnectionMethod: <<<Checking Via Direct...192.168.1.2:1328>>> [02/06/06-18:01:41] Dll : DetectConnectionMethod: <<<Via Direct was OK>>> [02/06/06-18:01:41] Dll : DetectConnectionMethod ends [02/06/06-18:01:41] AC Dll : Attempt to connect to echoServer via Direct [02/06/06-18:01:41] AC Dll : Connection to proxy 192.168.1.2:1328 Error : 0.. [02/06/06-18:01:41] AC Dll : Connected to proxy...192.168.1.2:1328 [02/06/06-18:01:41] Added Socket : 424 to the connection list [02/06/06-18:01:42] AC Dll : Received Bytes on Authentication Socket Socket : 28 [02/06/06-18:01:42] AC Dll : Received Message - MSG_PROXY_CONNECTED. [02/06/06-18:01:42] DLL : PublicKey key generated... [02/06/06-18:01:42] DLL : Generated public key : …    [02/06/06-18:01:42] AC Dll : Received Bytes on Authentication Socket Socket : 348 [02/06/06-18:01:42] AC Dll : Received Message - MSG_PROXY_PUBLICKEY. [02/06/06-18:01:42] AC DLL : Get the client public key.... [02/06/06-18:01:42] AC DLL : Session key generated.... [02/06/06-18:01:42] AC DLL : Sending encrypted password.... [02/06/06-18:01:42] AC Dll : Received Bytes on Authentication Socket Socket : 59 [02/06/06-18:01:42] AC Dll : Received Message - MSG_PROXY_HANDSHAKECONFIRM. [02/06/06-18:02:56] ENDC Dll : Sending MSG_PROXY_FIND_PARTNER message to proxy [02/06/06-18:02:56] AC Dll : Received Bytes on Authentication Socket Socket : 46 [02/06/06-18:02:56] Dll : Received Message - MSG_PROXY_PARTNERFOUND. [02/06/06-18:02:56] ENDC Dll : rlserver Partner was found with Proxy 192.168.1.2:1328 [02/06/06-18:02:56] ENDC Dll : Partner Found for Establishing new Data Channel.. [02/06/06-18:02:56] DLL : PublicKey key generated... [02/06/06-18:02:56] DLL : Generated public key : ;[1] [02/06/06-18:02:56] ;[1] [02/06/06-18:02:56] ENDC Dll : Sent MSG_CONNECT_TO_PEER message to echoserver [02/06/06-18:02:56] AC Dll : Received Bytes on Authentication Socket Socket : 39 [02/06/06-18:02:56] ENDC Dll : Received message - MSG_CHANNEL_CODE. [02/06/06-18:02:57] AC Dll : Received Bytes on Authentication Socket Socket : 359 [02/06/06-18:02:57] ENDC Dll : Received message - MSG_PEER_KEY. [02/06/06-18:02:57] EncDec val for this proxy is : 1 [02/06/06-18:02:57] AC Dll : Connection to echoServer via Direct [02/06/06-18:02:57] ENDC Dll : Sending MSG_DATA_CHANNEL_CONNECT GetLastError returned : 0 [02/06/06-18:02:57] Dll : CreateLocalListeningSocket [02/06/06-18:02:57] ENDC Dll : Created Listening Socket on Port : 0 [02/06/06-18:02:57] Added Socket : 376 to the connection list [02/06/06-18:02:57] AC DLL : Get the client public key.... [02/06/06-18:02:57] AC DLL : Session key for data channel generated.... [02/06/06-18:02:57] Session Key : 058154525BC19678DE69C76334F8A7A1BA572A6D13E412A1FDF4558D3AEAAE28D05F3460BB65F1493A45 [02/06/06-18:02:57] Encryption/Decryption Option : 1 [02/06/06-18:02:57] Added Socket : 228 to the connection list [02/06/06-18:02:57] ENDC Dll : Establish Data Channel Event Set... [02/06/06-18:02:57] ENDC Dll : New listener socket port returned by the Dll : 4011 [02/06/06-18:02:57] ENDC Dll : Waiting for initiator to connect to port : 4011 [02/06/06-18:02:58] ENDC Dll : Accepting Client socket for Data Proxying :232   [02/06/06-18:02:58] New socket : 228 added to complete socket pair : 232 in list [02/06/06-18:02:58] ENDC Dll : Accepted Client socket for Data Proxying : 127.0.0.1:4012   [02/06/06-18:10:58] Socket 228 was closed by the client. Shutting down. [02/06/06-18:10:58] Shutting down and closing socket : 376 [02/06/06-18:10:58] Removing Listener Socket : 376 [02/06/06-18:10:58] deleting conn object       -----Original Message----- From: Scott Best [mailto:[EMAIL PROTECTED] Sent: Saturday, January 28, 2006 8:23 PM To: Alexander Alekseev Cc: echovnc-users@lists.sourceforge.net Subject: Re: [Echovnc-users] Echovnc on Windows Server 2003           Sorry: if you name echowinvnc1.2pre03.exe back to just echowinvnc.exe, it will then save its settings into itself. I'm not sure if that's a  feature or a bug just yet. :)   -Scott   On Jan 28, 2006, at 4:49 PM, Alexander Alekseev wrote:   > I tried echowinvnc 1.2pre03 on the 2k3server, and when I tried  > connecting to > it using echovnc 1.40/1.70 from the xp home box and it still  > disconnects > immediately. >  > BTW echowinvnc1.2pre03 doesn't save settings into itself? >  > -----Original Message----- > From: Scott Best [mailto:[EMAIL PROTECTED] > Sent: Saturday, January 28, 2006 11:04 AM > To: Alexander Alekseev > Cc: echovnc-users@lists.sourceforge.net > Subject: Re: [Echovnc-users] Echovnc on Windows Server 2003 >  > Alex: >  >     Just to confirm: you get to the VNC password prompt, and after you > connect, the session immediately drops, correct? If so, exactly what > flavor > of VNC Server are you running on the remote 2k3 server? >  > thanks, > Scott >  > On Jan 27, 2006, at 5:38 PM, Alexander Alekseev wrote: >  >> Using echovnc on remote 2k3 server, echoserver 1.40 on local, >> echovnc viewer >> on local. >>  >> When I connect to the remote 2k3 server, screen blinks the vnc >> viewer and >> disappears. >>  >> Here are my logs: >>  >> Echovnc proxy log on w2k3 server: > <snip> >  >  >  >  > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through  > log files > for problems?  Stop!  Download the new AJAX search engine that makes > searching your log files as easy as surfing the  web.  DOWNLOAD  > SPLUNK! > http://sel.as-us.falkag.net/sel? > cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Echovnc-users mailing list > Echovnc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/echovnc-users