On 14/08/2003 at 6:41 p.m. William Hooper wrote:
>The server does have a debug mode. Unfortunately "Unable to connect to
>server" is generally a networking problem, not a VNC one.
Thought as much. Was hoping VNC could diagrnose at least some idea as to why
it wasn't able to do it's thing and help us poor fleshies.
>I wouldn't be too sure. A number of ISPs started blocking port 5900 after
>a MS Windows trojan used the VNC code.
Wow, news to me.
Surely they didn't start doing that in the last couple of days though...
Should I re-set the ports to something uncommon do you think.
>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)?
Yes, checked and all looks clear to me.
>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.
Tried it with firewalls in place (as it was when it was working fine) and with
all firewalls offline, no difference.
---
Karl @ Copy King PN
Store Manager
Shop 55
The Plaza
Palmerston North
Ph/Fx: (06) 355-1853
NOTE: Please ring before sending faxes, as we will not accept unannounced faxes.
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
