guide - remote access
Tamos.net is a unix machine in a crowded little closet. Currently, there are no plans for dial-up lines. Whatever access you get will be by the network through which Tamos.net is connected. There is a balance one must try to keep between making access easy and making access secure. I have tried to do my best in making things as easy as possible to access but always with security in mind. I feel Tamos.net is somewhere in the middle.

ftp

The File Transfer Protocol is very heavily used and comes with most Operating Systems of one form or another. Some browsers, such as Netscape, Internet Explorer and Lynx, even support the FTP protocol natively.

http

This is a little more interesting than ftp in that the web daemon can handle bi-directional file transfers. Netscape Gold uses this ability to upload files to a remote web server. I will post instructions on how to use this once I have it installed.

Netware Core Protocol

I have no plans to export directories via NCP. The route to the internet does not propogate IPX packets. Therefore, this option is moot.

Network File System

I have no plans to export directories via NFS.

Server Message Block protocol (SMB)

Using the SMB protocol, it is possible to export your home directory to another machine. Operating Systems that support this protocol include some versions of Unix, Microsoft Windows for Workgroups, Windows 95 and Windows NT. This is now implemented on tamos.net. If you would like to access stuff remotely using this protocol, let me know.

ssh

SSH is a secure replacement for rlogin, rsh and other "r" tools. Ssh has now been implemented on tamos.net and it's use is recommended in leiu of the "r" tools. Instructions are available in the form of "man pages".

telnet

Telnet is a very common and probably the most used remote access protocol in the wonderful world of Unix. Telnet software comes with most Operating Systems and is available from sites all over the place.