EPICS Home

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>  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: Benjamin Franksen <[email protected]>
To: EPICS Tech Talk <[email protected]>
Date: Mon, 16 Jan 2017 13:59:51 +0100 
On 15.01.2017 19:01, Ralph Lange wrote:
> Hi Ben,
> 
> On Sun, Jan 15, 2017 at 3:37 AM, Ben Franksen <
> [email protected]> wrote:
> 
>> 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.
> 
> 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.

Oops. Sorry... (to NI, mostly).

Cheers
Ben
-- 
"Make it so they have to reboot after every typo." ― Scott Adams

Attachment: signature.asc
Description: OpenPGP digital signature

References:
CA server bind failure on Windows freddie.akeroyd
Re: CA server bind failure on Windows Ben Franksen
Re: CA server bind failure on Windows Ralph Lange
Navigate by Date:
Prev: Re: Asyn and devices with changing register map Dirk Zimoch
Next: Support for Rigol DSA815 spectrum analyzer? [RF-128] Konrad, Martin
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 
Navigate by Thread:
Prev: Re: CA server bind failure on Windows Ralph Lange
Next: Re: CA server bind failure on Windows Andrew Johnson
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