I'm having a problem trying to allow Microsoft Terminal Server through a router with an extended access list. I found out that the tcp port used for the application is 3389. This router separates a test network from our corporate network and has a very restricted access list which allows only dns, ftp, smtp, telnet and icmp. The access list is placed on the Ethernet interface that faces the test network for the traffic going in to the interface. The Terminal Server client is on the corporate side connecting to a server in the Test Network side. Could you help me please.
Thank you for your reply. That was very helpful in a way that I found out the reason why the access list was blocking it. Apparently the server has a fixed port number by default (3389) and that was ok. The thing is that when the server reply to the client it uses a random port number which I don't know yet the actual range but it is in the region of 1500-2000. So what really helped was the 'deny ip log' command. Now I have allowed that range and it is working.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...