At 02:44 PM 3/9/02 -0800, Doug Sampson wrote:
>Hi all,
>
>I'm still having a problem with port forwarding packets to the internal web
>server... I am on a Cox network that supposedly blocks packets coming inward
>via port 80. I've set up an account with DynDNS that forwards packets
>directed at http://www.cybersampson.com to http://www2.cybersampson.com:8080.
>I am getting an error message that essentially says "connection request
>refused".
I would be happier knowing what it says rather than what it "essentially"
says. Also what "it" is (what browser is reporting the error). From here,
Netscape (on Win95) gets the right translated address from DynDNS, but times
out with its standard "The server is not responding ..." message.
>Here is the data for analysis:
Where in the config file are you setting up the port forwarding? If I look
at the section on port forwarding, all I see is a commented-out line to
specify the port-forwarding link:
>#INTERN_SERVERS="tcp_${EXTERN_IP}_8080_192.168.1.200_80"
(You do uncomment the line to identify the internal WWW server, but that
doesn't include any port-8080 information.)
>INTERN_WWW_SERVER=192.168.1.200 # Internal WWW server to make
>available
You might want to check if the port-forwarding rule you desire is actually
in place. I always forget this command, but I think it is --
ipmasqadm mfw -L -n
>Running DCD 1.02 on a system with 2 NICs.
[details deleted]
--
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
