Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
<== Date ==> <== Thread ==>

Subject: Re: CA server bind failure on Windows
From: Ralph Lange <ralph.lange@gmx.de>
To: Ben Franksen <benjamin.franksen@helmholtz-berlin.de>
Cc: EPICS Tech Talk <tech-talk@aps.anl.gov>
Date: Sun, 15 Jan 2017 19:01:39 +0100
Hi Ben,

On Sun, Jan 15, 2017 at 3:37 AM, Ben Franksen <benjamin.franksen@helmholtz-berlin.de> wrote:
Am 12.01.2017 um 19:04 schrieb freddie.akeroyd@stfc.ac.uk:
> [...] suggests another application/service might have bound to the port
> already with SO_EXCLUSIVEADDRUSE and this appears to be the situation
> (the National Instruments network variables server process in this
> case).

This is very nasty behaviour on part of NI. The CA ports 5064 and 5065
are registered with the IANA and officially belong to Channel Access
(both UDP and TCP), see
https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt.

IMO you should file a complaint with NI; they should change their
default port to some unregistered port, perhaps they want to register
their protocol with IANA under another port number, but simply hijacking
an existing registered port is not acceptable.

Careful...
NI's LabVIEW network variables server has a plugin that contains their implementation of the Channel Access server, see http://www.ni.com/white-paper/13865/en/. While their CA server has a couple of flaws and issues and doesn't fully behave like the EPICS CA servers (e.g. by presumably using SO_EXCLUSIVEADDRUSE), using the Channel Access ports for Channel Access is definitely legitimate and recommended.

Cheers,
~Ralph


Replies:
Re: CA server bind failure on Windows Benjamin Franksen
References:
CA server bind failure on Windows freddie.akeroyd
Re: CA server bind failure on Windows Ben Franksen

Navigate by Date:
Prev: RE: Problem with parallel make with seq 2.2.4 on Linux Mark Rivers
Next: Re: Asyn and devices with changing register map Dirk Zimoch
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
Navigate by Thread:
Prev: Re: CA server bind failure on Windows Ben Franksen
Next: Re: CA server bind failure on Windows Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
ANJ, 14 Feb 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·