Frequent Visitor
•
6 Messages
Internally hosted ftp server via iis
I have recently upgraded my xfinity internet to unlimited gig speeds. I have always used my own router do to the fact that I run a rather complicated network. I use a windows server 2019 domain controller and connect all other computers to my domain. I run an ftp server through the iis 10 role from the domain controller. I statically adding the internal ip address to that domain controller. Within my router all I would do is forward port 21 to that ip address of the DC. For external connection I also use a NoIp free dns domain. On the DC I use NoIp's dac agent that simply checks and associates the external IP with my domain name. Since going to the upgraded service with xfinity I elected to go with their xfi gateway. I like the ability to control the internet usage for my kids and my old modem wasn't able to handle gig speeds. Also it actually saved me 5 bucks a month with the unlimited plan. So now with the new gateway and the ports forwarding to the simian controller I'm having weird connection issues with my ftp server. Internally the ftp server works fine and I connect with no issues. Externally however it seems to get stopped after it relays to the external address. I have disabled the advanced security but I'm still unable to connect via filezilla from outside my network. Intrsting enough using a n ftp client from my phone I can get a connection to work from outside if I set the connection to active and not passive. But when doing that the connection does not work if I'm connected to my wifi (internal). Reading that the way port forwarding works in this xfi gateway it does not forward to the static ip address however uses the dhcp record and the Mac if the computers nic. Not sure if that's an issue bit I think not because if I put my Domain controller pc in the dmz it seems to work so that leads me to the fact that I may need another port range open and forwarded to that computer but I've not been able to find what works. Something that was simple before is proving to be a big pain now. I do want to keep using this gateway so I'd love to figure this out! Any help would be appreciated!
Responses
jlavaseur
Valued Contributor
•
409 Messages
7 m ago
I experienced the same thing before, I didn't use any fancy ip thing because my ip would stay the same for a year or more, anyway when I was connected behind the router I always had to use the internal ip to access my server, when I wasn't behind it I would use the external ip or domain and it would work fine with port forwarding, I am not sure why it was like that, dmz will expose that computer to the world, so a separate firewall is recommended
0
0
gec5741
Frequent Visitor
•
6 Messages
7 m ago
Yeah I've setup my FTP server before. I had to rebuild my DC so was going about it again and this time around it was more involved than it has been in the past. I know when outside your network you need to use your external IP and forward the apropriate prts/ports the internal address of the ftp server. But i've never had issues with ports. It was strange and hard to explain but the client i use on my phone after opening a range of ports seemed to fix the issue for my phone client. However thorugh an external pc and filezilla i'd connect but fail to get a directory listing. After looking at the firewall setting within IIS 10 there is a spot to enter in your external IP. Once I did that wahla I was able to connect remotely just fine. I may remove that port range that I forwarded and see if that's even needed. I just don't recall ever needing to do that.
0