Hmm... wonder if maybe you've got something in your TCP Wrappers blocking your Windoze box from accessing your Debian box? I'm not sure how to configure that in Debian, but in RedHat/Fedora, there's an /etc/hosts.allow and /etc/hosts.deny. Check to make sure you don't have something like "ALL: ALL" or "ALL: <ip.of.your.wbox>" in the hosts.deny file. I did something like that and blocked myself from getting in from work for awhile until I specifically allowed my external work IP in. :-)
-----Original Message----- From: Jerry Westrick [mailto:[EMAIL PROTECTED] Sent: Sunday, May 15, 2005 8:40 AM To: Robert Segelbaum; [email protected] Subject: Re: Kind of a newbie -- trying2talk2Ubox from Wbox On Sunday 15 May 2005 15:22, you wrote: > Dear Jerry, > > At 06:55 15/05/2005, Jerry Westrick wrote: > >Hello Robert... > > > >Please answer to list so all can see.... > > Thought that's what I did, by Cc'ing [EMAIL PROTECTED] But apparently > not, since I can't find this reply appearing in the thread, using my > browser...so how do I do it? I can't see ANYWHERE a "reply to thread" > option or indeed a "reply" option of any kind, on the Web, so I figured it > had to be done thru email. Which I did. But it STILL didn't go up...from > what I can see. > > >I suspect we are talking about typos, but just to make sure: > > > >999.999.999.999:5901 is not the same as > >999.999.999.999:1 > > > >The number after the colon is not the port number but the X-Windows > >instance. In the windows operating system there is only one Graphical > >Interface, in Linux that is not the case. > > > >The port number used is calculate as follows: > >5900 + window instance number. > > > >Or in your case 5901. > > > >Since I'm assuming you know all this I'll describe a way to debug your > >problem. > > Your assumption is valid! > > >Basically, we need to prove that the network is allowing you to connect. > >The easiest way to do this is to use telnet. so Try "telnet > >999.999.999.999 5901" This command will attempt to connect to port 5901 on > >999.999.999.999. > >If a vnc server is running there you will get a line with "RFB 003.003" or > >something like that. > > Did that, and that's exactly what I got. > Okay, we have proven that the vncserver is running, and that tcp/ip can get through... SO that only leaves out your client. There once was a problem with new versions of real vnc connecting to older versions of Tight vnc. Something about protocols getting mixed up.... There is a misc. option on the vnc client called "Only use protocol version 3.3"... Could you try that one? Jerry _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
