Path: utzoo!utgpu!watserv1!watmath!att!ucbvax!NSCULTRIX1.NETWORK.COM!dotytr
From: dotytr@NSCULTRIX1.NETWORK.COM (Ted R. Doty)
Newsgroups: comp.protocols.tcp-ip
Subject: (none)
Message-ID: <9102181547.AA06656@nscultrix1.network.com>
Date: 18 Feb 91 15:47:32 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The Internet
Lines: 30

well!bnox%well.sf.ca.us@apple.com posted a message about problems with
TCP configuration on a PC running SCO.  I tried responding to him only,
but the mailer barfed on the address.  So here it is (sorry for
cluttering the ether ...):

Your problem is in the mkdev tcp statement.  The Internet Address is *NOT* the
same as the address printed on the ethernet card (in short, Xerox is the keeper
of the sacred ethernet address space - if you want to sell ethernet stuff, you
buy a block of addresses from them; however, you can assign your own IP
addresses at will (unless you are connecting tothe Internet)).

Fortunately, the solution looks pretty easy - use an IP address like :

                      192.1.164.<host number>

where <host number> is a one-byte address that is not duplicated by any other
host on that net.  Note that *ALL* hosts on that net will have an address of
the form 192.1.164.<something>

There is this magic thing called ARP that takes care of mapping IP addresses
to ethernet addresses, so don't worry about it.

Things should work after this.  OBTW, if you are new to the wonderful world
of TCP/IP, run don't walk to your nearest technical bookstore and score
yourself a copy of "Internetworking with TCP/IP" by Douglas Comer (2nd Ed.)
(Prentice-Hall, 1990, ISBN 0-13-468505-9).  While you'll find that you outgrow
it pretty quickly, it's the best introduction it TCP/IP that I've seen.

- Ted Doty, Network Systems Corporation  phone: +1 301-596-2270