Re: I cannot get my damn FTP server to work? Really frustrating.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"Ed" <Ed@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:u0kn1w4HGHA.1192@xxxxxxxxxxxxxxxxxxxxxxx
>> No, I am not connecting from an outside machine. I am using
>> http://www.web2ftp.com/ for my testing purposes.
>> If I try and ftp using the internal router address (192.168.1.100), it
>> works fine. If I try using the outside ip address, it gives me an error.
>
> That is expected and is the way it is. If I understand your post, here's
> how your network is setup:
>
> 1) PC1 = 192.168.1.101
> 2) PC2, which is the IIS/FTP server = 192.168.1.100
>
> Your router is anywhere in the 192.168.1.x range, just not .100 nor .101
> (likely 192.168.1.1).
>
> If you ftp from PC1 (.101) to PC2 (.100), and it works, then yes, your
> FTP is setup properly.
>
> When you created a port forwarding entry in your router, it had *nothing*
> to do with your internal setup. What you did was allow *anyone* outside of
> your internal network (anyone on the internet) to access your ftp server.
> In other words, just as an example, I can access your ftp server if I knew
> what your external/public IP is. Your external IP is the one your ISP
> assigns to your router, and in your example, is the 69.x.x.x address.
>
> Without getting into networking concept/details:
>
> - you **cannot** test your ftp from your internal PC (192.x.x.x) by going
> to the 69.x.x.x address. It will not work, nor should it.
>
> - your *only* choice for ftp **within your internal network** is to
> connect via the *internal* IP address of your IIS/FTP (192.168.1.100),
> unless you have some name resolution setup installed (dns, static hosts
> files, etc.) so that you can use names like your example of
> "www.web2ftp.com" (internally, netbios will also work).
>
> - if you want to test your router port forwarding setup, then you have to
> do so from **outside** - not from any 192.168.1.x address. This means that
> you are testing OUTSIDE access to your internal FTP server, *NOT* testing
> whether your internal PCs can connect with each other successfully.
>
> The above are general "rules"/concepts for your type of use - in other
> words, in larger, more complex networks (ex. multiple internal routers) my
> comments don't apply.
> --
> Cheers,
> Ed
>
>
> "David Mills" <davidmillsjd@xxxxxxxxx> wrote in message
> news:nLednexIJf4Ork7enZ2dnUVZ_vydnZ2d@xxxxxxxxxxxxxxx
>> "Ed" <Ed@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:OX27JlxHGHA.916@xxxxxxxxxxxxxxxxxxxxxxx
>>> Are you connecting from an external machine to test your configuration?
>>>
>>> Or are you attempting to ftp from PC1 (192.168.1.101) to your IIS/FTP PC
>>> (192.168.1.100)? If this is the case, then you don't have to go through
>>> your router at all. You just FTP to 192.168.1.100 from PC1. If this
>>> works then you're good to go. Otherwise, your FTP server is configured
>>> incorrectly. This is likewise your first step to identify the issue (try
>>> internally first).
>>>
>>> In your setup, port forwarding on routers is *only* for allowing
>>> ***outside*** machines to connect to your **internal** machine (either
>>> PC1 or PC2).
>>> --
>>> Cheers,
>>> Ed
>>>
>>
>> No, I am not connecting from an outside machine. I am using
>> http://www.web2ftp.com/ for my testing purposes.
>> If I try and ftp using the internal router address (192.168.1.100), it
>> works fine. If I try using the outside ip address, it gives me an error.
>>
>
>

You are right about how I have everything setup and how it is working. (or
not working) :)


.

Relevant Pages

  • Re: FTP Server behind firewall
    ... I don't think it's the router because all unsolicited packets would be ... The FTP server says it is listening on the internal IP address but I can't ... >> When I try to connect to my FTP server, using the Internet IP address ...
    (comp.security.firewalls)
  • Re: question about nat
    ... to a private address of an internal Ftp server. ... default gateway (another router) and ftp requests don't get a response. ... If the NAT'ing router is accepting traffic from the internet as a whole ...
    (comp.dcom.sys.cisco)
  • Re: I cannot get my damn FTP server to work? Really frustrating.
    ... you don't need to setup router port forwarding just to FTP ... >> of your internal network (anyone on the internet) to access your ftp ...
    (microsoft.public.inetserver.iis.ftp)
  • Re: I cannot get my damn FTP server to work? Really frustrating.
    ... is setup properly. ... When you created a port forwarding entry in your router, ... internal network (anyone on the internet) to access your ftp server. ...
    (microsoft.public.inetserver.iis.ftp)
  • RE: Client Computers cannot upload or download from Remote FTP ser
    ... SBS External NIC - Cannot FTP From this server ... SBS Internal NIC ... FTP server is Checked in Routing and Remote Access - Internet Connection - ...
    (microsoft.public.windows.server.sbs)