Windows RealVNC server not accepting connections

[Mike Miller]

I'm running the latest Free RealVNC server in service mode on a WinXP box
and it isn't accepting any connections. I tried to connect to localhost
and I get a dialog box right away saying the connection closed
unexpectedly. I'm not prompted for a password.

The icon is in the tray saying it is running.

What do you recommend I do to troubleshoot this?

I found the log in the Windows Event Viewer. When I look at properties,
this is what I see for every attempt from localhost:

SocketManager: unknown listener event: 0

But when I try to connect from a Linux machine on the subnet, it doesn't
register anything. When I use nmap on the Linux box to look at the
Windows box, I see that port 5900 is "filtered" rather than "open".

I was able to use "vncviewer -listen" on the Linux box to receive a
connection from the VNC server on Windows. That worked but only
momentarily. It locked up almost right away and then the VNC server
crashed on Windows, including the usual Microsoft request to report the
error, which I did.

Mike

[Gregg Levine]

Post by Mike Miller
I'm running the latest Free RealVNC server in service mode on a WinXP box
and it isn't accepting any connections.  I tried to connect to localhost and
I get a dialog box right away saying the connection closed unexpectedly.
 I'm not prompted for a password.
The icon is in the tray saying it is running.
What do you recommend I do to troubleshoot this?
I found the log in the Windows Event Viewer.  When I look at properties,
SocketManager: unknown listener event: 0
But when I try to connect from a Linux machine on the subnet, it doesn't
register anything.  When I use nmap on the Linux box to look at the Windows
box, I see that port 5900 is "filtered" rather than "open".
I was able to use "vncviewer -listen" on the Linux box to receive a
connection from the VNC server on Windows.  That worked but only
momentarily.  It locked up almost right away and then the VNC server crashed
on Windows, including the usual Microsoft request to report the error, which
I did.
Mike
_______________________________________________
VNC-List mailing list
http://www.realvnc.com/mailman/listinfo/vnc-list

Hello!
If I remember correctly, using VNC on Windows is tricky. Is it on the
"allowed programs list" for the firewall? And for trying to connect to
it on the host, you'd need to enable that feature during the startup
routines.

-----
Gregg C Levine ***@gmail.com
"This signature fought the Time Wars, time and again."

[Mike Miller]

Post by Mike Miller
I'm running the latest Free RealVNC server in service mode on a WinXP
box and it isn't accepting any connections. I tried to connect to
localhost and I get a dialog box right away saying the connection closed
unexpectedly. I'm not prompted for a password.

I realized that I was allowing connections only from a certain other
machine on the subnet, and was therefore blocking connections from
localhost. I fixed that and then was able to make the connection from
localhost. So I guess this is what we see in the event log when WinVNC is
disallowing a connection (at least if it is from localhost):

SocketManager: unknown listener event: 0

Post by Mike Miller
But when I try to connect from a Linux machine on the subnet, it doesn't
register anything. When I use nmap on the Linux box to look at the
Windows box, I see that port 5900 is "filtered" rather than "open".
I was able to use "vncviewer -listen" on the Linux box to receive a
connection from the VNC server on Windows. That worked but only
momentarily. It locked up almost right away and then the VNC server
crashed on Windows, including the usual Microsoft request to report the
error, which I did.

Any ideas? Why would the server crash after making a connection to a
listening viewer?

I'm guessing that my problem making a normal connection is due to some
kind of firewalling problem. I'm trying to turn all of that off. It's
hard to figure out exactly where the problem is, though.

Mike

[Mike Miller]

Post by Gregg Levine
If I remember correctly, using VNC on Windows is tricky. Is it on the
"allowed programs list" for the firewall?

I think there are multiple layers of firewalling and I'm probably missing
something.

Post by Gregg Levine
And for trying to connect to it on the host, you'd need to enable that
feature during the startup routines.

I'm not sure I understand you. The service is running and it now accepts
connections from localhost (at least up to the password prompt, but I
haven't gone beyond that because it gets tricky to log into Windows from
localhost).

Mike