What's RES.net?


Well, this question is answered in more detail by the WWW pages maintained on the TSC homepage, attainable by clicking here. But, for a very brief overview, read on.

RES.net will allow you, the on-campus student, access to all campus computer systems, as well as direct internet access from the comfort of "home". This means that if you are a Computer Science student, you can access the HOLMAN1 Novell server. Business majors can access Bliss servers*. You can also access your UNIX and TSCVM accounts directly: You can read your E-MAIL, or use UNIX/TSCVM commands just as if you were seated at a computer lab terminal.

There is one caveat to be aware of. If you originally had no access to a UNIX/TSCVM/Novell account, RES.net will not permit you access to those systems. RES.net is merely a connection to the campus networks, it does not get you access to system resources if you do not have login information for the system in question.

RES.net (and indeed, any network) can be visualized as a system of highways and roads. Your car (your PC in the RES.net case) can take you to any place the roads go, but if you don't have a key to the home/business you'll find alnog the way, you can't get in.

That said, what else can you do? Well, RES.net gives you a direct, fast (in theory**) connection to the internet. This means you can use telnet or FTP to access systems external (as well as internal) to the college. Note that once again, RES.net is only a transportation mechanisim. You won't gain access to external site's accounts without the required login/password information.

Does any of this seem familiar? It should if you used to trek to the Bliss or Holman labs to telnet into Rutgers for a round-table chat, or FTP to your favorite file repository. The only difference is that you need only trek across the room to your PC (though I realize a cross-room trek is a challange for those very untidy folk....) ;)

Return to my RES.net page


*Access to Novell servers (HOLMAN1, BLISS1-4, etc.) comes with limitations. Novell servers can handle no more than 100 simultaneous connections throughout campus. This means that if a lab is full (say 50 students), and 25 more are using its server from teaching labs, conceivably only 25 connections are left available to that server. The 26th person is out of luck.

**I say "in theory" because any network will be loaded down when hundreds of users are accessing it. This holds true for RES.net. You will find as you use RES.net that certain times of the day certain operations take longer to complete than at other times. It's because many people are at class, off campus, sleeping, etc.