Do you have a firewall in place at your office that might be blocking all telnet packets?
Normally you would see something like "RFB 003.003" when connecting to an open VNC port with a telnet client. Let's back up to the beginning of things and see if we can establish what is going on... it will take a few exchanges to get it done, but it will likely be the fastest way to do it, and will help make sure you know exactly what is going on with your VNC access. Could you verify the following for me? I am including some notes from prior email, since I want to keep this info together for reference. 1 - There is a VPN in place at your work; things work fine if you access the network via the VPN. 2 - You don't use the VPN over your connection. 3 - For some reason, your VPN works only over dialup; it won't accept through-internet connections. 4 - You can access B through the Internet, but not W. 5 - This is an item you will need to probably check at work (actually a question). Does your firewall/router redirect traffic coming in on port 5903 to the internal IP address that W uses? ----- Original Message ----- From: "J. Meltzer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, 2002-06-02 09:03 Subject: Telnetting to B and W > Greetings. I cannot telnet to port 5900 on B, or to port 5903 (I have > the display set up as 3) on W or port 5900 on W. I get a "Could > not open a connection to" error. > > However, as I stated, I can VNC to B just fine - just not to W. > > I can ping both machines when on the VPN, both by hostname and > by IP address. > > I apologize if I was confusing you, but this whole thing is confusing > me. :-) > > Thanks, > > Jonathan > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
