Network Error: Connection reset --- Assistance required

jhughesjr · Post by **jhughesjr** » 2004-12-29 16:17

When attempting to connect to 2 of my home machines running ultravnc I can not. When I try to log in using the browser plugin I enter my password and then receive the error Network Error: Connection reset. Here is what the winvnc log in the system32 directory says:

C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncsockconnect.cpp : accepted connection from 64.236.208.25
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncclient.cpp : vncClient() executing...
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncserver.cpp : AddClient() done
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncclient.cpp : client connected : 64.236.208.25 (1)
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncclient.cpp : DSMPlugin Pointer to socket OK
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncclient.cpp : negotiated version
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncPasswd.h : PASSWD : ToText called
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vsocket.cpp : socket error 2: 10054
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncserver.cpp : removing unauthorised client
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncserver.cpp : RemoveClient() done
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncclient.cpp : ~vncClient() executing...
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncclient.cpp : deleting socket
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vsocket.cpp : closing socket

When attempting to use the ultravnc client app itself it displays a dialog box for a brief second and then goes away.
The winvnc log says:

C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncsockconnect.cpp : accepted connection from 64.236.208.25
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncclient.cpp : vncClient() executing...
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncserver.cpp : AddClient() done
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncclient.cpp : client connected : 64.236.208.25 (1)
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncclient.cpp : DSMPlugin Pointer to socket OK
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncclient.cpp : negotiated version
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncPasswd.h : PASSWD : ToText called
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vsocket.cpp : socket error 2: 10054
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncserver.cpp : removing unauthorised client
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncserver.cpp : RemoveClient() done
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncclient.cpp : ~vncClient() executing...
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vncclient.cpp : deleting socket
C:\c++\sourceforge\ultravnc\winvnc\winvnc\vsocket.cpp : closing socket

I can connect when I'm on my lan at home but not remotely from work.
I started having the problem when I upgraded winvnc from 3.5x to 4.x, so I thought I would try ultravnc as well. I'm using RC18. Using Firefox 1.0.

I have now upgraded one of my home machines to xp and installed remote desktop on it. I can remote desktop into my one home machine and log into a different one using ultravnc browser plugin. However soon as I try to connect from work directly using ultravnc I receive the error.

Any other info required to resolve this issue I will provide as I do not want to move to remote desktop but if I can not get this resolved I don't think I'll have any other choice.

ipsec · Post by **ipsec** » 2004-12-29 23:43

dont have vnc and ultravnc installed at the same time

Remove both instances of the programs.

Run registry cleaner - should remove all registry entries of both programs.

Install UltraVnc.

Test.

Do this for each machine... it is important that you reboot after you uninstall and very important that you remove all registry entries from the programs.. I hear they dont play well together.

jhughesjr · Post by **jhughesjr** » 2004-12-29 23:49

I had done this prior to installing ultravnc.
I guess I can try and uninstall it again.
Is the socket error 10054 pointing to some sort of registry issue?
Why the only failure when connecting from external machine?

ipsec · Post by **ipsec** » 2004-12-29 23:52

well the stupid question is - what did you install before this broke.

Some sort of dev kit or some program?

I would always go back to that program that was last installed and blame it.. because before it .. it worked.

You just never know about the registry.. its always good to just start off fresh regardless of what you are doing if you install something that is the same and or similar to an appy u have or had.

But more times than not if I do a clean uninstall and then install (of course a few reboots in there) I have more success than failure.

jhughesjr · Post by **jhughesjr** » 2004-12-30 13:50

I'm sorry I can be a bit confusing at times.

I have not installed any software after UltraVNC and then had it stop working. I have 2 machines both running Windows 2000 and they are not working.

At this point I am not certain there is an issue with the VNC server and not the client as Ultravnc works when I connect to it from an XP machine on the LAN but not when I'm outside of my LAN.

For all I know it could even be my router screwing things up but without knowing what the problem is I can't fix it.

The software needs to read registry keys in order for the registry to be an issue. If you were able to tell me that the software utilizes keys x,y and z when dealing with socket communication and authentication and those values should be a,b, and c that would be valuable information in tracing down the problem or what the socket error actually means ie., This is the error code for failure to decrypt the password then I could look and see if I have mismatched encryption packages on my machines.

ipsec · Post by **ipsec** » 2004-12-30 15:25

is your problem inside your outside your lan.

Then next did you set up your router to port forward correctly. **Biggest cause for not working outside of lan is incorrectly configured router**

Are you using a DSM plugin for security? - if yes re-generate the key and give it to the viewer machine... but if your laptop is the one you are trying to use outside it should have the right one since you said it works..

jhughesjr · Post by **jhughesjr** » 2004-12-30 16:28

is your problem inside your outside your lan.

I can not say for certain it is an inside/outside lan issue. I can say for certain that from work when I attempt to connect to one of two machines at home that the VNC Server generates the errors in the log that I posted in the first post.

Then next did you set up your router to port forward correctly. **Biggest cause for not working outside of lan is incorrectly configured router**

I believe so. I opened ports 5820, 5920 for one machine and 5810 and 5910 for the other machine. I have set them in the default and user settings as the ports to use. I'm fairly confident I opened them correctly. If the ports were not opened then the attempted access would not make it to the vnc server, never download the browser plugin, never ask me for a password and it is logging the attempts in the winvnc.log file.

Are you using a DSM plugin for security? - if yes re-generate the key and give it to the viewer machine...

no I'm not using the plugin.

but if your laptop is the one you are trying to use outside it should have the right one since you said it works..

Jeez, I confused you again.

The xp machine that works at home is not the xp machine that works at work. They are 2 different machines.

I have 3 machines at home 2 running Windows 2000 and ultra VNC and a 3rd now running Windows XP professional. My machine at work is also running Windows XP Pro so I was originally thinking there was some sort of issue with connecting to 2000 from XP however since I can connect to the 2000 machines from my new XP Home machine I think I can safely rule that out as an issue.

Since I can remote desktop into my XP machine at home and vnc to my other 2 windows 2000 machines this is less of an issue of necessity and more of an issue of wanting to figure out what is wrong and fix it.

ipsec · Post by **ipsec** » 2004-12-30 16:47

I am assuming you have tried using IE also.. since you said you are using FF...

At work - are you sure the port you are trying to connect to is not being blocked in any way?

Have you had a friend try to connect to these machines from the internet that isnt behind a corporate firewall / proxy?

-If you get your friend to connect to your home network via http://xxx.xxx.xxx.xxx:5820 address and you cant from work its something being blocked at work - e.g. the port is not set up to work from work or they allow initial communication then kill the port. This would require you to talk to your network admin / firewall inet person. ***Try IE and FF**

But of course you have to successfully test it from somewhere else first... then try it from work and see if the same thing occurs.