telnet (with userId/password as parameters)??

No, password is require by typing for telnet.

However, you can use rsh (remote shell) which without typing password ( put "+" in ~/.rhost)

Wesly

I would not use telnet to do this kind of job. A sniffer can capture the plain text package from a telnet connetion including user + password. ssh can do the job.

If you really want to use telnet, expect is a tool to help make an automatic telnet script, and you can redirect the output to a local file!  
http://expect.nist.gov/

or have a look at
http:Q_20995574.html

some systems support unsafe file named .netrc to store raw passwords.
ssh is much safer and supports passwordless authentication using public key authentication with ssh agent, so consider exploring this posibility instead of others.

Does .netrc work for telnet too?? I though it was FTP only

Manav

.netrc is FTP only.

Unlike FTP, telnet is a totally unstructured protocol and does not have native concepts of user-id and password.

I'd have to throw my hat in with yuzh and say to use ssh or telnet+expect.

What I was hoping for is to have telnet (or PuTTY) shortcuts on my desktop such that I could double click on one and it would
open to a machine and I would not have to be prompted for user/passwd (just provide it as a parm).

This would be a great convenience at times.  

Increase points to 100

I take it this is a Windows desktop.

My suggestion is to:
o Use SSH instead of Telnet, using PuTTY as the client
o Setup keys so you can login with the keys instead of a password
o Use PuTTY's key-agent so that you only get prompted for the key's passphrase once instead of on every login

Yes this is a Windows desktop.


If I use SSH, then can I only execute a command?  Because I want a session (with the mere convenience of
not being prompted with userId/passwd), not just a command.

Hi,
>  want a session (with the mere convenience of lot being prompted with userId/passwd), not just a command
Yes, you can with ssh as chris_calabrese's post.

Rsh will do the same thing if you donot care about the security very much. Because it will be easier for you to implement
passwordless login ( put "+" in ~/.rhost).

However, it's up to you.

Wesly

Sounds good Chris.  Can you provide me more detail on the PuTTY way.  I've tried it, but it's
not clear how I should proceed.

Increasing points to 200 (for more detail).

thanks.

PS -
I have a PuTTY client on my Windows desktop.  I want to use it to create a session with a Unix machine such that I am not prompted
for user Id and password.  I have an account on the Unix machine.  This is only for the convenience to be able to double click on an
icon and have the Unix session ready to go w/o being prompted for login.