1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 <2017> 2018 2019 2020 2021 2022 2023 2024 | 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> 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: CA server bind failure on Windows |
From: | Ralph Lange <[email protected]> |
To: | Ben Franksen <[email protected]> |
Cc: | EPICS Tech Talk <[email protected]> |
Date: | Sun, 15 Jan 2017 19:01:39 +0100 |
Am 12.01.2017 um 19:04 schrieb [email protected]:
> [...] 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.