Gregg:
Heya. Some quick comments:
> 2) Let's see here:
> - - I don't think i can put a computer on the unprotected (WAN) side of the
> firewall, by defualt my routeer forces everthing behind the firewall.
> - - I put my PC directly on the net w/o the router/firewall and i still got a
> "ReadExact: Socket error while reading." error message. So i guess it's not
> my firewall.
>
> 3) We actually use VNC at my work on multiple computers on our network so
> i'm pretty sure that port isn't being blocked.
As per #2, we agree that your home firewall isn't causing
the problem. But as for #3...keep in mind that your workplace firewall
doesn't try to filter any traffic until it *leaves* your workplace
LAN. So...intra-LAN, VNC sessions would never see a firewall, and
so you'd expect them to work. This sorta confirms that it *is* your
workplace firewall that's refusing to allow the outgoing connections.
> As for changing the VNC
> server listening port, i'm not exactly sure about how i'd go about that.
In case you didn't see it, it was bit further down in the
same Digest version your email was in:
| Using regedit, you can enter the port number directly without any of the
| arithmetic. The keys/values you want are:
|
| [HKEY_CURRENT_USER\Software\ORL\WinVNC3]
| "AutoPortSelect"=dword:00000000
| "PortNumber"=dword:00000015
|
| The PortNumber value, 15, is hexadecimal for 21 which you can enter as
| 21 when you use regedit. As a sanity check, after you enter these, you
| will see that the VNC server properties show 4294961417 for the display
| number.
Good luck!
-Scott
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
