[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20020529: McIDAS ADDE Port Usage

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20020529: McIDAS ADDE Port Usage
  • Date: Wed, 29 May 2002 11:24:15 -0600
>From: "Steven E. McKee" <address@hidden>
>Organization: Lyndon State College
>Keywords: 200205291640.g4TGejp17822 McIDAS ADDE

Steve,

>While configuring the mcadde account on our new server foxfire.lsc.vsc.edu, I 
>found that Port 500 was already assigned in /etc/services as follows:
>
>       pim-rp-disc     496/udp
>       isakmp          500/tcp
>       sakmp           500/udp
>       gdomap          538/tcp
>
>Can I use another Port Number e.g. 501 for the mcadde server Port?

No, you have to use port 500.  The conflict in port usage is a design
weakness in ADDE, but we have to live with it nonetheless.  My
recommendation is to comment out the isakmp entries in /etc/services
(port 500) and also make sure that there is no conflict for port
503.  After making changes in /etc/services and /etc/inetd.conf, you
will need to send a HUP to the inetd process.

Tom Yoksas