dunigan@THDSUN.EPM.ORNL.GOV (Tom Dunigan 576-2522) (01/17/91)
we're trying to figure out what service is broadcasting on UDP port 60000. It's coming from an SCO Xenix engine with Lachman TCP/IP. thanks
cliffb@isavax.isa.com (cliff bedore*) (01/18/91)
In article <9101162103.AA12082@thdsun.EPM.ORNL.GOV> dunigan@THDSUN.EPM.ORNL.GOV (Tom Dunigan 576-2522) writes: >we're trying to figure out what service is broadcasting on >UDP port 60000. It's coming from an SCO Xenix engine >with Lachman TCP/IP. >thanks What I've been told is that SCO is broadcasting their license number so that if another host hears its license number it will "shut down" tcp in some manner. Its apparently a copy protection scheme. Cliff
urlichs@smurf.sub.org (Matthias Urlichs) (01/19/91)
In comp.protocols.tcp-ip, article <9101162103.AA12082@thdsun.EPM.ORNL.GOV>,
dunigan@THDSUN.EPM.ORNL.GOV (Tom Dunigan 576-2522) writes:
< we're trying to figure out what service is broadcasting on
< UDP port 60000. It's coming from an SCO Xenix engine
< with Lachman TCP/IP.
It looks like they are trying to verify the uniqueness of their serial number.
Nothing you can do about it, I'm afraid...
--
Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\
Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(0700-2330) \o)/ericd@sco.COM (Sharky the Lanshark) (01/21/91)
In article <i1kbh2.=28@smurf.sub.org> urlichs@smurf.sub.org (Matthias Urlichs) writes: >< we're trying to figure out what service is broadcasting on >< UDP port 60000. It's coming from an SCO Xenix engine >< with Lachman TCP/IP. >It looks like they are trying to verify the uniqueness of their serial number. Correct.. >Nothing you can do about it, I'm afraid...S Close, it is possible to obtain a patch that will reduce how often the Copy Protection Daemon (CPD) bradcasts to the network. Details below: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Eric Davis () INTERNET -=> ericd@sco.COM Technical Support Engineer II () UUCP -=> {uunet|sun|att|ucsc}!sco!ericd (Lanshark Support Team) () VOX -=> US + 408 425 7222 () FAX -=> US + 408 427 5443 () TWX -=> 910-598-4510 sco sacz () HOME -=> ericd@bumby.santa-cruz.ca.US The Santa Cruz Operation, Inc. ()=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 399 Encinal Street () "We are the people our parents warned us Santa Cruz, California 95061 () about" -Jimmy Buffett attn: ericd () #include <legal/network/disclamer.h> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Periodic network traffic on port 60000 causing unwanted network load. KEYWORDS: cpd daemon port 60000 network broadcast traffic unwanted load sls lng248 RELEASE: SCO TCP/IP Release 1.0.1 for SCO XENIX PROBLEM: The copy protection daemon, cpd, periodically checks the network for copy protection violations. Unfortunately, this places an unwelcome load on the network. SOLUTION: Support Level Supplement (SLS) lng248, installs a new cpd daemon that checks for copy protection violations less often. This SLS is only for SCO TCP/IP Release 1.0.1. Note that the same problem occurs with the cpd daemon for SCO TCP/IP Release 1.1.1 under SCO UNIX System V/386 and for the SCO TCP/IP included with Open Desktop Release 1.0.0. For these releases, SLS lng227 addresses the cpd problem.
ronald@robobar.co.uk (Ronald S H Khoo) (01/21/91)
urlichs@smurf.sub.org (Matthias Urlichs) writes: > < we're trying to figure out what service is broadcasting on > < UDP port 60000. It's coming from an SCO Xenix engine > < with Lachman TCP/IP. > It looks like they are trying to verify the uniqueness of their serial number. > Nothing you can do about it, I'm afraid... Depends on what you mean by "do about it". You can't avoid running /etc/cpd, the CoPyrightDaemon which broadcasts on udp.60000, but you can get a version of cpd that only does it at startup. Someone probably informed SCO that the broadcasts make IP over pieces of wet string rather less useable. Support Level Suppement lng227 applies to SCO Unix TCP/IP and lng248 applies to SCO Xenix TCP 1.0.1 (the release version). Both are available for anon UUCP from sosco or scolon. Obviously you can get them from SCO Support as well... Disclaimer: I haven't actually tried them, though. -- Ronald Khoo <ronald@robobar.co.uk> +44 81 991 1142 (O) +44 71 229 7741 (H)
tom@rsp.UUCP (Thomas Ruf) (01/21/91)
dunigan@THDSUN.EPM.ORNL.GOV (Tom Dunigan 576-2522) writes: >we're trying to figure out what service is broadcasting on >UDP port 60000. It's coming from an SCO Xenix engine >with Lachman TCP/IP. >thanks The "service" in question is their copy protection scheme. Thomas -- Thomas Ruf tom@rsp.de Schneider & Koch GmbH Schneider & Koch, Inc {uunet,mcvax}!unido!rsp!tom Germany Palo Alto
larryp@sco.COM (Larry Philps) (01/21/91)
In <1991Jan18.120021.21189@isavax.isa.com> cliffb@isavax.isa.com (cliff bedore*) writes: > In article <9101162103.AA12082@thdsun.EPM.ORNL.GOV> dunigan@THDSUN.EPM.ORNL.GOV (Tom Dunigan 576-2522) writes: > >we're trying to figure out what service is broadcasting on > >UDP port 60000. It's coming from an SCO Xenix engine > >with Lachman TCP/IP. > >thanks > > What I've been told is that SCO is broadcasting their license number so that > if another host hears its license number it will "shut down" tcp in some > manner. Its apparently a copy protection scheme. It is the networking copyright daemon, /etc/cpd. It is indeed broadcasting serial numbers. Early versions did shut down networking if somebody broadcast a duplicate serial number. For some reason that was not popular :-) Anyway, newer versions just print nasty messages when that happens. Networking does not shut down. --- Larry Philps, SCO Canada, Inc (Formerly: HCR Corporation) Postman: 130 Bloor St. West, 10th floor, Toronto, Ontario. M5S 1N5 InterNet: larryp@sco.COM or larryp%scocan@uunet.uu.net UUCP: {uunet,utcsri,sco}!scocan!larryp Phone: (416) 922-1937 Fax: (416) 922-8397
HAROLD@UGA.CC.UGA.EDU (Harold Pritchett) (01/23/91)
>< we're trying to figure out what service is broadcasting on >< UDP port 60000. It's coming from an SCO Xenix engine >< with Lachman TCP/IP. > >It looks like they are trying to verify the uniqueness of their serial number. > >Nothing you can do about it, I'm afraid... There is always something you can do about it. Send the software back and refuse to ever do business with a company which resorts to this sort of crap. And be sure to let them know how you feel about this. Harold
fin@UNET.UNET.UMN.EDU ("Craig A. Finseth") (01/23/91)
>< we're trying to figure out what service is broadcasting on >< UDP port 60000. It's coming from an SCO Xenix engine >< with Lachman TCP/IP. > >It looks like they are trying to verify the uniqueness of their serial number. > >Nothing you can do about it, I'm afraid... There is always something you can do about it. Send the software back and refuse to ever do business with a company which resorts to this sort of crap. And be sure to let them know how you feel about this. You can also point out that the larger the network, the more trouble these schemes will cause. Hence, they will alienate their largest (potential) customer base: hardly good business practices! (There is a long list of vendors whose products do not function here because they were designed for "large" networks of 10-20 users: our network has many thousands of hosts. In one fell swoop, the vendors have prevented themselves from selling thousands of copies.) Craig A. Finseth fin@unet.umn.edu [CAF13] University Networking Services +1 612 624 3375 desk University of Minnesota +1 612 625 0006 problems 130 Lind Hall, 207 Church St SE +1 612 626 1002 FAX Minneapolis MN 55455-0134, U.S.A.
lucio@proxima.UUCP (Lucio de Re) (01/25/91)
In article <13743@scorn.sco.COM> ericd@sco.COM (Sharky the Lanshark) writes: > >In article <i1kbh2.=28@smurf.sub.org> urlichs@smurf.sub.org (Matthias Urlichs) writes: >>< we're trying to figure out what service is broadcasting on >>< UDP port 60000. It's coming from an SCO Xenix engine >>< with Lachman TCP/IP. >>It looks like they are trying to verify the uniqueness of their serial number. > >Correct.. > >>Nothing you can do about it, I'm afraid...S > >Close, it is possible to obtain a patch that will reduce how often >the Copy Protection Daemon (CPD) bradcasts to the network. > >SOLUTION: Support Level Supplement (SLS) lng248, installs a new cpd daemon > that checks for copy protection violations less often. > This SLS is only for SCO TCP/IP Release 1.0.1. Any reason one can't merely unload the cpd (kill -9)? Lucio de Re ...uunet!ddsw1!proxima!lucio -------------------- plan to throw THIS one away -- lucio@proxima.UUCP