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: Ben Franksen <benjamin.franksen@helmholtz-berlin.de>
To: <freddie.akeroyd@stfc.ac.uk>, <tech-talk@aps.anl.gov>
Date: Sun, 15 Jan 2017 03:37:22 +0100
Am 12.01.2017 um 19:04 schrieb freddie.akeroyd@stfc.ac.uk:
> I've had instances of both an IOC and a CAS being unable to create a
> channel access port. The servers attempt to bind to the usual channel
> access server port number, but rather than EADDRINUSE being returned
> on failure they are seeing EACCES. Looking at
> https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx
> 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). If I change things to request a dynamic port allocation after
> any bind() failure (rather than only on EADDRINUSE) as per the
> attached patch then everything works fine

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.

Cheers
Ben

Attachment: signature.asc
Description: OpenPGP digital signature


Replies:
Re: CA server bind failure on Windows Ralph Lange
References:
CA server bind failure on Windows freddie.akeroyd

Navigate by Date:
Prev: Re: ASYN VXI-11 Ben Franksen
Next: Re: Problem with parallel make with seq 2.2.4 on Linux Ben 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
Navigate by Thread:
Prev: CA server bind failure on Windows freddie.akeroyd
Next: Re: CA server bind failure on Windows Ralph Lange
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 ·