06-28-2013 10:49 PM - edited 03-18-2019 01:22 AM
Not sure your gus have experience this before, I was unable to telnet to C60 codec with TC6.0 (new codec). The Telnet service was enable. Ping and web access is working fine. Whenever I put telnet it keep on getting message like as below. I have put it back to factory default via web and still same issue. any clue?
Command: telnet codec IP, and reply was as below:
Get name info: localhost : success
Temporary in name resolution: success
connection to host lost
DV
Solved! Go to Solution.
06-29-2013 03:53 PM
Hello Din,
You probably hitting bug CSCue72551 (Telneting to EX90/C90 failed)
Workaround:
Make sure DNS is working properly so codec can do reverse lookup of the address which is connecting into the codec.
Or upgrade to a release containing fix.
Or use SSH.(Recommended one from my point of view)
HTH,
Ahmed
06-30-2013 01:44 AM
Hi,
Upgrade codec to TC 6.1.x which is having fix as per internal detail of bug .
Kind regards,
Dharmmesh
06-29-2013 01:27 AM
Hi Din,
Please check if there is no ip binding for telent access
check it in the xconf // network
xConfiguration Network [1..1] RemoteAccess Allow
Filter IP addresses for access to ssh/telnet/HTTP/HTTPS.
Format: String with a maximum of 255 characters, comma separated IP adresses or IP range.
Example: xConfiguration Network 1 RemoteAccess Allow: "192.168.1.231
if so please remove the address.
from where are you accessing your codec ,
thanks
Ravi kr.
06-29-2013 04:31 AM
I have tried both this config without any IP address and with the IP addrerss of PC wish to do telnet, both case have the same result. I also tried put it back to factory default by web and only configure system IP, enable telnet without changing any others setting, it still didn't work.
Any other idea?
06-29-2013 03:53 PM
Hello Din,
You probably hitting bug CSCue72551 (Telneting to EX90/C90 failed)
Workaround:
Make sure DNS is working properly so codec can do reverse lookup of the address which is connecting into the codec.
Or upgrade to a release containing fix.
Or use SSH.(Recommended one from my point of view)
HTH,
Ahmed
06-30-2013 01:44 AM
Hi,
Upgrade codec to TC 6.1.x which is having fix as per internal detail of bug .
Kind regards,
Dharmmesh
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide