Since moving to ATM have not been able to telnet to the router through the ATM Interface (Tried ip of atm, eth, and loopback no success). Can telnet to a switch behind the router and then telnet to the router from the switch.
Switch <--> ATM Router <--> T3 Router <--> Client trying to connect to ATM Router.
There are several things that might produce the symptoms that you describe and we do not yet have enough information to identify the most likely cause.
One potential problem is not having a working route to the telnet target, or the telnet target not having a return route to the client. One way to test this would be to ping the address of the telnet target from the client. If ping works then it is not an IP connectivity problem. The fact that you can telnet to the switch behind the router suggests that it is not an IP connectivity problem. ping would confirm this.
When you attempt to telnet what happens? Do you get a prompt to login? Do you get an error message and if so what is the error message? Knowing these things would help narrow down the cause of the problem.
Another thing that might cause these problems is an access list. Is there any access list on any interface? There did not seem to be any in the config that you posted but it was not the complete config. There might also be an access list on the vty ports (assigned with access-class) which controls telnet access. Is there any access-class on the vty ports?
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 custome...