Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Andrzejek on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

No Prompt for PPP Connection on S8700 Dial-Up

Status
Not open for further replies.

Midstream

Programmer
Jan 15, 2004
733
US
Instead of being prompted for starting my PPP connection upon dial-up to this S8700, I get some kind of Terminal Emulation prompt, followed by a BASH Command Prompt. This is unlike any other S8700 I've dialed into. Advice please?

Phil
S8700 CM2.1
 
rockspop,

first of all, do you really need ppp if you already got the command prompt? just type 'sat' and you'll have terminal emulation to do anything you need. if you do need ppp, just type 'ppp' at the command prompt and you'd get it.
 
I'm still in the Windows Dial-Up Networking window, trying to get the ppp connection established so I can launch ASA. This is what I see after successful login.

RFC_8700_12.4.20-AV14login: remote
Password:
Last login: Thu Aug 4 08:13:12 on usb/ttyACM0
Fri Aug 5 09:52:34 CDT 2005
Enter your terminal type (i.e., xterm, vt100, etc.) [vt100]=>vt100
16101: old priority 0, new priority 0

remote@RFC_8700_1> startppp
-bash: startppp: command not found
remote@RFC_8700_1> ppp
-bash: ppp: command not found
remote@RFC_8700_1>

The sat command gives me a SAT terminal right there in the Windows Dial-Up Networking box. It doesn't give me the opportunity to complete the ppp connection and launch ASA.
 
rockspop,

alternatively you can set up your asa to use 'modem' dial-up method to reach this switch.
 
Jaymzter,

First let me say that I use your web page A LOT! Thanks!!!

I know that I shouldn't have to start the PPP process, it should start by itself, but it doesn't. The 8700 gives me the bash prompt instead. Just for the heck of it I dialed up using ASA, entered the remote login and password, typed SAT at the bash prompt, then used my personal login and password to access the CM software. I've never done it that way, never heard of that being a new process.
 
Figured it out!

Read Jaymzter's documentation one more time!

The service level on the "remote" login was set to super-user, not remote.

Now it's working like it should.

Thanks!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top