FTP server

[Bloodstein]

I'm currently using no-ip (http://www.no-ip.com) to provide a domain name for my dynamic ip...i've got a pc running an ftp server (guildftp) behind a router.

My problem is that I am able to login to the ftp server if i use the loopback ip (ie. 127.0.0.1) or the local ip (ie. 192.168.1.x)....but not so if I'm using the no-ip domain name....or even if I use the real ip (assigned by isp). I don't think it's a problem with the ftp server itself (thought it might be set to block certain ip addresses or something....gotta check on that). It's also able to recognise the ftp server if i use no-ip...juz not able to log on to it. It'z juz....weird....any help, anyone?

 

[JackMDS]

If you have a Cable/DSL Router, and or Software Firewall you have to open port 21.

 

[AFB]

Are you forwarding the port in the router?

 

[Bloodstein]

If you have a Cable/DSL Router, and or Software Firewall you have to open port 21.

i have an adsl router....ok, i'll check to see if port 21 is opened.....but it isn't a firewall though....why would it close ports?

Are you forwarding the port in the router?

errrm.....darn! not enuf networking knowledge...wat's "forwarding the port" and where could you generally find this option on the router configuration?

 

[JackMDS]

Link to: Cable/DSL Routers - NAT & Ports.

 

[JackMDS]

Link to: Cable/DSL Routers - NAT & Ports.

 

[AFB]

You have to forward the ports, or the router will just block it. :Q

 

[Bloodstein]

Able to set up a "virtual server" on the router....but what'z the difference between public and private port no'z? fot ftp aren't both of them 21?

 

[AFB]

Yes, in your case, both are 21. A private port is the port on the private LAN side. A public port is the port on the Internet side.

 

[Bloodstein]

Ahh...having done all that, it now completely fails to even detect the ftp server...

I think I see what was happening before. I think my router acts as an ftp server....which was why the ftp server was recognised....but I'm not able to log in from the outside. All the while I was thinking that I was able to see the ftp server which I set up....only not able to log on to it.

However, I guess progress has been made (though it lookz like a step back ) in that....with the virtual server set up, I don't see the ftp server. This is my setting for the mapped port:

ID Public Port Private Port Host IP Address
8 21 21 192.168.1.20

It might have to do with the Host IP Address. Previously, I had DHCP enabled on the ftp server machine. Well, DHCP is still turned on the router, but I specified 192.168.1.20 as the IP address of host machine, 255.255.255.0 subnet mask and the router IP as the gateway....all the standard stuff. Just hoping these information might help in figuring out why my ftp server is failing from the outside.

 

[kamper]

Why did you stop using dhcp on your machine? And your router will not act as an ftp server, it will forward requests using any protocol on a port you specify to any port on any internal machine that you specify.
What about port 20? Doesn't that have something to do with ftp as well? Something about passive and active connections, dunno, it's been a while since I read about it. Someone who knows more can explain why I'm wrong

 

[AFB]

Try ports 20-22