I was wondering if it was possible to use telnet to download a file onto a target box and run it all remotely? Or should I look into downloading vnc .dll's and do it all from a gui?

Telnet is obsolete, legacy.
rdesktop is included in Windows, IIRC, just go to services.msc and enable it.
Anti-viruses and *firewalls* generally doesn't like VNC, and Vista doesn't like tightVNC.
If it's a Unix-like box, some form of rsh might be installed, use this instead.

A simple batch script can download it and run it.
Lookup wget in your favorite search engine.

Looks like we need that announcement/sticky again...

Looks like we need that announcement/sticky again...

lololol how does i telnet into mah school? plz guiz i wan 2 delete system32.

lololol how does i telnet into mah school? plz guiz i wan 2 delete system32.

All I meant was to say that all of the computers at my university had port 23 open and I thought that it would be easier to try to connect using telnet than some other method. I already have most of their passwords, I was just looking for an easy way to get in remotely.

You should read some stuff on telnet- it's not really something that can be used to execute commands on another computer- if I'm not mistaken that would be SSH, or if you wanted to upload files that would be FTP. etc., telnetting on port 23 will rarely get you anywhere, maybe a BBS but that's it.

You should read some stuff on telnet- it's not really something that can be used to execute commands on another computer- if I'm not mistaken that would be SSH, or if you wanted to upload files that would be FTP. etc., telnetting on port 23 will rarely get you anywhere, maybe a BBS but that's it.

thanks, Im probably going to set up an ssh client on some of the machines and see how that goes.

You should read some stuff on telnet- it's not really something that can be used to execute commands on another computer- if I'm not mistaken that would be SSH, or if you wanted to upload files that would be FTP. etc., telnetting on port 23 will rarely get you anywhere, maybe a BBS but that's it.

Telnet is unencrypted ssh.

Oh okay, I finally know what it's used for now!

You should read some stuff on telnet- it's not really something that can be used to execute commands on another computer

Telnet is primarily used to log into other computers and execute commands.

It is not a file transfer system, however.

Telnet is primarily used to log into other computers and execute commands.

It is not a file transfer system, however.

Well, I now know that- I thought it was a universal sort of...connection tool but you specified a port number and it would use that protocol. I was really ignorant on the subject and never bothered to look it up lol, I always thought SSH was the main thing for remote logging-into-systems.

Well, I now know that- I thought it was a universal sort of...connection tool but you specified a port number and it would use that protocol. I was really ignorant on the subject and never bothered to look it up lol, I always thought SSH was the main thing for remote logging-into-systems.

Telnet existed almost as long as the original interconnection protocols of ARPANET. It was the main login system, and was considered adequate because the network itself was assumed to be free of saboteurs. (ARPAnet was a network between a few government agencies, universities and defense contractors, and eventually expanded into the Internet.) It was entirely unencrypted, however, so passwords were easy to capture -- but then again, that wasn't a concern for the designers of a closed system. This was back in the late 1960s, specifically, 1969.

SSH came about in the 1990s, while the Internet was expanding beyond its military user base. It was an encrypted replacement for telnet, and also provided encrypted replacements for ftp (sftp) and uucp (a unix-to-unix copy program replacement -- called scp).

Telnet existed almost as long as the original interconnection protocols of ARPANET. It was the main login system, and was considered adequate because the network itself was assumed to be free of saboteurs. (ARPAnet was a network between a few government agencies, universities and defense contractors, and eventually expanded into the Internet.) It was entirely unencrypted, however, so passwords were easy to capture -- but then again, that wasn't a concern for the designers of a closed system. This was back in the late 1960s, specifically, 1969.

SSH came about in the 1990s, while the Internet was expanding beyond its military user base. It was an encrypted replacement for telnet, and also provided encrypted replacements for ftp (sftp) and uucp (a unix-to-unix copy program replacement -- called scp).

Was scp a replacement for uucp, or for rcp? I always thought the s* utilities were a replacement for rlogin/rcp and the rest of the r* utilities.

Was scp a replacement for uucp, or for rcp? I always thought the s* utilities were a replacement for rlogin/rcp and the rest of the r* utilities.

rcp and uucp perform the same job, so it could be said to be a replacement for either.

rcp and uucp perform the same job, so it could be said to be a replacement for either.

I thought uucp was email before email?

I thought uucp was email before email?

uucp was used for the original email, and for a long time it was used to copy usenet from one node to another. It was a general purpose remote file copier though.