Stack error- 3100 not logging on

Stack errors are normally indicative of corruption in falcon (falcon.opt specifically).  You need to reload your options file.  Be advised, that you may or may not be able to negotiate reloading your 3100 if the opt is corrupt.  You are going to have to give it a try and if not able, you may have to copy, cut, and paste it in from console. Try to load it with iSite first, if unsuccessful, you can try WinSCP or do it from the linux prompt on console from the /etc/idirect/falcon directory.  

To save myself some typing, see this thread:
https://www.satsig.net/cgi-bin/yabb/YaBB.pl?board=idirect;action=display;num=120...

Use Teraterm Pro instead of hyperterminal (if you have ttpro).  Hyperterm often adds characters when negotiating the cut and paste.

M

Can you attach to it with iSite?  

I am assuming you are seeing stack errors popping up in telnet...that is, if you are able to connect to it (which I am guessing you are able to telnet to it).

Did you see any fatal errors in the boot process right as falcon is starting (or possibly just before falcon starts)?  

It certainly wont hurt to reload the opt.  That is fairly painless/harmless. If you can attach with iSite it is even easier to load that opt.  

In the past I normally resolved stack errors by either copy and pasting the opt directly into etc/idirect/falcon or I would do it by using WinScp to move it from my desktop into etc/idirect/falcon.  However, if you decide to do it with WinScP save the opt out on your desktop and rename it to falcon (it will take on the .opt extension automatically) and then copy it into etc/idirect/falcon

The messages that appears well connected through Hyper term.
On boot:  Failed to initialise ST
He is only able to ping the modem, he is not able to connect using iSite, Winscp, Telnet.