In addition to the suggestions from Edwin I have a comment and suggestion. I notice that the original post has the exec timeout set to 0 which says that inactive sessions will never time out. While I sometimes do this on console connections I think it is not a good idea on vty ports. I have seen many situations where someone telneted to a device, lost the network connection, and the vty port still maintained the session. I have seen situations where telnet access did not work because all of the vty ports were busy and orphan sessions were most or all of it.
If you can get to the router at all (perhaps through the console connection) do a show user and see if the vrt ports are in an occupied state with unexpired connections. If so a clear line on the router will solve the immediate problem.
I suggest that it is better to set very long timeouts on vty if you want, but I suggest that you do not disable inactive timeout on vty ports.
If I understand the question "if you do not want to have access to the 831 is correct" then I would remove the login and password from the line command. You could also create an access list and apply it to the vty's that would limit who is allowed to telnet to the router.
If you do want access and the lines are not all used what possible access lists do you have on the main interfaces that could be blocking incoming telnet connections?
Rburt is correct about the exec-timeout command. The way you have it all the vty lines could get used and also stop any further sessions to the router.
From your post under line vty 0 you have disabled the incoming connections by keyin in transport input none just change the same to transport input telnet and also any specific reason attached in configuring the length to 0,we normally keep that to defau value which 24....
Prevents any protocol selection on the line. This makes the port unusable by incoming connections
transport output none--Issue 2
Prevents any protocol selection on the line. The system normally assumes that any unrecognized command is a host name. If the protocol is set to none, the system no longer makes that assumption. No connection will be attempted if the command is not recognized.
Comment on above.
Any settings made with the transport input or transport output commands override settings made with the transport preferred command
length 0--"Not normal but should not be an issue"
In the following example, the terminal type is specified and the screen pause function is disabled for the terminal
My concern would be does the ISP allow you access your routers HTTP port.
What I would do is swap IP addresses on the router and connect your PC to the Outside interface(That is now configured with your internal IP network address) then see if you can get to the web interface. This would at least determine if you might have an ISP blocking you from accessing the outside interface when connected correctly to the Internet.
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...