Any FTP & Router Setup Gurus Here?

BBand.
Using: XP_SP1
Router: WGT624 (Netgear.)



I'm trying to setup an occasional FTP. I'm using TYP_FTP as it's
simple and all I need.

However I am going bald over this

I have given the machine a static IP in network preferences:

IN TCP\IP (net connections)
--------------------------------
IP: 192.168.1.100 (PC)
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.2 (ROUTER)
Preferred DNS server: 192.168.1.2 (ROUTER)
-------------------------------

... and in the router I have setup port forwarding:

FTP_01 - 12345 - 12345 - 192.168.1.100 TCP\UDP


The FTP program itself has very few configuration needs.

I assume the IP for passive mode means my WAN IP
address? (I haven't even started to think about opening
ports for that yet..)


I can do localhost to 192.168.1.100:12345 but can not attach to the
FTP if I try looping back to my WAN_IP:12345


GRC.com tells me the port is still stealthed.. which if the setup were
working it should not be.


Am I missing something? Are there extra things I need to do in the
router to get this to work?

Help appreciated.


Pete

Spamblocking

"Pete" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> BBand.
> Using: XP_SP1
> Router: WGT624 (Netgear.)
>
> I'm trying to setup an occasional FTP. I'm using TYP_FTP as it's
> simple and all I need.
>
> However I am going bald over this
>
> I have given the machine a static IP in network preferences:
>
> IN TCP\IP (net connections)
> --------------------------------
> IP: 192.168.1.100 (PC)
> Subnet Mask: 255.255.255.0
> Default Gateway: 192.168.1.2 (ROUTER)
> Preferred DNS server: 192.168.1.2 (ROUTER)
> -------------------------------
>
> .. and in the router I have setup port forwarding:
>
> FTP_01 - 12345 - 12345 - 192.168.1.100 TCP\UDP

Why port 12345? Also, you only need to forward TCP but forwarding UDP as
well won't stop it working.

> The FTP program itself has very few configuration needs.
>
> I assume the IP for passive mode means my WAN IP
> address? (I haven't even started to think about opening
> ports for that yet..)

Yes.

> I can do localhost to 192.168.1.100:12345 but can not attach to the
> FTP if I try looping back to my WAN_IP:12345

It's not usually possible to connect to a "port forwarded" server from
inside the network using the WAN IP address.

> GRC.com tells me the port is still stealthed.. which if the setup were
> working it should not be.
>
> Am I missing something? Are there extra things I need to do in the
> router to get this to work?

Something is apparently dropping the incoming connection requests. This
could be the ISP, the router (blocked by firewall or port forwarding isn't
working for some reason) or the server machine itself.

Alex

On Sat, 16 Jul 2005 22:55:20 +0100, "Alex Fraser" <(E-Mail Removed)>
wrote:

>Why port 12345? Also, you only need to forward TCP but forwarding UDP as
>well won't stop it working.

No reason other than getting it up and running and not disturbing
anything else.. Was going to change it later...

>Something is apparently dropping the incoming connection requests. This
>could be the ISP, the router (blocked by firewall or port forwarding isn't
>working for some reason) or the server machine itself.

Your telling me )

My LAN has stopped working now after messing with TCP\IP also so I
have to fix that ... and it still won't work after reverting the
settings... I'm having a bad network day I think...

I'll be back later after I get my internal machines talking again

Pete

Thanks Alex

I got my FTP program up and running in the end.

In the end i shouldn't have listened to any of the stuff I read on
various 'expert' sites.. It was a simple matter of opening the port
(which I did anyway) and running net start ...

I guess not all the needed wndows services were running.. It's now a
simple job for me to start disabling services again until I locate the
exact ones needed...

But basically in the end I did not have to mess with TCP\IP or
anything else..

Phew.. I almost gave up....

Cheers again.

Pete