External FTP Requests Stopped Working!
I installed our FTP server via IIS6 on our public web server about 6 months ago and bound it to a separate network card, public IP address and public DNS name, which up until recently it has been working without fail.
Recently, external clients complained intermittently that they couldnt connect. Initially I couldn't replicate from from home, but I am now finding that it appears to have totally stopped working as I now I cant connect from home and no one else has reported success with it.
If I test this internally, it works every time!
The known results from vairous external methods of connections to both the DNS name (ftp://www.ftpsite.co.uk) and IP (ftp://xxx.xxx.xxx.xxx), are as follows:
Windows Explorer: "A connection to the server could not be established."
Internet Explorer 7: "Internet Explorer could not display the page"
DOS: "Connection timed out"
Ping:
Pinging www.ftpsite.co.uk [xxx.xxx.xxx.xxx] with 32 bytes of data
Request timed out.
Request timed out.
Request timed out.
Request timed out
The strange thing is that our http: website works fine, which is on the same server and also hosted via IIS6. So I changed the internel IP of the FTP site to share the one that our website is using, and tried to access the same FTP site using the dns name of our website, but it still doesnt work.
Can anyone shed any light on this issue, as I'm running out of ideas?
Thanks
FTPDiagram.jpg
Recently, external clients complained intermittently that they couldnt connect. Initially I couldn't replicate from from home, but I am now finding that it appears to have totally stopped working as I now I cant connect from home and no one else has reported success with it.
If I test this internally, it works every time!
The known results from vairous external methods of connections to both the DNS name (ftp://www.ftpsite.co.uk) and IP (ftp://xxx.xxx.xxx.xxx), are as follows:
Windows Explorer: "A connection to the server could not be established."
Internet Explorer 7: "Internet Explorer could not display the page"
DOS: "Connection timed out"
Ping:
Pinging www.ftpsite.co.uk [xxx.xxx.xxx.xxx] with 32 bytes of data
Request timed out.
Request timed out.
Request timed out.
Request timed out
The strange thing is that our http: website works fine, which is on the same server and also hosted via IIS6. So I changed the internel IP of the FTP site to share the one that our website is using, and tried to access the same FTP site using the dns name of our website, but it still doesnt work.
Can anyone shed any light on this issue, as I'm running out of ideas?
Thanks
FTPDiagram.jpg
DewFreak
This sounds like a firewall issue. What type of firewall are you using and have you rebooted it latley?
ASKER
I have rebooted the firewall recently, but no other traffic appears to be affected and the FTP rule is still there.
We are using a SonicWall 2040 Pro.
Would you suggest another firewall reboot?
I rebooted the web server last night to see if that helped, but alas it didnt!
We are using a SonicWall 2040 Pro.
Would you suggest another firewall reboot?
I rebooted the web server last night to see if that helped, but alas it didnt!
Yeah, sounds like a firewall rule. Watch the logs for your FTP requests to see what is happening.
I would check the rule and see what internal IP the FTP is pointing to.
ASKER
Just tested again from an external source and this time I was able to login successfully via IE and was able to open an FTP Explorer window via 'Page\Open FTP Site in Windows Explorer'
I guess the intermittent issue is back!
I guess the intermittent issue is back!
ASKER
I would say that the rule is fine as it used to work and as per my last post, it still does, but now its only occasionally.
The rulle allow FTP WAN traffic into the internal IP assigned to the FTP site. However this does explain why it didnt work when I changed the internal IP of the FTP site to that of our Web site!
The rulle allow FTP WAN traffic into the internal IP assigned to the FTP site. However this does explain why it didnt work when I changed the internal IP of the FTP site to that of our Web site!
Again, watch your logs. When people call up with the issue you can get their IP address (www.wimi.com) and search your logs for the information on there. It will go a long to figuring out the root cause.
ok, so now to troubleshoot the "occasional" problem. Using IIS6 your users willl need to disbale passive FTP.
ASKER
I'm so confused as to why a PC that didnt work, now works!
On the test PC, I disabled Passive FTP and its still working, but as it was working prior I cant confirm that this made any difference.
I will try again from home tonight, as I can definitely say that it wasnt working from there last night.
On the test PC, I disabled Passive FTP and its still working, but as it was working prior I cant confirm that this made any difference.
I will try again from home tonight, as I can definitely say that it wasnt working from there last night.
ASKER
Thanks for your help so far guys, have a nice weekend.
ASKER
I've looked at my firewall logs and found notthing has been blocked.
But I may have found a solution, which uses part of DewFreaks last suggestion and may be related to just IE7.
#: In IE, Tools - Internet Options - Advanced
#: Tick: Enable FTP Folder view (outside of Internet Explorer)
#: Untick: Use Passive FTP (for firewall and DSL modem compatibility)
#: Click OK
#: Then enter: ftp://<username>:<password>@ftps
#: Click Page Menu and select "Open FTP site in Windows Explorer".
I'm still awaiting feedback from others on this, but its been working for me since trying this method.
But I may have found a solution, which uses part of DewFreaks last suggestion and may be related to just IE7.
#: In IE, Tools - Internet Options - Advanced
#: Tick: Enable FTP Folder view (outside of Internet Explorer)
#: Untick: Use Passive FTP (for firewall and DSL modem compatibility)
#: Click OK
#: Then enter: ftp://<username>:<password>@ftps
#: Click Page Menu and select "Open FTP site in Windows Explorer".
I'm still awaiting feedback from others on this, but its been working for me since trying this method.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.