TCP/IP lan setup setup howto:
This howto will tell you how to install a TCP/IP Network Lan
with (dotted).Quad Numbers and a simple Plan to follow.
ASSUMPTION:
1.) That you have Network Cards installed in each Machine.
2.) That they are Connected either ...
2.a) By a thin Ethernet Cable with 'T' Connectors and both ends of the run Terminated.
2.b) Or are you're using a Hub; with some form of twisted pair cabling
connecting all the machines in a star fashion.
3.) And are able to see the Drives of each of the Machines on your Network.
via whatever Protocols you have installed (Netbios) or (IPX) it doesn't matter.
NOTE: YOU DON'T HAVE TO REMOVE THEM TO INSTALL THE TCP/IP PROTOCOL.
They all sit next to each other - so If you use IPX to play Doom on your Network
you still will after the TCP/IP protocol is installed.
START:
TCP/IP or Transmition Control Protocol (and)/ Internet Protocol
isn't quite a scarey as they make out!
To set up a TCP/IP Networked Lan you don't need to read a Huge Book on the subject either.
To set it up on your computer(s) do the following.
In Windows 3.11 - eMail me at the bottom I can help!
In Windows 95 and 98.
To Install the TCP/IP protocol.
"LEFT" click on 'Network Neighborhood'
goto 'Properties'
If you see TCP/IP its already there. If not click on the 'ADD Button'
You'll be presented with a window that says 'Select Network Component Type'
click on 'protocol'
click ADD - another pops up Window 'Select Network Protocol'
click down to 'Microsoft' the Window on the right will show
IPX/spx
Microsoft 32bit DLC
Microsoft DLC
NetBEUI
and finally TCP/IP
Click OK after you've highlighted this option - It's installed!
and it will be bound to the Network adapter that your other
protocols use.
Double click on TCP and up pops a Window/Box:
The first TAB highlighted 'IP Address' is what we want
because those two options are discussed below ...
BEGIN:
There are several Quad Categories in the IP realm that are used for private networks.
A Quad Number is just that 'xxx.xxx.xxx.xxx' a Quad Set of Numbers.
The FRONT:
The 192.168.('x'.'x') bit is the front part of the Quad we're allowed to use.
The MIDDLE:
192.168.0.x and it goes up to
192.168.255.x
notice the numbering 0 -> 255.
The 0 -> 255 is a group identifier;
so your network at home/office in our example would be .100.
could be anything from 0 to 255 but we're using 100
you stick with this number.
it's your network number.
and it never changes. [for the sake of this example]
The END:
In all these cases .x. is the number you give [ a ] machine on your network.
ie: 1,2,3,4 in our example were using 2,4,6,8,10 you can use ANY number from 0 to 255
*but* don't use 0 or 255
1.) A matter of politics and
2.) Some Software doesn't like those Two Numbers used on a TCP/IP Lan.
So you can have 254 Machine's on One Group. (includes 0) total ip numbers = 256:
This just is one set, 192.168.100.'x' and it's what we're going to be using.
On this Lan there are 5 Machines - called ...
vPop machine (ip quad number is) 192.168.100.2
_Dad machine (ip quad number is) 192.168.100.4
_Mum machine (ip quad number is) 192.168.100.6
Girl machine (ip quad number is) 192.168.100.8
_Boy machine (ip quad number is) 192.168.100.10
All the these Machines use the same Subnet Mask of 255.255.255.0
Note: It's used by some software to broadcast messages to a TCP/IP group like
'server shutting down now' -( Unix Terminals! )-
Remember that pop up Window/Box? - Now click the option 'Specify an IP Address [x]'
And enter the quad numbers you've decided to give this machine from the information above.
^^^^
now do it on all the other machines in your network.
^^^ ^^^^^
giving them the diffrent quad numbers you've decided to use.
Now when it comes to testing a TCP/IP Network Lan just logging onto ...
... the Remote Machine Drives isn't sufficient!
You have to test a TCP/IP network by sending packets of data to other TCP/IP Machines.
and TCP/IP Programmes listen to ports:
Vsocks listens to port 1080:
while Vpop3 listens to port 25: for SMPT outgoing.
and port 110: for Mail incoming.
THE TEST:
In a DOS BOX at what ever prompt you on type 'ping 192.168.100.1' and press
the 'Enter key' you should receive lots of cryptic information ...
such as ... if you've got it wrong:
C:\WINDOWS>ping 192.168.100.2
Pinging 192.168.100.2 with 32 bytes of data:
Destination specified is invalid.
Destination specified is invalid.
Destination specified is invalid.
Destination specified is invalid.
Ping statistics for 192.192.100.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
or; if you got it right you should see this ...
C:\WINDOWS>ping 192.168.100.2
Pinging 192.168.100.2 with 32 bytes of data:
Reply from 192.168.100.2: bytes=32 time=3ms TTL=128
Reply from 192.168.100.2: bytes=32 time=1ms TTL=128
Reply from 192.168.100.2: bytes=32 time=2ms TTL=128
Reply from 192.168.100.2: bytes=32 time=1ms TTL=128
Ping statistics for 192.168.100.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 1ms
Vpop3 is now ready to talk to eMail clients and eMail clients can talk to vPop3.
BUT - setting up of eMail clients is another story ...
<< eof >>
Hope it helped a little bit