www.satsig.net

Satsig.net home page

Index page for all SatSig topics

SatSig Topics IndexiDirect Forum: hubs and terminals › Cannot " Telnet 0 "to Modem
SatSig topic:

Cannot " Telnet 0 "to Modem

(Read 5183 times)
Jul 11th, 2008 at 9:45am  
  hi

  I connected my 3100 series modem via hyperterm from my pc , i can login to linux prompt by user as root and when i tried to access idirect application by typing
"telnet 0" it shows like this

iDirect login: root
Password:
Linux iDirect 2.4.24-uc0-iDirect0 #1 Fri Apr 29 16:01:03 GMT 2005 armv5b unknown

# telnet 0
telnet: Unable to connect to remote host (0.0.0.0): Connection refused
#

How i can solve this

sml
Jul 11th, 2008 at 10:14am  
This is normal when the Falcon process cannot be started, typically due to a bad options file, do you also get a message repeating that starts with FPGA then a time/date stamp?
also does the modem restart after a time?

your issue is common with bad options files, so recovery with a known good (Correct software version and Serial number etc.) options file will solve this for you.

Jul 11th, 2008 at 10:54am  


i did but it shows

failed to reload stack config
r7 : 000003e8  r6 : 000014a3  r5 : 40d9e008  r4 : 002deae0
r3 : 00000000  r2 : 40d9e008  r1 : 002deae0  r0 : 40d9e008
Flags: nZCv  IRQs on  FIQs on  Mode USER_32  Segment user
Control: 39FF  Table: 03D24000  DAC: 00000015
Falling back to Error stack, and trying again:
Segmentation fault
OK

Starting falcon_monitor:OK
Jul 11th, 2008 at 11:53am  
Scout is right on the money.  Your opt is corrupt and Falcon is not able to start properly.  You are going to have to do it all manually via console or WinSCP.
Jul 11th, 2008 at 5:11pm  
Remote stop boot with Stack Error, this means your s/w file also currupt or incorrect. You will need to load the s/w file and option file thru WinSCP. So,  you need to use Remote recovary procedure.

1. Stop the falcon process "service idirect_falcon stop".
2. Start sshd to use WinSCP "service sshd start" and make sure it is running by ps -ef | grep sshd
3. use WinSCP and copy the s/w file to /root/tmp at Remote.
4. Follow Remote recovary procedure.

Hope this helps..!

www.satsig.net

Email me:eric@satsig.net

Disclaimer, Terms of Use and Privacy

Old Forum rules

Cookie policy.