Re: The esoteric art of LANS
Micom 2000 said:
I have a huge book called Windows NT server, a whole set of SCO, and somewhere here a book called LANs for Dummies, and a video included with WFW on LAN hookup with token ring cards in a "star" or "hub" set-up. My NEXT documents garble about NTSF. I even have an Ethernet Hub.
Do you mean NTFS? instead of NTSF? NTFS OR (New Technology (NT) File System (FS))
Is used on windows NT, 2000 & XP
it's a pretty good file system much better then FAT12,16,32 however it's
a real pain to do anything with it under dos so it's best to use fat 16 for
anything you might need underdos & winnt - xp
however you run into problems with large disk's under dos.
it's best to keep dos on it's own computer.
NTFS is used for storing files on your hdd and has next to nothign to do
with networking.
im unsure what you are trying to do. there are all
kinds of different network hardware and protocols plus each OS is diff.
are you wanting to connect your atari , commodore , windows & linux pc's
all up to one network? well im sure it can be done but im also sure it would
be a pain.
windows for workgroups 3.11 -> xp is pretty simple dos can be networked
too with a little extra effort, linux is built for networking as well but with linux
if you have odd ball hardware it might be harder to find a working driver
as there is'nt as wide a support for devices on linux. It does not help that
manufactures wont release informatin about there cards so it takes longer
for someone too write one and even then it's not always 100% still it's not
as bad ad you would expect.
as far as networking hardware goes if i can't get ethernet working it dont
get networked i got rid of (small) collection of tokenring crap.
ethernet is simple, fast & flexable, not to mention affordable.
really hardware wise all you need to connect two computers is for each
to have there own cards & a single cable (crossover) if you need to
connect more then 2 computers you'll need a hub (you already have)
or a switch. Switch is just like a hub but better in every single way.
if you hook up to a hub make sure you use (straight through) cable (the most common).
here's a link that will illustrate what i mean (
http://www.cabletron.com/support/techtips/tk0231-9.html)
the bigist problem is making sure your OS can handle the network
like i said windows, linux have no problem, dos can be done too.
atari & commodores im sure someone has done before but i have'nt a clue.
all the computers in the network will need to use the same protocol (language)
to talk to each other the most common is tcp/ip it's what you use on the
internet and it's very flexable. however older machines do not always have this newer protocol you
might have to settle on IPX. it's possible to have your windows & linux machine
run this as well and at the same time so they can talk to older machines
and still talk to the newer machines in tcp/ip
Micom 2000 said:
I usually freeze when the program calls for my NIC address and I don't proceed from there since the ethernet card gives very little indication of what my address should be, and since it's not on the INET, would it conflict with a proper INET address.
NIC address's if you are talking about hardware then that would be called your MAC address (Media Access Control)
the only thing you need to know is what it is.. write it down.
dont worry about conflicts because it rarly matters they are all unique.
if you are talking about your IP address then you can have this setup
by DHCP server but it's prob easier to just set them up your self in a small
lan. you can use several different blocks that are set a side for private use
private use is address you can use in your own lan that arent used on the
internet there for there will be no conflicts with routing and such.
the ranges are:
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255
i use the 10.x.x.x range however any will do. this really only matters
if your lan is at somepoint somehow connected to the internet
you can use what ever ip you want there is no law however it's good practice to use private ranges.
for a subnet i use a subnet of 255.255.255.0
subnet just tells your system how many computers it will try to contact
before routing it also does some other minor stuff too but you really dont need to
know unless you want to. with that subnet your machine will contact
255 hosts directly.. should be more then enough for any thing you might
throw at it.
here's a small page about ip's and subnet's (
http://www.ralphb.net/IPSubnet/)
so for example the wired part of my lan i use 10.0.0.x with a subnet of 255.255.255.0
so i can access all computers on 10.0.0.x directly except 10.0.0.255 thats
a ip used for broadcasts (broadcast being all computers see this traffic even on a switch)
if i want to access the internet or anything beyond my subnet for that matter
it will need to be routed using a router/gateway.. router is just a middle man.
the router has a ip address on both networks 10.0.0.x and internet.
really the internet is nothing more then a very very very large collection
of networks linked together in fact just accessing this website my request
prob went though 15-30 routers not including my own
CP/M User said:
Terry Yager said:
There's really nothing to be afraid of these days.
That's the problem these days, it's all too easy - which is why I'm all out in regards to new computers. Bill Gates has said we'll eventually catch up for the dumbo's, well not literally, though through his actions.
Hmm well i can understand where thats comming from i dont like fighting
with the computer but at the same time i dont like to be herassed by the machine
about stupid crap (Win XP). i like taking the short route but i also like to know
how to do it by hand if i need too.
CP/M User said:
That's the other thing which bugs me about Kids, why employ some slightly older person to use a computer, when some Kid can come along & get paid half the price & do twice as much with a computer?
Define kid's are you talking about high school students or kid's as in fresh out of ITT
or some other place? Or do you just mean kid's as in young? people have to start somewhere.
if the company is going to hire a "kid" as in little / no exp. as a full time or as the only administrator
then it is the companies fault when they have problems not the "kids"
The "kid" is prob just trying there best they ask for a job the company is
the one that gave them something over there heads.
CP/M User said:
I think now that being stuck on a computer all day long, would be quite boring.
i agree somewhat you gotta break it up a little.
but i still would like having a job with lots of computer time, and oh god casual dress is a must.
CP/M User said:
Sure I used to think it'd be nice, but technology changes, users change, software changes & it's better to find something else anyway - since computers are used everywhere, any new job would involve using one at some stage.
thchnology/software changes, users remain the same
oh ya gotta love them users always bugging you about dumb simple shit.
"i think i need a new computer my keyboard wont work" why dont you try pluging it in.
CP/M User said:
All of a sudden that Network Administrator sounds like a boring job to have! ;-)
sounds like a stressfull existance if you ask me. all those users bugging you about dumb simple shit.
the boss breathing down your neck about crap that he wants done when he
snaps his fingiers. jump dog jump, sit, sit i say, fetch go fetch, Now grant me 3 wishes. lol
vbriel said:
It's one thing to be able to set up a cute 3-5 PC network in your house with WiFi. It's another to set up and maintain 2-500 user systems.
lol i pitty the fool who uses wifi for network backbone