After a long time of having all the virtual servers' ports open to any IP, I decided to restrict access to some of them to the IPs that needed them.
So I restricted access to the Terminal Server port (3389) only to the company's IP, but left the HTTP (80) and FTP (21) ports open to any IP.
However, after applying the change, the FTP port now appears to be blocked to any connection. The only way to unblock it is by restricting access to it to the company's IP, but in that case the other IPs won't be able to connect to it anyway. The HTTP port keeps working as usual.
Why did this happen, and how can I fix it?
Here is an example of what I had before the changes:
As expected, Terminal Server is now accessible only from the company's IP address, while the HTTP port is accessible from any IP. So should be the FTP port, but instead it doesn't work at all (connection failed).
The best way out in this case would be to use a Router that supports Access Lists or a firewall that will permit or deny certain users and also for the specific ports. The configuration seems fine to me, however I have not been able to detect the cause for the FTP connection not working. You could also check if there is a bug related to this.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...