Hi, I'm currently having problems with a Linux installation of VNC version 4. We are using VNC v3X on WinTel without problems and are just starting to use Linux again.
SuSE Personal 9.1 installation (running in a VMWare instance) SuSE1-linux -> Corporate Net -> NAT F/W -> Internet -> NAT F/W (w/ port forwarding 5500) -> Home W2K machine VNC 3.3.7 On SuSE1-linux ./vncinstall /usr/local/bin vncserver :5 -name "SuSE1-linux" -geometry 1024x768 & vncconnect -display :5 <FW2 public ip address> On Home W2K machine VNC 4 (or 3) listener Up pops the X desktop no problems - really cool! Same machines, same network configuration VNC 4.0 On SuSE1-linux ./vncinstall /usr/local/bin vncserver :5 -name "SuSE1-linux" -geometry 1024x768 & vncconfig -display :5 -connect <FW2 public ip address> "connecting to <ip address> failed" On Home W2K machine VNC 4 (or 3) NOTHING! :-p If I repeat the tests in the office I can initiate a connection via vncconfig to a local IP address on the network (same subnet). Using the local network (& different subnet) it doesn't work however - routing problems within VNC (surely it is just a 'TCP/IP stack?). This points me towards a protocol / network / port forwarding type issue / UDP / TCP - has this changed between version 3 and 4? Any pointers? How can I dig further? At the moment I think I will have to go back to version 3 of the S/W which isn't 'ideal'..... Any ideas? Carl -- Carl Morgan DCG | Datapoint Surrey, UK Once you have flown, you will walk the earth with your eyes turned skywards, for there you have been, and there you long to return. - Leonardo de Vinci [demime 0.99d.1 removed an attachment of type application/ms-tnef which had a name of winmail.dat] _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
