To have a better experience, please upgrade your IE browser.upgrade
Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
|After the operating system is installed on the T3500, remote SSH logins are slow to implement.|
Step 1 According to the fact that local SSH logins are normal, this problem is hardly possible related to the T3500 hardware. The network may be faulty.
Step 2 Use a normal T3500 onsite to ping the faulty T3500, and the ping is successful. However, pinging the faulty T3500 remotely fails.
Step 3 After the customer logs in to a normal T3500 using an SSH tool, the customer successfully pings the faulty device from the normal T3500. This fact indicates an error on the transition between the Intranet and Internet.
Step 4 Compare a normal T3500 with the faulty T3500 in terms of the IP address, subnet mask, and gateway address. It is found that the gateway address and IP address of the faulty T3500 reside on different network segments. External access to the T3500 passes through improper routing; therefore, logins slow down and pings fail.
Step 5 Configure the gateway address to the same network segment as the IP address.
Step 1 The operating system is faulty.
Step 2 The network is faulty.
Step 3 The hardware is faulty.