3rd-Party FTP Server?

On 01 Apr 2015, "(PeteCresswell)" wrote in
alt.windows7.general:

But it seems pretty clear that I am doing *something* wrong... and
my gut says it's something really, really basic - as in totally
misunderstanding something.

It's possible, though not probably, that your ISP is blocking the
standard FTP port (21). You can change it to any unused port in
Filezilla Server's General Settings. I use 2121. When connecting, you
must indicate the port in your client.

You might also find that after connecting, you have trouble getting a
directory listing. It may help to tell your server to use Passive
(PASV) mode (see "Passive Mode Settings"). This requires the use of
more ports - I use the range 3000 - 3100. You will have to open this
range in your firewall as well as the main port 2121. You'll need to
set you client to use PASV mode, too.

Don't forget to forward the ports in your NAT router to the FTP server
machine.

You should now be able to connect from outside using your main IP
number. If you have a DNS listing (I use the free service from
NoIP.com) you will be able to connect by name rather than IP.

Per Stormin' Norman:
Have you tried connecting to your FTP server directly from the command line?

See:
https://support.godaddy.com/help/art...dows-or-macosx

C:\ftp 10.0.0.10:99
Unknown host 10.0.0.10:99.
ftp dir
Not connected.
ftp bye
C:\

C:\ftp 127.0.0.1:99
Unknown host 127.0.0.1:99.
ftp bye
C:\


Have you tried using a FTP client such as FileZilla client or FireFTP for
Firefox?

That's the next step.
--
Pete Cresswell

Per Stormin' Norman:
AND..... have you tried setting up and connecting via port 21 instead of 99?

Yes. Started out with Port 99 just on the assumption that Port 21
would be anybody and everybody's snooping target.

But now I am about to go back to the default 21 before trying the client
- just to minimize the number of variables.
--
Pete Cresswell

Per Stormin' Norman:
AND..... have you tried setting up and connecting via port 21 instead of 99?

Here's what the client says: http://tinyurl.com/lz7uvvc

"Status: Connecting to 10.0.0.1:21...
Status: Connection attempt failed with "ECONNREFUSED - Connection
refused by server".
Error: Could not connect to server
Status: Waiting to retry..."

Well, at least I'm back to "Refused"... even with Windows Firewall on...
which seems to me to indicate that the firewall settings are at least
partially right.

Going back to my theory that it's something simple, stupid, and basic I
have to wonder if I have found some way to mess up the ID/PW thing.

- I am careful to keep the same case with both ID and PW...

- I carved the PW down to just one character "x" to eliminate
mis-typing as a possibility.


But I'm still thinking "simple, stupid, and basic"...
--
Pete Cresswell

(PeteCresswell) wrote:

I tried setting up Windows 7's, but no luck... can't even see the
service.

So I went to FileZilla where I am in the process of getting my pasty
white butt kicked.

The Question:

Can anybody recommend another FTP server - something that even a total
idiot can set up ?

By the way, is this FTP server only to be accessible within your
intranet or will you be letting outsiders through your firewall to
connect to it? If you make it publicly accessible from the Internet
then you'll also have to consider how to secure your network and your
other intranet hosts.

If this will be publicly accessible, do you really want to use an
internal FTP server? Why not something like Dropbox (2GB free),
OneDrive (7GB free, upped with reputation), or Google Drive (15GB free)
where you can choose what to share with others, file management is easy,
and someone else has to worry about security and penetration?

Are the files sensitive in that they contain data you must not let
anyone see except to whom you give permission? Well, an FTP server can
require login credentials but those could get shared without your
knowledge. I have used (not run) FTP servers where the owner doles out
a temporary login that survives for either a few days or a fixed number
of logins. Filezilla's documentation is unusually sparse
(https://wiki.filezilla-project.org/Documentation) to know what methods
of authentication they support and what management it provides on
logins. Folks in the Filezilla forums might know if there is something
beyond login credentials that will let you define how long or how many
times someone has access. With the online storage providers above, you
can decide who gets to share which folder but it's pretty much make you
do the manual login management, too; i.e., you'll have to decide when to
yank the sharing.

Do you have a static IP address from your ISP? If not, and if the FTP
server will be accessible via the Internet, you'll have to consider DDNS
(dynamic DNS) to provide a hostname (their loaner or one you register)
at a DDNS service that will dole out the IP address to you (well, to the
WAN-side of your router where you have to punch a hole in its firewall
to redirect to your intranet host running the FTP server). When you get
a DDNS account, you'll also need to run a DNS updater client on the FTP
host to keep your DDNS account updated with the current IP address
allocated by your ISP to the WAN-side of your router (the client
connects to them, they see the IP address for your connection [of your
router], the client logins into your account, and they record the IP
address of the connection into your DDNS account). Some DDNS providers
have free accounts but with limitations, plus often they require that
you periodically login to keep your free account alive. Some routers
support a couple DDNS providers but be warned that such routers often
login into the DDNS account only when their WAN-side IP address changes;
i.e., after the old IP binding expires, the binding is cut (the router
is powered down or reset), and a new IP binding is retrieved from your
ISP's DHCP server. That rebinding could occur longer after the free
account expiration period so you would lose your free account. For free
accounts or for DDNS providers not supported in the router, you need a
DNS updater client running on some intranet host to get your DDNS
account updated with your current IP address of your router.
Dynamically assigned IP address, the typical type from an ISP, can and
will change plus users really don't like using IP addresses and prefer
hostnames.

There's lots to think about if you're going to provide a publicly
accessible FTP server even if you use login credentials to regulate who
can connect. What will users use to find your FTP server? A hostname
or an IP address? If an IP address, is yours static rather than
dynamic? Will your router let you punch a hole in its firewall to
define redirection of connects on a particular port to send the
externally-sourced connection requests to your host with the FTP server?
How are you going to secure that intranet host against penetration? How
will you secure your intranet? How will you defend against DDOS attacks
at the router? The FTP server lets you define login credentials but
does it provide multiple credentials so you can assign different ones to
different users (so, for example, yanking access from one abusive user
doesn't mean yanking access from everyone else until you provide all but
the abusive user with new login credentials)?

Is the FTP server to be accessed you only? Then the login credentials
are easy to maintain; however, if you're going to be somewhere outside
your intranet to access the FTP server, you still have to consider DDNS
so you can find your FTP server when outside your intranet, punching a
hole in the router's firewall to redirect incoming connects to your FTP
server host, and securing your FTP server host and your network. You'll
need to use a strong password for your login credentials and probably
change it periodically to prevent hacking.

You open a can of security worms when making any server program on a
local resource accessible to external source (Internet). If all you
want to do is share some files, use online storage services (some are
free but with limited quotas) and let them handle the security issues
and you only need to control who has access to what. If the files
contain sensitive data, encrypt them and provide the password via some
other communications venue, like encrypted e-mails. They send you a
digitally signed e-mail as an invite to allow you to send them encrypted
e-mails, you save the public key therein into your e-mail client, like a
contact record, and then you send them an encrypted e-mail with the
login credentials for their account on your FTP server -- or you hope
your e-mails are sufficiently disconnected from your FTP service that
you can send their FTP login credentials in the clear via non-encrypted
e-mail. If it's just you accessing your FTP server intranet host, you
still have more setup to do (to find and secure it) to access it from
the outside than just installing the FTP server software.

If this FTP server is not for external access by others (i.e., it is not
publicly accessible) and just something you want to use within your own
intranet to store files, why use and FTP server versus, say, a NAS host?
Or use that intranet host where you would install the FTP server program
and instead just use file sharing? Presumably you want to use an FTP
server to allow external access to it via the Internet, and that entails
more than just installing the softwa how to find your FTP host (DDNS)
or getting/paying for a static IP address, router config to redirect
incoming FTP connects to your FTP server host, and securing it all.
Seems using someone else's online file storage service would be easier
to setup.

_Free online storage providers_
OneDrive: 25GB free, 10GB max file size
Google Drive: 15GB free
Dropbox: 2GB free, 2GB max file size
SpiderOak: 2GB free.
aDrive: 50GB free, 2GB/file max (no desktop sync client, web only)
Symform: 10GB free, earn more by sharing your disk space in their cloud

You might think downloading from cloud storage would be slower than
retrieving files from your FTP server but that depends entirely on what
is your upstream bandwidth. It is likely you have asynchronous
bandwidth. What you get for upload bandwidth is far smaller than your
download bandwidth. Downstream might be 20, 30, 50 Mbps but upstream
will only be 2, 5, 8 Mbps. Their big downstream pipe will be choked by
your smaller upstream pip. For example, at 5 Mbps upstream bandwidth
(your end), sharing a 10GB file would take them around 4+ hours to
retrieve. Then consider how many concurrent connections you will allow.
Each concurrent user would share your upstream bandwidth. I did a test
download of a 2.37GB file from my OneDrive account but wasn't going to
wait for it to complete before posting this message. I only wanted to
see the effective download speed which was reported at 1.29 MBps (or
10.3 Mbps). While I have 59 Mbps downstream bandwidth (at the moment),
the site throttles the connection so I got less -- but it still higher
than my upstream bandwidth. At that higher downstream bandwidth from
the storage site, it would take about 2 hours to download a 10GB file.
The download is faster because my effective downstream bandwidth from
the site is much greater than my upstream bandwidth (to other users
connecting to a server on my end).

If you still go with an FTP server, and if you need DDNS to find your
router (which then redirects to your FTP server host), I've used DynDNS
(http://dyn.com/remote-access/). It was previously easy to get a free
account but they don't do it openly anymore. As I recall, you now have
to open a trial account and then cancel it before its trial expires.
Then they give you a limited free account in appreciation for trialing
their service. The free account lets you define only up to 2 endpoints:
2 hostnames for DNS lookup that doles out the IP address for 2 of your
hosts/routers. Some routers support DynDNS in their config but, as
noted, they may not update your DDNS account soon enough to avoid idle
expiration (I think DynDNS requires logins 28 days, or sooner, but
consider it abuse it you update too often - so get their DNS updater
client to update often enough but not too often to keep alive a free
account). You can register a domain and bring it to them to use their
DNS service to find your host/router, or use one of their loaner domains
(e.g., yourhost.dyndns.com. There are other DDNS providers, like
No-IP.com. As I recall, there is a limit in the free account on the
number of DNS lookups they will permit per day but it's so high that I
don't concern myself about it.

On Wed, 01 Apr 2015 16:06:11 -0400, (PeteCresswell) wrote:

Yes on both - assuming that clicking the 2 "Turn off WIndows Firewall
(not recommended)" buttons in the Windows FireWall UI is sufficient to
actually turn it off 100% and that my IE syntax is correct:
:99
makes IE throw "This page can't be displayed."

Firefox throws "Unable to connect"... which is a *little* friendlier
IMHO.

Isn't it ftp://usernameassword@site and presumably you have set up
your server to listen on port 99?

If you want me to try to connect from outside to you send me a private
email with temporary connection details. I have CFS/ME so sleep a lot
:-)


--
Faster, cheaper, quieter than HS2
and built in 5 years;
UKUltraspeed http://www.500kmh.com/

In article , lid,
(PeteCresswell) says...

Per Stormin' Norman:
AND..... have you tried setting up and connecting via port 21 instead of 99?

Here's what the client says: http://tinyurl.com/lz7uvvc

"Status: Connecting to 10.0.0.1:21...
Status: Connection attempt failed with "ECONNREFUSED - Connection
refused by server".
Error: Could not connect to server
Status: Waiting to retry..."

Well, at least I'm back to "Refused"... even with Windows Firewall on...
which seems to me to indicate that the firewall settings are at least
partially right.

Going back to my theory that it's something simple, stupid, and basic I
have to wonder if I have found some way to mess up the ID/PW thing.

- I am careful to keep the same case with both ID and PW...

- I carved the PW down to just one character "x" to eliminate
mis-typing as a possibility.


But I'm still thinking "simple, stupid, and basic"...

It could be working. You really need to test from outside your local
network (I *still* can't do that myself - connect from inside my
network). That said, I know it's my server firewall software - but we
won't go there.
So get a mate to test - from the "real" outside.

--
Duncan.

On Wed, 01 Apr 2015 16:06:11 -0400, "(PeteCresswell)" wrote:

Per Stormin' Norman:
Have you tried, as a test, completely disabling the firewall to see if that
makes a difference?

Have you tried accessing the FTP server from your local network (another machine
behind the router)?

Yes on both - assuming that clicking the 2 "Turn off WIndows Firewall
(not recommended)" buttons in the Windows FireWall UI is sufficient to
actually turn it off 100% and that my IE syntax is correct:
:99
makes IE throw "This page can't be displayed."

Firefox throws "Unable to connect"... which is a *little* friendlier
IMHO.


Have you setup users with authentication in the FTP server? Are you testing
access to the FTP server with the proper credentials?

I *think* so. Viz: http://tinyurl.com/p49lhtd

But it seems pretty clear that I am doing *something* wrong... and my
gut says it's something really, really basic - as in totally
misunderstanding something.

I just downloaded and installed FileZilla Server to see for myself what
might be going on. Standard install, next, next, next.

Note that there are two ports to be concerned with - the port for the admin
interface (in case you want to be able to do remote admin) and the port for
the FTP server itself. I ignored the former and set the latter to 2121. Next
I created a user and gave him a password and a home directory. Finally, from
another PC on the LAN I tried to connect to the new FTP server...and failed.
I forgot to open the firewall on the PC that hosts the FTP server. Once I
did that, I could connect and browse around, transferring files at will.

As others have said, I would definitely get local access working before
tackling the WAN access portion, but once local access does work, you know
it's just a matter of forwarding port 2121 (or whatever you chose) plus a
port range that you configured in FZS.

--

Char Jackson

On 01 Apr 2015, "(PeteCresswell)" wrote in
alt.windows7.general:


C:\ftp 10.0.0.10:99
Unknown host 10.0.0.10:99.
ftp dir
Not connected.
ftp bye
C:\

C:\ftp 127.0.0.1:99
Unknown host 127.0.0.1:99.
ftp bye
C:\

Windows own FTP client is really stupid. For one thing, it won't parse
addresses with port numbers. At least, the XP and earlier version
wouldn't. I don't have access to my Win7 system to check that.

Per Stormin' Norman:
Are you doing this all from the same machine? By any chance is the machine
multi-homed (more than one physical adapter or more than one IP address)?

I am curious, what do you have set up for your subnet mask? 255.255.255.0 will
provide you with up to 254 hosts.

Same machine. As soon as I finish typing this, I will try from another.

The rest is way above my pay grade but, assuming you mean the subnet
mask on this machine, here is what I show:
------------------------------------------------------------------------------
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Batipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Giga2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-0A-B4-EE-A0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection
I217-V
Physical Address. . . . . . . . . : 94-DE-80-A0-CC-52
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::8cbe:8194:3dc6:8af5%11(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, March 30, 2015 7:43:38 PM
Lease Expires . . . . . . . . . . : Monday, April 06, 2015 7:43:38 PM
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 244637312
DHCPv6 Client DUID. . . . . . . . :
00-01-00-01-1A-0D-F7-35-94-DE-80-A0-CC-52

DNS Servers . . . . . . . . . . . : 216.146.35.35
216.146.36.36
10.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet
Adapter
Physical Address. . . . . . . . . : 08-00-27-00-0C-7A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::e5e4:9a05:fd23:2b57%15(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 336068647
DHCPv6 Client DUID. . . . . . . . :
00-01-00-01-1A-0D-F7-35-94-DE-80-A0-CC-52

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{4AB1E5C0-E084-484A-904C-05243ADA5E3D}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{D83C0A7E-F91B-4BD4-BB90-22695033123A}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{0AB4EEA0-DA4C-4FA4-B275-00554013918F}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Bat
------------------------------------------------------------------------------
--
Pete Cresswell

Per Stormin' Norman:
Are you doing this all from the same machine?

Just tried it form two other machines: one on the same LAN using the
local numeric IP addr, the other on a remote machine using my domain
name.
--
Pete Cresswell

Per VanguardLH:
By the way, is this FTP server only to be accessible within your
intranet or will you be letting outsiders through your firewall to
connect to it? If you make it publicly accessible from the Internet
then you'll also have to consider how to secure your network and your
other intranet hosts.

If this will be publicly accessible, do you really want to use an
internal FTP server? Why not something like Dropbox (2GB free),
OneDrive (7GB free, upped with reputation), or Google Drive (15GB free)
where you can choose what to share with others, file management is easy,
and someone else has to worry about security and penetration?

Without going on-and-on about something I have only the vaguest
understanding of, here's the scenario - total use of FileZilla for Yours
Truly:

- I am setting up an IP cam/server at another house besides this one.
(A house at the shore? .... Maybe in my dreams... actually it's
a close family member's house just a few miles away)

- That cam server, local to the house, will be recording Alert images
and video clips in response to motion detection - and emailing
and/or texting low-rez copies of the Alert images to the homeowner's
cell phone - at least until he realizes that the false alerts are
more trouble than the whole thing is worth -)

- The cam server there has the capability to FTP Alert images and
video Clips to another location across the WAN. That's me....
The idea is that, in case of a destructive break-in/theft scenario
the alerts & clips just *might* have had time to upload to my 24-7 box
before the perpetrators find and grab the server.

Wasn't my idea.... but it seems like an opportunity to explore the
capabilities of that server software (which I use at home and at
a remote site) and the real-world limitations of said strategy.
--
Pete Cresswell

(PeteCresswell) wrote:

Per VanguardLH:
By the way, is this FTP server only to be accessible within your
intranet or will you be letting outsiders through your firewall to
connect to it? If you make it publicly accessible from the Internet
then you'll also have to consider how to secure your network and your
other intranet hosts.

If this will be publicly accessible, do you really want to use an
internal FTP server? Why not something like Dropbox (2GB free),
OneDrive (7GB free, upped with reputation), or Google Drive (15GB free)
where you can choose what to share with others, file management is easy,
and someone else has to worry about security and penetration?

Without going on-and-on about something I have only the vaguest
understanding of, here's the scenario - total use of FileZilla for Yours
Truly:

- I am setting up an IP cam/server at another house besides this one.
(A house at the shore? .... Maybe in my dreams... actually it's
a close family member's house just a few miles away)

- That cam server, local to the house, will be recording Alert images
and video clips in response to motion detection - and emailing
and/or texting low-rez copies of the Alert images to the homeowner's
cell phone - at least until he realizes that the false alerts are
more trouble than the whole thing is worth -)

- The cam server there has the capability to FTP Alert images and
video Clips to another location across the WAN. That's me....
The idea is that, in case of a destructive break-in/theft scenario
the alerts & clips just *might* have had time to upload to my 24-7 box
before the perpetrators find and grab the server.

Wasn't my idea.... but it seems like an opportunity to explore the
capabilities of that server software (which I use at home and at
a remote site) and the real-world limitations of said strategy.

Too bad the cam software won't save images to files under a folder.
Then you could specify that folder gets synced with online storage
(OneDrive, Google Drive, Dropbox, etc) using their local client. All
you have to do is install their sync client and specify which folders
get synced up to the server.

Since the cam software only does FTP, yep, looks like you'll have to
setup an FTP server. A local FTP server (one inside your intranet)
eliminates any networking problems getting across the Internet to
transfer the images to an external FTP server. You would use your
strong login credentials to access the FTP server that is local to the
cam's intranet.

You would still have to be able to login from your host to that FTP
server host. Does the intended FTP server host have a statically or
dynamically assigned IP address? If dynamic then you'll have to add
DDNS unless somehow you're going to be kept informed of the WAN-side IP
address of the router (which can change due to rebinding) of where is
the cam and the FTP server.

You'll also need redirection setup in the router for when connect
requests come to the router on port 21. The router gets the external
connection to its port 21 (to accept commands to the FTP server) and has
to know to which LAN-side (intranet) host to forward that connection. I
think port 20 traffic would be outbound from the FTP server so you don't
need to punch a hole for it in the router's firewall.

Since ports are being bypassed (opened) in the router's firewall, there
are security issues. If the FTP server is configured for a max
connection count of 1 (just for you), if strong login credentials are
used for the FTP server authentication, and if the FTP server host is
secure, like isolating it in a DMZ, then the person at that end is
probably okay regarding breaches. You could add FTPS (secure FTP) to
further strengthen security, like protecting the login credentials. In
that case, you would punch a hole and redirectn on port 990 connects
through the router's firewall. However, any hacker polling ports to
find those that answer (the listener on the port acknowledges) can DDOS
that IP address or attempt vulnerability access. They found something
listening there.

Having the cam software save image files to a folder on the local HDD
and using a sync client to copy those files to online storage would be a
lot less hassle to the customer. FTP requires installing the FTP server
software, managing authentication, reconfiguring the router, setting up
DDNS, and probably other little gotchas. Using FTP versus a sync client
to online storage is like using UltaVNC (or another VNC variant to gain
remote access to a host rather than use TeamViewer, LogMeIn, or mikogo.
Is this customer capable of managing all this server, router, and DDNS
setup when you are no longer in the picture?

While the cam software has an FTP feature, you sure it didn't also come
with online file storage services so it could send its pics there or
store them locally and get them synced to a server?

On Wed, 01 Apr 2015 21:49:05 -0400, "(PeteCresswell)" wrote:

Per Stormin' Norman:
Are you doing this all from the same machine?

Just tried it form two other machines: one on the same LAN using the
local numeric IP addr, the other on a remote machine using my domain
name.

Make sure you're trying to access the FTP server port and not the admin
interface port. They are different and not interchangeable.

Pretty obvious, but considering that it took me less than 2 minutes to
install it and get it working here it's probably safe to assume that you
missed something 'obvious'. Apologies if that's not the case.

Also, contrary to what I think I read in this thread earlier, the FTP server
*does* work from the machine on which it's installed.

In a web browser on the PC where the FTP server is installed, enter
"ftp://127.0.0.1/" and you should get a login box where you'll enter your
username and password, or type "ftp 127.0.0.1" from a Command Prompt. BTW, I
changed the FTP port to 21 for this test since Windows seems to have trouble
using a non-standard port when working from a Command Prompt. Telnet works,
but not FTP. Yes, you can Telnet to an FTP server, just like you can Telnet
to a web server, etc. If you use Telnet, your login commands a
user myusername
pass mypassword
help -- to get a list of available commands


--

Char Jackson

Per Stormin' Norman:

I see you have a virtualbox machine installed. By any chance, did you install
the FTP server in the VM? I know, it sounds like a stupid question, but it is
worth asking.

Believe-it-or-not, I was just checking Windows Firewall | Allow programs
to communicate... | Allowed programs.... just to make double sure
FileZilla was covered and I saw an entry for "FTP Server" without the
leftmost box checked and neither "Home.." nor "Public" boxes checked.

Checked all 3, exited Windows Firewall, went back in to confirm that it
"Took", and then tried connecting again via FileZilla Client - but no
luck: same-old-same-old "Connection attempt failed with 'ECONNREFUSED -
Connection refused by server'".


IIRC the virtualbox machine is from my install of a disk imaging app
called "ShadowProect".
--
Pete Cresswell