FTP Site Profile

ftp.csr.utexas.edu is a SUN Ultra server with roughly 2-GB of free space at any one time for incoming files. The system runs over a 100-Mbit link from our site to the University of Texas Main Campus. From there its probably a 45-Mbit link to various internet points.

CSR/TSGC Anonymous FTP Server


FTP Site Rules

Like most FTP sites, CSR has a few restrictions...

  • Only 25 users can connect at any one time. We seem to average 2 to 5 users, so its fairly robust.

  • Any files in ftp:/pub are available for 'getting' only, you will not be able to 'put' any files into this directory. Files in this directory are permanent (are not removed/wiped after any preset time period.)

  • Any files in ftp:/outgoing are available for 'getting' only, you will not be able to 'put' any files into this directory. You should also be aware that all files are removed/wiped after 30-days of being deposited.

  • Any files deposited in ftp:/incoming are available for 'viewing' only, you will not be able to 'get' any files from this directory. You can not create sub-directories in 'incoming' without administrator approval. You should also notify the CSR/TSGC receiver as all files are removed/wiped within 30-days of being deposited.

  • All user accesses are logged (when you connected and from where.) If we can not resolve (via DNS) from where you are connecting, you will be denied access.

  • Currently ALL '.net' users are refused access. This policy is under review. However in the past 2-years we have had ONE user request access from a '.net' domain.


Typical FTP Site Access Problems

Remember! We do not allow connections from ".net" domains at this time. If you are coming from a non-".net" domain, read on for the most common problem.

Some users/sites can not access our FTP server because the originator's site is not doing things properly, or what we consider proper.

We do simple DNS authentication for all users accessing our FTP site, we've done this for several years because of previous abuses. Thus, we require all anonymous users to have their machines registered such that a check of the originating system's IP number "125.125.125.1" resolves to a DNS name. Those sites that do not do this basic DNS courtesy are considered potentially dangerous. This simple technique has served us well.

To check if you are setup properly do the following from any UNIX based system.

nslookup [IP.Number.Number.Number]

This isn't a guarantee that you should have access, but it is a positive indicator. We have seen some sites configure their DNS server to work locally but not globally.

If you need help with how to configure your DNS systems, send us the following information ...

  • Your DNS Server [optional, helpful]
  • The system you are attempting to FTP from
    • with the system's host name
    • and the system's IP number

We expect your local DNS administrator to know how to resolve your problem. But we can point out if the DNS resolution is working and why it fails. A quick work-around? Find a machine that does DNS resolve properly.

Your administrator, at a minimum, should be able to direct you to a machine that can accomplish the FTP. If you are sitting behind a firewall or something see your administrator we can't help you.

Otherwise, if you fail to get a DNS administrator to assist you recontact us and we will ask if someone is willing to vouch for you to make special accomodations. If you don't know anyone, we will be slow to respond as we strongly encourage the correct procedure illustrated above (its the courteous way of doing things.)

Questions can be directed to: ftp.help@csr.utexas.edu



Buttons


CSR/TSGC Team Web