remote ftp server
- Thread starter Jabes
- Start date
Jabes
banned
i can look at file in my network just not from a pc outside of the network
I tried this too http://www.grc.com/port_21.htm and wen I probed it, it said that the port was stealth so I think theres sumthing with the router
I tried this too http://www.grc.com/port_21.htm and wen I probed it, it said that the port was stealth so I think theres sumthing with the router
axgrinder73
New Member
Do you know your IP from your ISP? Is that the IP that you use when you try to access it remotely? Do you have a static address assigned to the box running FTP? And you are port forwarding to that address?
Jabes
banned
I think I have the ip address I went to www.whatismyipaddress.com and thats how I found out is that what I need to do and I have a dyndns account setup and thats how I'm making a static IP address
axgrinder73
New Member
You don't need to mess with a dydns right now. Your address (for the box running FTP) needs to be static at your router. You need to set the router to give out addresses in a range for DHCP.
lets use 192.168.1.1 - 192.168.1.200 for example, that way the router will assign IPs to machines in this range leaving the other addresses (192.168.1.201 - 192.168.1,254) for static assignments. This has nothing to do with your IP from your ISP, this is necessary for the port forwarding to work properly.
You will also need to set the network properties on the FTP box to use a static address.
The reason to use DYDNS is for when you have a registered domain name and want to use it with an address (from your ISP) that is DHCP. DYDNS will change when your are issued a new IP from your ISP.
You do realize that once to start running FTP that you will have people constantly trying to hack it?
lets use 192.168.1.1 - 192.168.1.200 for example, that way the router will assign IPs to machines in this range leaving the other addresses (192.168.1.201 - 192.168.1,254) for static assignments. This has nothing to do with your IP from your ISP, this is necessary for the port forwarding to work properly.
You will also need to set the network properties on the FTP box to use a static address.
The reason to use DYDNS is for when you have a registered domain name and want to use it with an address (from your ISP) that is DHCP. DYDNS will change when your are issued a new IP from your ISP.
You do realize that once to start running FTP that you will have people constantly trying to hack it?
massahwahl
VIP Member
How would anyone know he was running an FTP server? And how would they know his IP to connect to it?
Jabes
banned
well I have my ftp box set to static so your saying that I need to make my router static wouldn't that make it so that all my pcs on that router are static?
and its going to be running linux so it won't be as hackable as a pc right?
axgrinder73
New Member
Ever hear of a port scanner? Mine was up for three day before people started trying to get in. Luckily, no one got in, but I blocked all of the IPs that were trying to gain unauthorized access (that's a pretty long list). Almost all of the IPs were coming from proxy servers from Asia, so there was no easy way to find out who was trying to hack me.
Jabes
banned
but isn't linux harder to hack?
axgrinder73
New Member
Your router probably already has a static address (most likely 192.168.1.1). But, does your router see the FTP box? think that most router have to be set up to allow both static and DHCP addresses (via the process I mentioned before).
If your FTP box already has a static address and the router sees it, GREAT! You are on your way. Now, make sure that your port forwarding rules point to that static address.
For example: port 21 forwarded to xxx.xxx.x.xxx (what ever the address of the box is, NOT the address from your ISP)
If this is set right, goto another machine on your network- goto my computer - in the address bar type ftp://xxx.xxx.x.xxx (fill in the x's with the address from your FTP box) and hit enter.
Let us know what happens.
If your FTP box already has a static address and the router sees it, GREAT! You are on your way. Now, make sure that your port forwarding rules point to that static address.
For example: port 21 forwarded to xxx.xxx.x.xxx (what ever the address of the box is, NOT the address from your ISP)
If this is set right, goto another machine on your network- goto my computer - in the address bar type ftp://xxx.xxx.x.xxx (fill in the x's with the address from your FTP box) and hit enter.
Let us know what happens.
massahwahl
VIP Member
How in the world would someone know that you just set up a ftp server?
axgrinder73
New Member
Jabes
banned
by scanning for open ports they find out its just weird
axgrinder73
New Member
People just sit around with port scanners running to scan random IP addresses for open ports. Once they find one they use password cracks to try to get in. That is why a strong password and user name is important.
Like I said, no one was successful, but I take an active roll to keep people out.
Ninja, that is why I recommended Smoothwall for you. It has a feature that would allow you to block all incoming IP's except your brothers.
massahwahl
VIP Member
axgrinder73
New Member
I can get in from another pc on the network just not from a pc outside of my network so thats why I came here
Then you have an issue with your port forwarding rule OR your ISP blocks incoming port 21.
Double check your port forwarding rules on your router.
Did you scan yourself for open ports at GRC.com?
axgrinder73
New Member
No that should work. Do a "sheilds up" scan at grc.com to see if those ports are open. Let us know waht you find out.