I've been using telnet centos for the class and now the class is ending (just finished the exam a few hours ago) and I was wondering if there were any way to transfer some of the practice files I've been working with to my local hard drive. As far as I can tell the two systems are completely independent and can't communicate.

What operating system/distro are you running, what are you connecting to, and how are you connecting to it?

You can not transfer files using telnet. You need to contact your instructor to see if there is anyway to download your source code. The usual methods are ftp and scp. I assume neither nfs or SMB/CIFS are enabled.

1 members found this post helpful.

I've been using my mac, the google chrome browser to connect to a remote windows desktop, then I type cmd into the command prompt there and type in telnet centos.

Interesting. Why not use use the telnet client on your Mac?

This course only covered some very basic commands, connecting with a server or even manipulating files across different drives was never covered. I can copy files, that's just a matter of inserting the drive letter and directory location into the command isn't it? But I don't know how I would connect to the server using the terminal window.

Do both systems have Internet access? You could create a tarball and mail it to yourself.

What I posted was just an aside comment but then I do not know how networking was configured. Instead of using a remote desktop and then using telnet it might of been possible to just use telnet on your mac.

As suggested I would ask your instructor.

Under Linux/BSD you can use
but you will have to have the url.

In a browser, use save page as.

If they're connected on a network, and can talk to each other, and both have netcat installed, and the firewall isn't in the way.

Receiving machine:
nc -l -w 180 -p 5900 > filename.destination

Sending machine:
nc -q 0 -n $(IP) 5900 < filename.source

Where 5900 is the port used in this case, but could be any available port afaik. And $(IP) needs to be the IP of the receiving machine. I tend to use this a lot for firewall scripts and other things as it's mostly there by default, and doesn't require setting up any sort of server stuff. But if the firewall is in the way, then it fails.