|
|
Please explain how the U of M dormitory computer network operates. What sort of computer does a student need. Will a 386 do? What size hard drive, how much RAM, video RAM? What operating system and software? What kinds of network cards are acceptable? What exactly are networked computers used for? Do you need a modem with them or just the network card? Are they primarily for internet access, or for accessing a mainframe computer for calculations? Can you store your own data on the university computer? The reason for asking is that first, we have some network cards at Kiwanis, second, Davel has offered some 396s that currently have network software on them (and maybe network cards in them?), and we may be able to supply students with computers, very cheap, depending on the hardware requirements.
14 responses total.
There are two ways to connect to the university network: 1. Dial up with a modem. This is the same as any other internet provider. 2. Direct connection to the campus network via a network card. This last option requires a network card that can handle TCP/IP protocol of a flavor that is compatible with Novel Netware. The university supplies the connection software as they have modified it slightly. The 3COM ethernet cards you have are adequate. When connected to the university network, you are on the internet, that is, you are a computer on the internet, not just accessing it through a modem. You can, in theory, do anything any other internet computer can do. In practice, you are not allowed to be a server. You can do all the things you mentioned and others too. The kind of computer you need depends on what you want to do, however the university holds a truckload sale every Fall, in which students can buy brand new computers at a very good price. They can also go to a public workstation and use a computer that is more powerfull than anything you have to sell. In short, you may be able to sell students cheap network cards, but they are not likely to be interested in your computers.
If all they want to do is get on the Internet through the dorm network, they need an ethernet card and a computer with a TCP/IP stack. Windows 95 has TCP/IP built in. Windows 3.1 has a bunch of add-on packages. Novel Netware has nothing to do with that. If they're trying to access file sharing services I have no idea what the University is doing for that at this point. Novel Netware may be needed, although again with Windows95, the Netware client is included.
Win3.11 has a network stack available for it from Microsoft, free for the downloading. It only works with Ethernet cards, though, as it has no dialer or PPP stack.
U of M uses AFS. You would need an AFS client (available, I believe, from the U of M ITD website) to access the file server.
What is AFS? So could we conceivably set up a 386 or 486 computer with an Ethernet card and Win3.11 and the software needed to connect to U of M? If so, could someone explain in simple language how to do this (or better yet, come in and demonstrate?) We just got in a working 486-50MHz and have 3Com cards and Win3.11 around somewhere (or can get it).
AFS is a secure (supposedly) network file system. It's one of many network file systems. Microsoft uses something called SMB, Unix usually uses NFS, AFS, or Coda, Netware has their own, etc. AFS has some advantages and some disadvantages. Yes, you could theoretically connect to U of M. The only hitch is whether or not U of M still supports, and has software for, Win 3.1. It looks, from their website, like U of M no longer supports windows 3.1. The only thing I could find about it is that they have an old dial-up kit, and ethernet users are supposed to "contact their system administrator." Sorry.
SMB is actually an open standard, unusual for MS. There's a freely available package called Samba that allows UNIX and Linux machines to 'talk' SMB. I've tried it and it works quite well...my Win95 machine thought it was talking to an NT server and was able to mount shared directories on the Linux system as network disk drives. There's printer support, too.
Samba is great stuff. It means I only need one server to handle routing, web serving, file serving, print serving, mail serving, and it means that all this is available transparently no matter what OS I happen to have booted on a given machine. I highly recommend Samba for anyone setting up a home network.
Would a 486 running FreeBSD be suitable for hooking up to the U of M?
(Keesan, do you have a recent version of FreeBSD on CD? If not drop me a line - I've got 3.1 which I no longer need since I also have 3.2)
Hooking up how? Via ethernet, no. There is no free AFS client that I know of. Rather, the free software of focusing on a new standard called CODA that does pretty much what AFS does. So, with FreeBSD, you have the same problem that you have with Windows 3.1, namely that you need a comercial client for AFS. Now, either Win 3.1 or FreeBSD (or Linux, or NetBSD, or...) will connect to the ethernet and give you internet access, and telnet access, and whatnot. But, not AFS. If all you want it dialup, FreeBSD would work great.
See http://www.stacken.kth.se/projekt/arla/ for a project which is putting together a free implementation of AFS for FreeBSD, and other systems. Looks to be fairly early in its development, and I haven't tried it.
last time i checked, the linux kernel had built-in AFS support?
Complete information on the U-M network in the residence halls can be found on the ResComp website at http://rescomp.umich.edu/ The ResComp Networking Guide is available for reading online or printing in PDF format. Minimum hardware and software requirements are included in this guide. Your 386 would be allowed to connect to the network, but it would be unsupported. ResComp requires a Pentium-class or PowerPC machine with Windows 95 or newer or MacOS 7.6.1 or newer to qualify for support. A hard copy version of the Guide was distributed at summer orientation. If you have any questions about the residence halls network you can e- mail resnet@umich.edu
Response not possible - You must register and login before posting.
|
|
- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss