RE: Windows EPICS problem - PROBLEM SOLVED

[Emmanuel Mayssat <emmanuel_mayssat@lynceantech.com>]

Mark,

If I understand correctly the GigE camera comes with a network stack
that catches/filters the incoming packets.

VPN software works similarly.
VPN software needs to be configured to know whether to redirect a packet
over the VPN or not(filtering rule). I assume that your GigE camera
network stack needs to be configured as well. 
Do both of the windows computers you are talking about connect to the
same camera (same IP address) and use exactly the same filtering rules?

If so, then I am clueless ;-)

On Fri, 2008-04-11 at 14:37 -0500, Mark Rivers wrote:
> I figured out the source of the problem, but I don't understand it.
>  
> I had installed a packet filter from Prosilica for their GigE Vision cameras.  That filter is intercepts GigE Vision packets before they reach the Windows TCP/IP stack for efficiency, but passes everything else on.  When I just uninstalled that packet filter channel access then behaved normallly.  When I installed it again channel access went back to the behavior where I had to add localhost to EPICS_CA_ADDR_LIST.
>  
> What is strange is that on another Windows machine I also have the packet filter installed, and channel access works fine. That is the computer 164.54.160.38 for which I had also included the route print on my last message.  The only difference I can see is which Ethernet chip set is being used.
>  
> Anyway, I can work around the problem by adding local host to EPICS_CA_ADDR_LIST.  The benefits of the packet filter outweigh the annoyance.
>  
> Mark
>