networking doubts

[computernetworking]

tell me about networking?
what is the abbrevation for nt?
explain about the basic networking concepts.

 

[gunthnp]

what part, there is much out there that come under networking, tcp/ip, do you want to peer to peer, phones, the internet, etc. Well I'll just start with a little start info of hwo it got started and hope we can go from there the internet use a protocal called TCP/IP (which now most networks use today.) it came out in the 70's by joint work at berkly and cambrige which was later used by the milltary for the avernet which became the internet.

the the 80's there where tons of network types we had novell, token ring by ibm, local talk, lantastic,and ethernet the two that made it into the 90's where ethernet and token ring and now days it is manly ethernet out there. that in a nut shell is the start So long and thanks for all the fish.

 

[pbwarrior]

This is such a broad question that it is impossible to answer in this format. Depending on your experience there are various books available on any form of networking you use.

There is one I lend to people starting out. Networking For Dummies. This book is a starter for Win 98, Win 2K, and Novell Netware. In spite of the titles the Dummie series of booke are helpful


Good Luck!

 

[gunthnp]

nt now stand for Newer technogly it was the name of the company microsoft took nt from.

So long and thanks for all the fish.

 

[edfair]

IBM ,while marketing OS2, called it "NICE TRY". But that was before it got stable. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[CitrixEngineer]

I tend to call NT No Thanks, but that's just my sense of humour

Basic Networking Concepts:

You need

1) At least 2 computer class devices (this can include laptops, Palm Pilots or whatever)

2) A hardware port capable of two-way communication fitted to each device (eg, an NIC, a parallel port or a serial port).

3) A suitable cable to connect these ports (eg Cat 5).

4) Software to allow the Operating System on the device to communicate with the port (eg NIC driver).

5) Software to allow the devices to communicate using an agreed set of rules (protocol) (eg TCP/IP).

6) Software to allow you to perform data transfers using the protocol (ftp, telnet, file sharing, etc)


Of course, if you've got a bigger network, you'll get into a situation where it's more efficient to split the devices into smaller, more manageable groups (eg subnets), and you'll use devices like hubs, routers and switches to facilitate this. Or you may have users at more than one site, in which case you're looking at a WAN (Wide Area Network). For this you may need modems or some other means of connecting the sites.

The best example of how complex a WAN can be is the Internet.


Networking is such a huge area, with so many different ways of achieving the same thing, that the only way to really get to understand it is to build one yourself, and chat to guys who work with networks about specific issues.

It'll make your head spin at first, with all the new, unfamiliar terms and concepts, but stick with it, if you're interested - it's a fascinating field. I'd recommend getting an old PC (a 486 will do), and set it up as a Linux server. There's not much you can't do with one of these.


Good Luck!

 

[swayda]

Hi. You asked a VERY BIG question, kinda like saying tell me about life. :^) Microcomputer networking was a concept to allow computers to share resources, like expensive printers, and files. They accomplish this by placing a software layer, the network operating system (NOS) between the operating system and applications. The nos intercepts any calls made to the os and determines whether they are meant for the local computer or a networked machine. If it's for the local it relays that call to the os. If a remote then the call is redirected to the appropriate machine. For instance, someone creates a file on their computer and you want to access it, the nos calls the remote machine and calls for the file. The remote machine's nos breaks the file into chunks called packets and sends it through the interconnecting wire. Each packet has a header stating the address of the requesting machine. The way this is accomplished is called protocols, which is a simple way of saying they are speaking a language, but instead of English or French it's tcp/ip, ipx/spx, netbios, SNA etc. Each time a packet is received by the requestor a message is sent back to the remote saying, in effect, ok send another packet. I could keep going but that's the basics. Don Swayser

 

[gunthnp]

if you want to know everything about networking go to

http://www.ietf.org

these are the the pople who make networking look at the rfc's from them you can how things got started and where they are going. So long and thanks for all the fish.