When you say WAN, you mean the Internet side?  Or is it really a WAN?  That 
means your WinNT is a gateway connecting two LAN's?

        First, have you applied SP6a to your WinNT?  How about IE?  Second, make sure 
that within the LAN, a viewer can connect to your (WinNT's )VNC server.  If this part 
doesn't work (from what I understood, this seems to be your case), you don't have to 
look further; look into your WinNT.  Your problem happened after you installed your 
WinRoute Pro, right?  Check your software's manual to see if it's change your WinNT IP 
address in some way, and how to do "port forwarding" to itself.

> -----Message d'origine-----
> De : Theodore Kearley [mailto:[EMAIL PROTECTED]
> Envoyi : jeudi 18 mars 2004 16:00
> @ : VNC Mailing List
> Objet : Failed to Connect to Server
> 
> I am running VNC on Windows NT that is also running Kerio WinRoute Pro.
> I had to restart the PC yesterday and since it was restarted, I cannot
> access the PC with VNC.  I saw a posting that recommended trying to
> telnet the PC (telnet ip 5900) and see if it would connect using the
> public IP and the private IP but it would not.  All of the ports are
> open in the network configuration for both TCP/IP protocols.  Using
> www.gotomyvnc.com <http://www.gotomyvnc.com/>  shows no response from
> any display adapters.  I have stopped and restarted the VNC service and
> removed it and reinstalled it (both realvnc and tightvnc) all to no
> avail.  The WinRoute software is working fine - I can access the network
> to get to the terminal services server and use pcAnywhere to get to a
> host PC on the network.  There is nothing to configure for VNC to work
> in the router since it has a direct connection to the WAN.  Besides, I
> cannot connect on the internal address.
> 
> 
> 
> Any ideas as to what could be broken?
> 
> 
> 
> Thanks,
> 
> Theodore
_______________________________________________
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