Jayne Keller said: > I think I see what we must do now. Please correct me if I am wrong. Your > reply was very helpful because I did not understand that the Java client > port was just calculated by subtracting 100 from the non-Java client port. > > We are running the server on a Microsoft Windows 200x or XP system, so the > 5900 for the port number is in the registry. We have been using a Linksys > router to map port 23 into 5900 and port 80 into 5800 and we have not > changed the registry. We have a static IP address we use in conjunction > with the Java client that we use for nothing else.
OK, makes a bit more sense now, since VNC can't know that you are doing the port forwarding with the Linksys device. Unfortunitely the WinVNC files used to serve the viewer are part of the binary and can't be changed independently. > If we change the port in the registry to 180 and use the Linksys router to > map port 23 into 180, I think we will cause the Java client to use port 80 > in communication and retain port 23 for the non-Java client. Correct? > > Thanks for your help. > > Jayne It sounds like it will work at first, but I think you will find out that the source for the Java page will have port 180, not 23. This is for the same reason as above, VNC can't know what the Linksys is doing to the ports. I think you might want to take a look at TightVNC for your situation. They have added a feature that allows the HTTP and RFB ports to be set seperately, so you can set the ports correctly on the server machine and just have the Linksys pass them directly (80 -> 80, 23 -> 23). -- William Hooper _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
