home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip
- Path: sparky!uunet!spool.mu.edu!darwin.sura.net!aplcen.apl.jhu.edu!wb3ffv!fallst!tkevans
- From: tkevans@fallst (Tim Evans)
- Subject: Re: PCS WITH DUPLICATE TCP ADDRESSES
- Message-ID: <1992Dec19.135454.548@fallst>
- Reply-To: tkevans@eplrx7.es.dupont.com
- Organization: Tim Evans
- References: <1992Dec19.000209.1@kean.ucs.mun.ca>
- Date: Sat, 19 Dec 1992 13:54:54 GMT
- Lines: 23
-
- wayne@kean.ucs.mun.ca writes:
-
- >I am using CMU TCP on a VAX running VMS. I am telneting to this vax from
- >PC's using Kermit 3.11 ( which has built-in telnet ).
-
- >Many times pc users copy the kermit file from their pc around to other
- >machines. One of the files they copy is mskermit.ini that has the tcp
- >address of the person's pc. When that file is copied, the receiving machine
- >also gets the tcp address of the copying machine. And on it goes. Sometimes
- >a whole lab of pc's gets the same tcp address. The network dies a slow
- >death.
-
- >My question is " Is there a way to prevent a pc from accessing the network
- >if there is already a pc on the network at that moment with the same tcp
- >address as the one attempting access ?
-
- If kermit supports use of 'bootp' (I don't know if it does), you can
- use it to control IP addresses from a central server. This works on
- a real network. You can get UNIX bootp from CMU.
- --
- UUCP: {rutgers|ames|uunet}!mimsy!wb3ffv!fallst!tkevans
- INTERNET: tkevans%fallst@wb3ffv.ampr.org
- Tim Evans 2201 Brookhaven Ct, Fallston, MD 21047
-