You are right, it seems that the webramp is blocking the connections. Have you tried just port scanning the WebRamp from an external IP? You could then check if the port is even open. Does the webramp log successful and unsuccessful connection attempts? Check to see if logging is enabled for that port. Check your logs after a port scan to see if it blocking those ports. You may want to try and see if the ports being blocked both ways by the webramp. Try connecting to an external vnc server through those same ports to see if you can get through. If outgoing works but incoming requests from an external ip into your network does not then its just an issue of getting the webramp to allow that port.
Did you assign a "public lan server" for that port? You need to make sure that any traffic on those ports are being directed to the computer running VNC server. Also check the order of your rules. If you created your VNC rule after the default it will never get to it. Try moving your VNC rule higher in the list (not sure how you would do that). Hope that helps, Mike ----- Original Message ----- From: "Rodrigo Villarreal" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, December 12, 2001 11:44 AM Subject: Re: WebRamp 700s DSL router > But if my ISP is the culprit, then I would NOT be able to access my PC > regardless of the Router. And as I mentioned, I CAN access my PC so long as > it is directly connected to my DSL modem. Hence, we have to assume that the > Router (the WebRamp) is at fault, right? --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
