Viewer Window Does Not Open

[Azrael]

Hi,

I've been using UltraVNC to remote to my home machine from work for some time now.

All of a sudden, yesterday, it stopped working.

I connect to my machine, input my VNC password and then nothing.

The window just doesn't appear and VNC closes.

I use the MSRC4 plugin with it.

I've even uninstalled my client and re-installed it.

Any ideas?

Here is my VNC Log.

Code: Select all

Started and Winsock (v 2) initialised
bufsize expanded to 4352
Registered connection with app
Saving connection info
Saving to C:\DOCUME~1\RSKEVI~1.HLS\LOCALS~1\Temp\options.vnc
Viewer is C:\Program Files\UltraVNC\vncviewer.exe
Connected to XXXXXX.is-a-geek.net port XXXXX
RFB server supports protocol version 3.6
Connected to RFB server, using protocol version 3.4
VNC authentication succeeded
Clipboard changed
Don't send initial clipboard!
rdr::Exception (2): rdr::EndOfStream
Deregistered connection from app
Exiting
VNC viewer closing down

and my MSRC4 Log:

Code: Select all

09/06/05 09:31:47 : StartUp
09/06/05 09:31:47 : REGISTRY MS RC4 Plugin,Sean E. Covel,Mar 12 2005,1.1.8.0,MSRC4Plugin.dsm
09/06/05 09:31:48 : Set Params
09/06/05 09:31:48 : REGISTRY MS RC4 Plugin,Sean E. Covel,Mar 12 2005,1.1.8.0,MSRC4Plugin.dsm
09/06/05 09:31:48 : InitVars
09/06/05 09:31:48 : GetCryptoVersion.
09/06/05 09:31:48 : Acquiring the Crypto Context.
09/06/05 09:31:48 : Crypto acquired a Crypto Provider Context. 
09/06/05 09:31:48 : Crypto Version = 2
09/06/05 09:31:48 : OS is 'Windows XP'
09/06/05 09:31:48 : Using provider ''
09/06/05 09:31:48 : Max Key Length 128
09/06/05 09:31:48 : GetEnvVar (registry) programfiles = C:\Program Files 
09/06/05 09:31:48 : SetParams - StartUp.
09/06/05 09:31:48 : ***** VIEWER Application *****
09/06/05 09:31:48 : Trying to find the key file
09/06/05 09:31:48 : Looking at the registry
09/06/05 09:31:48 : Looking for C:\Program Files\ultravnc\rc4.key
09/06/05 09:31:48 : Found key at C:\Program Files\ultravnc\rc4.key
09/06/05 09:31:48 : CryptAcquireContext |15059640| || || |1| |-268435456|
09/06/05 09:31:48 : CryptAcquireContext |15059644| || || |1| |-268435456|
09/06/05 09:31:48 : Reading KeyBlob
09/06/05 09:31:48 : Importing ExponentOfOne KeyBlob
09/06/05 09:31:48 : Importing KEY KeyBlob
09/06/05 09:31:48 : Reading KeyBlob
09/06/05 09:31:48 : Importing ExponentOfOne KeyBlob
09/06/05 09:31:48 : Importing KEY KeyBlob
09/06/05 09:31:48 : Key File Read.
09/06/05 09:31:49 : Shutting Down.

09/06/05 09:31:53 : StartUp
09/06/05 09:31:53 : REGISTRY MS RC4 Plugin,Sean E. Covel,Mar 12 2005,1.1.8.0,MSRC4Plugin.dsm
09/06/05 09:31:53 : Set Params
09/06/05 09:31:53 : REGISTRY MS RC4 Plugin,Sean E. Covel,Mar 12 2005,1.1.8.0,MSRC4Plugin.dsm
09/06/05 09:31:53 : InitVars
09/06/05 09:31:53 : GetCryptoVersion.
09/06/05 09:31:53 : Acquiring the Crypto Context.
09/06/05 09:31:53 : Crypto acquired a Crypto Provider Context. 
09/06/05 09:31:53 : Crypto Version = 2
09/06/05 09:31:53 : OS is 'Windows XP'
09/06/05 09:31:53 : Using provider ''
09/06/05 09:31:53 : Max Key Length 128
09/06/05 09:31:53 : GetEnvVar (registry) programfiles = C:\Program Files 
09/06/05 09:31:53 : SetParams - StartUp.
09/06/05 09:31:53 : ***** VIEWER Application *****
09/06/05 09:31:53 : Trying to find the key file
09/06/05 09:31:53 : Looking at the registry
09/06/05 09:31:53 : Looking for C:\Program Files\ultravnc\rc4.key
09/06/05 09:31:53 : Found key at C:\Program Files\ultravnc\rc4.key
09/06/05 09:31:53 : CryptAcquireContext |15059640| || || |1| |-268435456|
09/06/05 09:31:53 : CryptAcquireContext |15059644| || || |1| |-268435456|
09/06/05 09:31:53 : Reading KeyBlob
09/06/05 09:31:53 : Importing ExponentOfOne KeyBlob
09/06/05 09:31:53 : Importing KEY KeyBlob
09/06/05 09:31:53 : Reading KeyBlob
09/06/05 09:31:53 : Importing ExponentOfOne KeyBlob
09/06/05 09:31:53 : Importing KEY KeyBlob
09/06/05 09:31:53 : Key File Read.
09/06/05 09:31:54 : Shutting Down.

[merwinb]

This isnt helpful at all - But I'm having the same exact issue.

I've been working on getting UltraVNC packed into an MSI file - everything seems to be going well. Files copy properly, service is created and started correctly, regsitry entries are entered. I kick up the viewer, it prompts me for a username/password - it says "password accepted" and then viewer just dies.

I have the same exact response when not using the MS logon settings.

Anyone have any suggestions?

[redge]

I experienced this issue
you have less 30sec to move your mice cursor to password field and complete it.
othervise, you had exactly what you wrote.

[JBREV]

I have the same problem, have you figured this out yet?

[redge]

try new viewer v2 if fix your issue and let us feedback
http://sc.uvnc.com/v2

more details about viewer v2
[topic=4137][/topic]


[edit]
anyway, if you don't move mice pointer and click to password field,
you have same issue ![edit]

[merwinb]

As I previously mentioned, I'm working on getting the UltraVNC server packed into an MSI file for easy deployment.

Everything works perfectly if I run the UVNC setup app, but not when I run the MSI file.

I followed the automation checklist and made sure that:
-Files are being copied
-Admin & Default properties are being set (in the registry)
-Winvnc is being installed as a service and started

I'm not using MSLogon right now, for testing purposes, however I seem to get the same exact issue regardless of which version I'm using.

So - my question is, what am I not doing that is being done by the installer?

I assume the my registry entries are correct because I am directly exporting them to a file once I've configured the UltraVNC Server from the administrator panel. I do question the password field, and how that may carry over to a different pc though.

Any help would be much appreciated.


Note to others experiencing this issue: The issue is resolved by running the UltraVNC Setup app. The new viewer app is awesome, but it wasn't required to resolve this situation.

[merwinb]

As I previously mentioned, I'm working on getting the UltraVNC server packed into an MSI file for easy deployment.

Everything works perfectly if I run the UVNC setup app, but not when I run the MSI file.

I followed the automation checklist and made sure that:
-Files are being copied
-Admin & Default properties are being set (in the registry)
-Winvnc is being installed as a service and started

I'm not using MSLogon right now, for testing purposes, however I seem to get the same exact issue regardless of which version I'm using.

So - my question is, what am I not doing that is being done by the installer?

I assume the my registry entries are correct because I am directly exporting them to a file once I've configured the UltraVNC Server from the administrator panel. I do question the password field, and how that may carry over to a different pc though.

Any help would be much appreciated.


Note to others experiencing this issue: The issue is resolved by running the UltraVNC Setup app. The new viewer app is awesome, but it wasn't required to resolve this situation.

Solution = don't be a retard.

The problem is that while configuring the MSI file, I failed to configure the service as being able to "interact with desktop".

*facepalm*

duh.

[Subbiah]

Hi,

I installed and used UVNC for a month or so now and all of a sudden the vnc viewer is not working. My work pc is WinXP Pro, Home pc is Win2KPro which is running UVNC Service. I am trying to connect to home from work.

At first I used the existing configuration to connect home (release meant for Production install). This is what happened:
I immediately got the message that "vncviewer.exe has encountered a problem and needs to close. We are sorry for the inconvenience."

Then after reading this thread, I copied and replaced vncviewer.exe with vncviewer12Beta.exe, renamed it as vncviewer.exe and then tried to start the viewer. The viewer started. But, when clicked on New Connection, the viewer failed> I got the same window "vncviewer.exe has encountered a problem and needs to close. We are sorry for the inconvenience."
I tried the above with vncviewer11Beta.exe as explained earlier. Met with same result.

When I tried to log in to my home pc, I was able to do fine using "Java". When I entered http://<Home IP address>:5800 in my browser, I was prompted for VNC authentication and then MS authentication at the pc and then was able to log in to the computer just fine. (The color was off but that is not the issue here).

Is there anything I can do about this issue? I am unable to follow all the remedies prescribed here, since I do not understand them. I would appreciate any help u might be able to provide.

[Rudi De Vos]

type %temp% in the explorer
This open your temp directory.
Check for options.vnc file...and remove.

Possible the option file corrupt.
(same file is used by all versions)

If this is not the cause, is has to be triggered by some other program.
Because it worked for some time..
Was some extra security software installed, auto MS updates.
Spyware checkers, Firewall....

Try to temp deactivate them and check again.

[Subbiah]

Hi there,

Thank u for ur help. I appreciate ur time on this.

I looked for options.vnc. Couldn't find it anywhere in my hard drive. I couldn't fine any file when I searched as *.vnc .

Yes, I did update my WinXP at work a few days back. Whatever MS proposed, I installed them all. Also, there was an email recently from my sys admin that they are routing all internet traffic thru our proxy server.

But, I am able to connect to my home pc thru Java. When I enter "http://<Home IP Address>:5800" in to my browser, my router asks for my password and then I am able to see my home pc and then I log in to it, etc. If these recent patches from MS or changes in settings in my work network could be cause of the viewer not starting, should not these changes affect me logging thru Java also? But, this works fine.

Once again, thank u for ur help. I appreciate ur time on this.

[Subbiah]

Hi there,

I disabled my Symantec AntiVirus program and ran the Viewer again. The same problem happened.
1) The MS window "Open File - Security Warning" pops up. It has the warning message "The Publisher Could not be verified. Are you sure you want to run this software?". I click Run.
2) Then VNC's Viewer window opens up. When I click on Help, I see the version: UltraVNC Win32 Viewer 1.2 Beta
3) Then I click on New Connection. And the program fails. I get the window Vncviewer.ext and asks me if I want to send a report to MS about this problem.
4) In the corresponding MS DOS window this is what I see:
fh is 3
Started and Winsock (v 2) initialised
bufsize expanded to 4352
Registered connection with app
5) Tried to copy and paste all the data that was in the text sent to MS but couldn't copy them.

I would very much appreicate it if anyone can help.

[redge]

don't take care about the version of beta, take care only built date of beta !

actual beta until I post this message:
built: Sep 17 2005 21:59:50

re-download and try again
http://www.uvnc.com/v2/

[Subbiah]

Hi there,

Thank u for ur help.

This is how I resolved the situation:
1) I uninstalled UltraVNC.
2) Went in to Win XP registry and searched and removed all the occurrences of the following:
a) Searched for ORL and removed all keys and the folders under it
b) Searched for *vnc* and removed all registry keys
3) Removed c:\program files\ultravnc folder.
4) Reinstalled ultravnc v1.0.1 again.
This time it worked great!

Conclusion:
Updating MS patches in my XP box somehow broke UVNC. Plain uninstall and reinstall of UVNC did not help. Uninstall of UVNC followed by removal of ALL UVNC related entries in the registry and then reinstalling UVNC got the VNC Viewer to work.

Thanks for all ur help and time! I appreciate ur time.

Looks like this link is not working: http://www.uvnc.com/v2/

;-)
Subbiah

[Rudi De Vos]

http://sc.uvnc.com/V2

[Subbiah]

Thank u for ur time!
;-)

[N0nE]

Please I have the newest stable version.
All-server and viewer run on W2000 machines.
On 26.IX. the viewer stops working, e.g. it accept my password connect to server but the window is -nobody knows where.
After canceling the viewer it is still there -it must be stopped in taskmanager.

I tried the procedure with uninstalling and removing all keys ORL, VNC, etc.
but nothing happen
the same problem after installing ultravnc.

[N0nE]

Hi,
I tried it also on XP machine (viewer), but the result was the same, as if the viewer is blocked from server after days of using -but UltraVNC is free and not shareware.

Secondly:
I proof that it is not the whole truth. The window appear BUT only as a line on top of the screen (cca 80% of screen lenght). REALLY, you can see the tin line. after interrupting with taskmanager you can proof that it is vncviewer.

the beta shows clean-free mdichildwindow

please help

[redge]

did you change the default value MTU=1500 to another size can happen

drtcp can help you to fix this issue to put to normal value 1500 !
but if you use between VPN, you need to reduce to 1492 !
that the dilem !

[N0nE]

I have never changed MTU,
I have chcecked to correct it with your drtcp, but the problem lives
I have never made the same things on both machines(viewers) W2k and WXp.
I have NO other connection to the server and thus I cannot say what on the server side is.

[N0nE]

I tried to change my provider and the same problem.
Can I connect to the server on which is MSRC4 NOReg plugin installed with other software???
the server/viewer is english 1.0.1 release
Please help

[redge]

• viewer encryption disabled can't connect to winvnc encryption plugin enabled.
• viewer encryption enabled can't connect to winvnc encryption plugin disabled.
• viewer encryption plugin disabled can connect to winvnc encryption plugin disabled.
• viewer encryption plugin enabled can connect to winvnc encryption plugin enabled.

[bevtech]

I have experianced a similar problem. Do you have a public IP address coming from your ISP?? Or is your router ip 192.168.0.1 or 10.0.0.1 etc.(On The WAN SIDE) I had the same problem if I double NAT which basically means I come in on 192.168.0.1 gateway then route into another 192.168.1.1 and have NAT turned on. The only success that I had with the SSL repeater is that I have it coming into my reapeater from a public ip one that is routable from all over the world. Then forward that public ip port 443 from my router to repeater which is 192.168.X.X. It only works for me this way. I am sure that you could spend sometime forwarding ports around but if your ISP is sending you a non routable Ip then they maybe controlling a NAT that you cant change. Thus giving you this issue on how your other vnc work and your ssl isnt. Keep in mind that ssl is still in beta..