Please reply to the list.
If your VNC servers don't reply to telnet, that means they don't
work (as expected).
Maybe you've got firewall enabled?
On Fri, May 16, 2008 at 4:50 PM, Gavin Baer <[EMAIL PROTECTED]> wrote:
> None of the VNC servers respond to telnet, even though the VNC works.
>
> -----Original Message-----
> From: Seak, Teng-Fong [SMTP:[EMAIL PROTECTED]
> Sent: Friday, May 16, 2008 4:57 AM
> To: vnc-list@realvnc.com
> Subject: Re: Cannot connect over WAN with new thin clients
>
> Have you tried telnet to the server to see if it responds?
>
> On Thu, May 15, 2008 at 5:07 PM, Gavin Baer <[EMAIL PROTECTED]> wrote:
>> I have been using VNC free 4.0 to connect between a client running Win XP
>> and several different servers running win 98 or Win NT embedded over a WAN
>> with no issues.
>> I am now trying to connect to servers running Win XP embedded (on Neoware
>> thin clients). I am able to use VNC on a LAN with these machines, but when
>> I have the thin client at another location on the WAN I can no longer
>> connect. I am able to ping the thin clients, but not able to connect with
>> VNC, and get a timeout message. Any ideas to resolve this?
>> thanks,
>> Gavin Baer
>> [EMAIL PROTECTED]
> _______________________________________________
> VNC-List mailing list
> VNC-List@realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
>
>
_______________________________________________
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
