It may be that you have themaximum number of telnet sessions already logged into the box. This could be the case since the telnet connections do not use TCP keepalives, and if you 'quit' a client telnet application, rather than 'close', then the connection state can be left up. I believe that there is an idle parameter in some MAXes which allows invalid connections to be timed out. This is in System>Sys Config>Idle Logout If the parameter is set to 0 then idle logouts are disabled. setting it to any value up to 60 will give the number of minutes which an inactive Telnet connection will stay around for. Do this before you reset the box. (or after you reset it the first time, during the same outage). Otherwise, it may occur again in the future. I believe that a reset must occur for this change to take effect. Greg > -----Original Message----- > From: Vilmos Branyik [mailto:vbranyik at piopc.com] > Sent: Sunday, August 12, 2001 1:40 PM > To: 'ascend-users at max.bungi.com' > Subject: (ASCEND) Problem telneting into 4048 > > > Sorry for what I think is a very basic question. > > I have a 4048 that has been in service for some time. All of > the sudden I > can't telnet into the box. Even when I connect to it and > change the password > I can't get in. > > I haven't tried a reset yet (I'm trying to avoid one) as this > is my primary > dial-up access router. > > I've gone through the docs. Does anyone have any suggestions > on how to fix > this. > > Thanks for any suggestions. > > V. Branyik > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to > ascend-users-request at bungi.com > Archives: http://www.nexial.com/mailinglists/ > ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/