Getting port forwarding to work, Netgear DG834G

Folks

This is vexing me. Nay, it is verily driving me up the wall.

I'm a Wanadoo broadband user, been with them for 2 years and no
problems to date. My setup is a Netgear DG834G router with a variety
of laptop/desktop, Win XP SP1 home, Win 2K and Win ME clients,
connected via Ethernet and 802.11b/g with WEP enabled. All is working
fine with the clients using DHCP or are fixed IP's.

Rather than paying a fortune for web hosting my plan is to use my
Desktop Win XP SP1 home system as a combined Web/DNS/mail and FTP
server purely for friends and family. To this end I have installed
Apache 2.0 on the box and configured it for name based hosting (using
the virtualhost directive). This works like a dream from the local
LAN.

Now, as Wanadoo use DHCP and muck around with DNS, forward and reverse
queries are not consistent for broadband users, I configured the
router to use its dynamic DNS utility. Specifically, I have the domain
thed.dnsalias.com setup. The router tells me this is being updated and
it is consistent with my current IP. So, I then configured port
forwarding for port 8000 on the router. It forwards to 192.168.2.14,
the fixed IP of the machine I'm typing on.

Any attempt to connect to http://thed.dnsalias.com:8000 or any other
URL I have configured results in a 'connection refused' error in the
browser. I've tried IE and Firefox.

Sniffing this with Ethereal I can see the client sending a SYN to the
routers WAN i/f on port 8000. The router immediately sends me a RST.
Anyone got any ideas why this is happening. As best I can tell the
router is configured properly but obviously something is unhappy. The
router firmware is the current version, 1.04.01.

TIA
--
While the Hobbits may be proud of spreading the "art" of smoking
pipe-weed, I would imagine that nowadays the Shire might be the seen of many
a class action lawsuit.Aaron Clausen on news://alt.fan.tolkien

On Mon, 14 Jun 2004 07:47:23 +0100, Dave Barlow
<(E-Mail Removed)> wrote:

>Folks

<snip>

>Sniffing this with Ethereal I can see the client sending a SYN to the
>routers WAN i/f on port 8000. The router immediately sends me a RST.
>Anyone got any ideas why this is happening. As best I can tell the
>router is configured properly but obviously something is unhappy. The
>router firmware is the current version, 1.04.01.

HTTP/1.1 200 OKDate: Mon, 14 Jun 2004 15:46:04 GMTServer: Apache/2.0.47 (Win32)Last-Modified: Sat, 06 Sep 2003 11:45:21 GMTETag: "d1bf-806-c080c4c6"Accept-Ranges: bytesContent-Length: 2054Connection: closeContent-Type: text/html; charset=ISO-8859-1
........


Looks fine from out here - you wouldn't be trying to access this from
your own lan, would you now?

Derek
--
"I sense much NT in you. NT leads to Blue Screen, Blue Screen leads to
downtime, downtime leads to suffering. NT is the path to the Dark Side."
-- Ellsworth, one small voice

In article <(E-Mail Removed)>, "Dave Barlow"
(E-Mail Removed) says...
> Folks
>
> This is vexing me. Nay, it is verily driving me up the wall.
>
> I'm a Wanadoo broadband user, been with them for 2 years and no
> problems to date. My setup is a Netgear DG834G router with a variety
> of laptop/desktop, Win XP SP1 home, Win 2K and Win ME clients,
> connected via Ethernet and 802.11b/g with WEP enabled. All is working
> fine with the clients using DHCP or are fixed IP's.
>
> Rather than paying a fortune for web hosting my plan is to use my
> Desktop Win XP SP1 home system as a combined Web/DNS/mail and FTP
> server purely for friends and family. To this end I have installed
> Apache 2.0 on the box and configured it for name based hosting (using
> the virtualhost directive). This works like a dream from the local
> LAN.
>
> Now, as Wanadoo use DHCP and muck around with DNS, forward and reverse
> queries are not consistent for broadband users, I configured the
> router to use its dynamic DNS utility. Specifically, I have the domain
> thed.dnsalias.com setup. The router tells me this is being updated and
> it is consistent with my current IP. So, I then configured port
> forwarding for port 8000 on the router. It forwards to 192.168.2.14,
> the fixed IP of the machine I'm typing on.
>
> Any attempt to connect to http://thed.dnsalias.com:8000 or any other
> URL I have configured results in a 'connection refused' error in the
> browser. I've tried IE and Firefox.
>
> Sniffing this with Ethereal I can see the client sending a SYN to the
> routers WAN i/f on port 8000. The router immediately sends me a RST.
> Anyone got any ideas why this is happening. As best I can tell the
> router is configured properly but obviously something is unhappy. The
> router firmware is the current version, 1.04.01.
>
Works fine from here - try accessing it via an external proxy.

On Mon, 14 Jun 2004 16:40:28 +0100, Derek <(E-Mail Removed)>
wrote:

Hmm ...

Smacks forehead, and roundly slaps Agent ...

>HTTP/1.1 200 OK
>Date: Mon, 14 Jun 2004 15:46:04 GMT
>Server: Apache/2.0.47 (Win32)
>Last-Modified: Sat, 06 Sep 2003 11:45:21 GMT
>ETag: "d1bf-806-c080c4c6"
>Accept-Ranges: bytes
>Content-Length: 2054
>Connection: close
>Content-Type: text/html; charset=ISO-8859-1
>.......

Derek
--
A computer lets you make more mistakes faster than any other invention, with
the possible exceptions of handguns and tequila.
- Mitch Ratcliffe

During a perfect moment of peace at Mon, 14 Jun 2004 16:40:28 +0100,
Derek <(E-Mail Removed)> interrupted with:

>Looks fine from out here - you wouldn't be trying to access this from
>your own lan, would you now?

Welllll, errr, shuffles feet and looks sheepish. But friends of ours
could not connect to the URL either. Even got the same errors.

I'll try again with better test subjects.

Dave "I hate it when that happens" Barlow
--
While the Hobbits may be proud of spreading the "art" of smoking
pipe-weed, I would imagine that nowadays the Shire might be the seen of many
a class action lawsuit.Aaron Clausen on news://alt.fan.tolkien

On Mon, 14 Jun 2004 17:13:45 +0100, Rob Morley <(E-Mail Removed)>
wrote:

>Works fine from here - try accessing it via an external proxy.

I got in fine too!

Cheers,

Guy

** I may not be perfect, but I'm
** English, and that's the next best thing!