I have setup CoreFTP and it was working (with WinSCP as client) for about a week.
THEN I tried (and failed) to setup RRAS on my server. Ever since then, CoreFTP has not worked externally. I have completed uninstalled RRAS role and feature, but to no avail.
I can use CoreFTP on the server locally by using localhost 127.0.0.1 and my NAT address (192.168.1.31) BUT I cannot use my server's external IP. NOTE: I use no-ip.org for a Dynamic DNS service (since I do not have a static public IP).
Can some one help me here?? Thanks!
Can't use CoreFTP externally - DNS issue?
About my no-ip.org DNS updater...
I cannot even use it to get to CoreFTP on my server itself. That is, when I open WinSCP and input my no-ip.org address, it times out. BUT if I use the server's NAT address (192.168.1.31), it works.
-
- Site Admin
- Posts: 987
- Joined: Mon Mar 24, 2003 4:37 am
[quote="ForumAdmin"]Are you trying your external IP directly?
(get your external ip - coreftp.com/misc/myip.php
If you can't connect via that, then it's some kind of routing issue external to Core FTP Server, or your router needs to port foward port 22 to 192.168.1.31[/quote]
Thank you. I have routed port 22 to my server's IP (192.168.1.31). I can use it's own address (192.168.1.31) in WinSCP and it successfully connects to CoreFTP. However, I cannot use the external IP or the DNS forwarder to the external IP. I know the DNS forwarder is working properly and is updated because I can RDP into my server externally.
(get your external ip - coreftp.com/misc/myip.php
If you can't connect via that, then it's some kind of routing issue external to Core FTP Server, or your router needs to port foward port 22 to 192.168.1.31[/quote]
Thank you. I have routed port 22 to my server's IP (192.168.1.31). I can use it's own address (192.168.1.31) in WinSCP and it successfully connects to CoreFTP. However, I cannot use the external IP or the DNS forwarder to the external IP. I know the DNS forwarder is working properly and is updated because I can RDP into my server externally.