Karl said:
> *********** REPLY SEPARATOR  ***********
>
> On 14/08/2003 at 11:27 a.m. William Hooper wrote:
>
>
>>There is a nice search feature.
>
>       Yeah, tried it, but WAY too much data came back for me to wade through.
>
>       After all, "Unable to connect to server" is such a common response, and
> thus a very common info request.
>
>       Maybe error-codes should be built into VNC perhaps, to try and narrow
> down the cause? Is that feasible?

The server does have a debug mode.  Unfortunately "Unable to connect to
server" is generally a networking problem, not a VNC one.
[snip]

>>Second, what kind of Internet connection (DSL, Cable, T1, etc.).  Could
>>your ISP have started blocking ports on you?
>
>       Doubt the ISP would try it, since it is our primary national
> telecommunication company.

I wouldn't be too sure.  A number of ISPs started blocking port 5900 after
a MS Windows trojan used the VNC code.

>       We are on a split-line ADSL connection - standard phone line that has
> been freq split - low freqs for phone/fax/EFTPOS, higher bands for ADSL
> only.
>
>       As I said, it started off working fine, then suddenly locked out.
>
>       Following the suggestion from another VNC user, I used NETSTAT -A from
> command prompt and can confirm server is listening on ports 5800 and
> 5900.

That doesn't mean VNC is accepting connections from anywhere in
particular, though.  Have you checked the AuthHosts registry setting (I
know someone else mentioned it)?

>>Is the WinVNC server accepting any connections (for example, from the
>>local network)?  Check out http://gotomyvnc.com and you can see both what
>>IP address you are connecting from, and test to see if your machine is
>>listening on the common VNC ports.
>
>       There is no local network. One PC only.
>
>       Tried that URL and no connection on any ports.

You most likely have a firewall in the way (either your own or your ISPs).
 Another option would be that VNC isn't binding to the interface, but I
would expect it to throw up an error message.  Maybe looking into the
WinVNC debugging isn't a bad idea.

http://www.realvnc.com/winvnc.html#11

-- 
William Hooper
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to