7
4
How can I prove (with logging) where a port block is occurring?
I've set up an FTP site on IIS (windows 7 home) and set up a rule in the Windows Firewall allowing access. The ftp site is accessible via my local browser to my static IP (ftp.example.com, where DNS is godaddy, so its resolving to my static IP and the ftp directory is being served). I've also set up a rule in my uVerse router firewall allowing FTP Server access to this machine. However, my customer cannot reach my FTP site, and when I test using mxtoolbox.com ..
1 open ports:
80 http Success 78 ms
These ports were closed:
21 ftp Timeout 0 ms
Furthermore, I can add other open ports, such as IMAP and POP3, and they show as open once I edit the router firewall. No matter how many times I delete and add FTP Server, port 21 never shows as open on mxtoolbox.com, and of course the customer cannot reach the FTP site. He can successfully reach my locally-hosted webpage.
Do you know of any websites set up to do this for a visitor? Such as mxtoolbox.com checks MX issues, and canyouseeme.org checks for open ports, a site that does a trace route and displays the results would be very useful here. (I don't have control over the remote customer box and he's not technical) – Robert Kerr – 2011-11-17T05:30:54.680
1I have never heard of any that would do something like this. Do you have no one you know that has a linux box? If you like I can test it. In my profile is my website, and there is contact form you can send me the IP address if you don't want to publish it here. – Paul – 2011-11-17T06:01:26.160