Anna: The forwarded message from your isp is not needed. Also, ssh is a more secure protocol than telnet so it's advisable to always use ssh as opposed to telnet if you are using a pc which is capable of making a connection to another machine via ssh. And, as you're running Red Hat you definitely do have this capability. So, to connect to your provider you'd do the following asumming your username there is annas. Type only: ssh annas at host Replace host with the fully qualified domain name of the machine where your shell account is. Of course, you could telnet instead, but to give you a better reason why most people would advise against you doing that, ssh is more secure than telnet, when you send data to a host which you've connected too via telnet it is possible for people to intercept and possibly read the data your sending if the people have malicious intent, whereas, ssh incripts all data so it does not send plane text which is interceptable by packet sniffing programs and such. If you're really set on telneting you just type telnet hostname at the prompt. And, in concluding, if you want more evidence of how telnet is not advisable I'm sure if you surveyed the members of this list who allow remote login on their machines, very few allow telnet logins. I do and will for the next three weeks or so as I do telnet in to my machine from time to time, however; after that I'm gonna kill the telnet service. Hth, good luck, and feel free to write if I might be able to help you further. Ed Barnes Harbour Grace, Newfoundland, Canada home phone +1-709-596-3165 e-mail and msn messenger id ebarnes at enigma2.cjb.net ******** "There is a fantasy in Redmond that Microsoft products are innovative, but this is based entirely on a peculiar confusion of the words 'innovative' and 'successful.' Microsoft products are successful -- they make a lot of money -- but that doesn't make them innovative, or even particularly good." -ROBERT X. CRINGELY ******** On Tue, 6 Aug 2002, Anna Schneider wrote: > > Okay, I read all the suggestions yesterday regarding what to do after > connecting, and I'd like to telnet for now. I at least know sort of what > it is, but I'm suspecting after some experiments that I have to set up > some kind of configuration file for it too, is that correct? I looked up > telnet on the man pages, but there was stuff of stuff that didn't make any > sense. Anywhere else I could look? Do people here have suggestions on > what I could do? And is any of the information in the PPP set up message > from drizzle that I'm forwarding again useful to telnetting? > > Thanks. > > Anna > > ---------- Forwarded message ---------- > Date: Tue, 30 Jul 2002 19:02:14 -0700 > From: Drizzle Technical Support <info at drizzle.net> > To: annas at drizzle.com > Subject: Drizzle Support - Linux PPP setup > > Hi Anna, > > If you're configuring Linux to connect to Drizzle, then we assume you have a > firm grasp of how to connect to an ISP. > > You can use PAP or CHAP to login. > > For your dial up connection, you need to append your username with "-ppp" > like this: > > annas-ppp > > Your connect script should look for some version of "login" and "Password" > and send your username (with the -ppp) and your password. > > Your IP address and Gateway address will be assigned dynamically via DHCP, > so you should leave them unspecified. Using 0.0.0.0 is the usual way of > doing this. > > POP3 server: pop.drizzle.com > > SMTP server: smtp.drizzle.com > > Dial-up Numbers > (206) 812-0034 - Seattle > (425) 974-0190 - Bellevue/Eastside > (425) 791-0139 - Everett/Snohomish > (253) 579-0111 - Tacoma/Pierce > > This information is found online at http://www.drizzle.com/vital.html > > If you have questions or need help, just contact us. Our tech support hours > are M-F 8 AM -7 PM. > > Good luck! > > Bill DeLarber > Drizzle Internet NW > info at drizzle.net > (206) 447-2702 > (800) 378-7405 > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup >
