I tried the settings on the , but after reading all these posts, I was led to believe it is a router problem. However, I don't see any changes at all on the router config panel. All I want is to be able to access these files by ftp -- just like it says on the box. I even bought the setup that was used as an example on the box so it would be easy. But it's not. Please help. Setting up a server can be challenging to the inexperienced, and setting up an ftp server even more so - but it's really not that difficult, once you understand what's required.
To make things easier we are going to do this in two distinctly separate steps, one being to get the ftp server up and running with local access, and the second will be to make it available over the internet - assuming that is a requirement, and by the way, if it is not, then the router has nothing to do with your troubles.
First - for any server - you need to be able to find it - which means an ip address that does not change randomly. Personally I prefer the static address - the DIR, by default, allows addresses in the Next - configure the ftp server itself and test.
I'll pause here for you to complete this first step and tell me where you need help. By the way - who set up the first DNS - the one that got damaged?
Thank you very much for your help. It is much more clear than anything else I've read. I can access via ftp on our network, but no such luck when trying from outside. A student last summer set everything up and I can't track him down. Just my luck. But it worked fine. Thanks again. Looking forward to your next installment. OK - ftp access from the internet is a little more challenging than from across the LAN, but taken one step at a time, it's not too difficult.
As before, the first step is going to be finding the server. This time, it's not going to be as easy as setting a static ip address - at least not for most of us, simply because we don't have the luxury of a static address. There is a possibility that this has already been setup for you by that student - so you need to let me know how you were accessing the old ftp server - if there was a previous DynDNS account it may still be working, depending on how it was being updated - it may have been done from the router which is my preference , but it can also be done on the DNS, so that is some something we might need to look at.
The second step is to "forward" port 21 to your ftp server - a little explanation is in order here. If there was no outgoing connection, when it sees incoming data traffic, it has no idea where to send it, and so it discards it.
For your ftp server to be accessible from the internet, you have to tell the router to forward all incoming traffic on port 21 to the ip address you set on the DNS this is where that link that gunrunnerjohn provided will come in handy. Now - once you have forwarded the port, you need to test access from the internet - it should work at this point, but you need to check it from OUTSIDE of the network to be really certain. More specifically, the big red error message above is popped.
A long message, ultimately asking you to update the share to use SMB2. A bit of searching and turns out Microsoft has already back in urged everyone to stop using SMB1 and finally shut it off from use now. You must enable SMB 1. Why would I need to enable SMB1 server on a Windows 10 machine if you only need to connect, not serve files?
But bear in mind, it is not safe to use SMB1 — two global ransomware outbreaks, WannaCry and Petya, spread quickly because of a vulnerability in Server Message Block version 1.
0コメント