Unsuccessful tests

SC<->proxy<->Repeater<->proxy<->viewer

Unsuccessful tests

Postby guest2 » 2005-07-08 22:15

Tried SCIII prebuilt (SCIII_test4.exe) on a connection office-home.

I had:

PC1 (SCIII) --> LAN Firewall+ Company Proxy --> uvnc.com --> PC2 (UVNCViewer)
Win XP SP2 on both sides. PC1 is on the LAN (no real IP). PC2 open on the internet.

Tried with many different pair of IDs, but no success at all in many attempts to connect.
On PC2, I tried both the normal viewer and the Special Viewer. No success in either of the two, even if the two had a different behaviour:
- Normal v1.0.0 viewer:
After negotiate protocol version,
"Proxy Connection Failed"
- with Special Viewer:
"Run Time Error" immediately after starting the program. The connection window will come up all the same but almost immediately it said "Failed to connect to server"

On PC1, the SCIII server started and showed a Ballon on the tray saying :
"Connected - A support rep is connected [Baloon2C] #[Debug]"
But after about 10s it disappeared closing down automatically (this all the times whether the vncviewer on PC2 was on or off did not see to matter).

Hope this gives you some clues of what is going on....

One thing I do not underderstand:
-is SCIII capable of autodetecting the LAN proxy addess from the registry settings? Why don't you put a parameter in the properties pop-up just to be sure of what is detecting?
- is there anything else to be done to force it trough http port 80? (my firewall only opens port 80; not 8080!)
- does the message Connected on the traybar means that the PC1 (most problematic as behing the firewall) was ok in reaching uvnc.com?
guest2
 

Postby Rudi De Vos » 2005-07-08 22:38

Only the special viewer works (SSL encryption is needed)

Viewer: Check if you have no ghost viewer in the background running
--->else crash

SCIII use the registry to detect the proxy settings

-Run SCIII_test4.exe
-Don't connect
-enter %temp% in explorer
-you see now a temp subdir with the extracted files
(winvnc.exe helpdesk.txt...)
-copy directory to some non temp directry
-cancel connection
-add the end of helpdesk.txt add
[DEBUG]
-run winvnc.exe
This should give you all information you need
By sure no other winvnc is running, (check task manager)
------------------------
DEBUG: not matched, addr to be SOCKSified: 216.55.178.47
DEBUG: resolving host by name: proxy.skynet.be
DEBUG: resolved: proxy.skynet.be (80.200.248.199)
DEBUG: connecting to 80.200.248.199:8080
DEBUG: begin_http_relay()
DEBUG: >>> "CONNECT 216.55.178.47:443 HTTP/1.0\r\n"
DEBUG: >>> "\r\n"
DEBUG: <<< "HTTP/1.0 200 Connection established\r\n"
DEBUG: connected, start user session.
DEBUG: <<< "Proxy-Agent: NetCache NetApp/5.5R5\r\n"
DEBUG: <<< "\r\n"
DEBUG: connected
DEBUG: start relaying.
DEBUG: send 54 bytes
DEBUG: recv 696 bytes
DEBUG: send 212 bytes
DEBUG: recv 75 bytes
-----------------------------------------
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 6029
Joined: 2004-04-23 10:21

Postby Guest » 2005-07-08 23:17

Good suggestions.
1) The vnc viewer crash was due to another running in the background (pressing cancel on connection does not remove it from background).
Now the VNC Viewer Special talks to the server, but no connection is established.

2) on the SCIII side (PC1), I get the debug window. Can I dump the data to a file somehow? They appear, stay ok for a while, but when getting an error the uvn closed immediately and so does the debg window.
I could only get read this:

Error number 10060.

Removing unauthorised client.

Cannot create a file when that file already exists.


It is always the same error message.
Always arriving after about 10s of attempt connection to uvnc.com.
Guest
 

Postby Rudi De Vos » 2005-07-08 23:29

click caption bar
Select edit
-->select all
-->copy
Standard dos window


10060 is a Connection Time-out

The interesting part is the http negotiation
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 6029
Joined: 2004-04-23 10:21

Postby Guest » 2005-07-10 17:19

Yes, I captured most of the message, but it is not so easy, as the debug window shuts very quickly once the connection cannot be established.
This is the result (almost all that appeared; possibly another 3-4 lines followed this before full shut down):

fh is 4
Sun Jul 10 18:15:54 2005
C:\c++\Z_SSL_SC\winvnc\winvnc\winvnc.cpp : sockets initialised
--The operation completed successfully.
Sun Jul 10 18:15:57 2005
C:\c++\Z_SSL_SC\winvnc\winvnc\winvnc.cpp : test... 127.0.0.1 59000
--The operation completed successfully.
C:\c++\Z_SSL_SC\SCcon\SCcon.cpp : 5901 --The operation completed successfully.

C:\c++\Z_SSL_SC\SCcon\SCcon.cpp : 216.55.178.47 --The operation completed succe
ssfully.
C:\c++\Z_SSL_SC\SCcon\SCcon.cpp : 443
--The operation completed successfully.
Sun Jul 10 18:15:58 2005
C:\c++\Z_SSL_SC\winvnc\winvnc\winvnc.cpp : server created ok
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncproperties.cpp : loading local-only settings
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncserver.cpp : KillAuthClients() done
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncserver.cpp : KillUnauthClients() done
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncserver.cpp : KillAuthClients() done
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncserver.cpp : KillUnauthClients() done
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncserver.cpp : authhosts cleared
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncserver.cpp : KillAuthClients() done
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncserver.cpp : KillUnauthClients() done
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncserver.cpp : KillAuthClients() done
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncserver.cpp : KillUnauthClients() done
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncpropertiesPoll.cpp : clearing user settings
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncclient.cpp : vncClient() executing...
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncclient.cpp : TEST 4
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncserver.cpp : AddClient() done
--The operation completed successfully.
C:\c++\Z_SSL_SC\SCcon\SCcon.cpp : Trying to connect to 216.55.178.47
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncclient.cpp : client connected : 127.0.0.1 (1)
--The operation completed successfully.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncclient.cpp : DSMPlugin Pointer to socket OK
--The operation completed successfully.
Error number: 10060
Sun Jul 10 18:16:19 2005
C:\c++\Z_SSL_SC\SCcon\SCcon.cpp : 2005/7/10 18:16:19 ERROR: connect unsuccessful


--Cannot create a file when that file already exists.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncserver.cpp : removing unauthorised client
--An existing connection was forcibly closed by the remote host.
C:\c++\Z_SSL_SC\winvnc\winvnc\vncserver.cpp : RemoveClient() done
--The operation completed successfully.

Moderated by redge at 2005-09-29 17:04:
disabled Smilies in this post
Last edited by Guest on 2005-09-29 17:04, edited 1 time in total.
Guest
 

Postby redge » 2005-08-08 17:22

Rudi

SCIII trying to use repeater hosted on uvnc.com:443
down, closed, frozen, crashed ?

update ?

unpossible to use it, rca221 or some others was trying it without succes,
I tested for verify and failed.

thank you to fix it, regards
redge
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
redge
Super-Mod
Super-Mod
 
Posts: 6815
Joined: 2004-07-03 17:05
Location: Switzerland - Geneva

Postby redge » 2005-08-09 23:40

Ok, test of rca221 and my own test was again successfull :-)
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
redge
Super-Mod
Super-Mod
 
Posts: 6815
Joined: 2004-07-03 17:05
Location: Switzerland - Geneva

Postby Guest » 2005-08-10 22:10

Rudi,
have you restarted work on SCIII?

I still have the exact same error as mentioned above.

On PC1 (the one behind a firewall), the SCIII server starts and showed a Ballon on the tray saying :
"Connected - A support rep is connected [Baloon2C] #[Debug]"
But after about 10s it disappeared closing down automatically
(this all the times whether the vncviewer on PC2 was on or off did not see to matter).
The error message is the same logged above.

On the Viewer side (PC2) the viewer window stays forever at "Negotiate Protocol version".

Iam still trying to achive the connection:
PC1 (SCIII) --> LAN Firewall+ Company Proxy --> uvnc.com <-- PC2 (UVNCViewer)
Guest
 

Postby Guest » 2005-09-29 16:26

[quote="Anonymous"]
On PC1 (the one behind a firewall), the SCIII server starts and showed a Ballon on the tray saying :
"Connected - A support rep is connected [Baloon2C] #[Debug]"

same issue :-(
Guest
 

Postby bevtech » 2005-10-01 21:48

I had success by setting my own repeater up and using static ip then forwarding port 443 to my repeater workstation. You could also use dyndns if your ip isnt static. So far I have had excellent results.

All of my files came from

http://sc.uvnc.com/SCIII/

Make sure that you rename the crash fix.exe to vncviewer.exe or change the command line to reflect that

The only thing is that
any software firewall on the clients machine will ask it for permission to run vnc but that is a really major problem. :)
bevtech
Super-Mod
Super-Mod
 
Posts: 2191
Joined: 2005-08-03 14:07
Location: Pennsylvania, United States

Postby Guest » 2005-11-12 00:24

The problem I have is exactly as in the first post.

The server side is fixed and untouchable (company LAN, no permission to change anything at all). On the clinet side (vncviewer) I am open to any change. But of course given I want to control fromm home the work PC I would need to bypass the firewall and proxy server first, possibly via http port 80, which I am sure is open.

But this is what I do not know how to do!
Any help would be appreciated. SCIII does not seem to be able to establish a connection to uvnc.net proxy at all on my server side (while it seems to connect on the viewer not-firewalled side).
Guest
 

Postby redge » 2005-11-12 15:48

2 tests made
when I close scIII_test4 (with winvnc 6 october 2005 ) and vncviewer_ssl



there remind... never close until reboot
Active Connections

Proto Local Address Foreign Address State
TCP pioupiou:3741 localhost:3742 ESTABLISHED
TCP pioupiou:3742 localhost:3741 ESTABLISHED
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
redge
Super-Mod
Super-Mod
 
Posts: 6815
Joined: 2004-07-03 17:05
Location: Switzerland - Geneva


Return to SCIII

Who is online

Users browsing this forum: No registered users and 2 guests