I have a wireless home network with
two computers, sharing files, printer, and internet connection using a Linksys wireless broadband router. Both computers run ZA.
The computers share appointment calendars for read-only using a product call Active Desktop Calendar (ADC) and shoulder-tap one another every so often to syncronize the two calendars. One of these two computers also occasionally connects to a third computer using VPN, totally unrelated to ADC.
When the one computer is not attached to the VPN,
ADC communicates with the other computer using a real adapter at IP 192.168.1.100/255.255.255.0 and the ZA firewall on the second computer permits the traffic. The second computer has '192.168.1.1/255.255.255.0' in its ZA "trusted zone". Note this is '192.168.1.1', not '192.168.1.100'. When the first computer is attached to the VPN, for some reason ADC chooses to communicate with the second computer using the virtual adapter at IP10.0.0.251/255.0.0.0. This traffic is blocked by the second computer.
I have
four questions:
1) Why does 192.168.1.100/255.255.255.0 match the ZA trusted zone address of 192.168.1.1/255.255.255.0?2) What IP/subnet do I need to add to the second computer's trusted zone for the virtual adapter at IP10.0.0.251/255.0.0.0 so that that ADC traffic is not blocked?3) Is there a risk to permitting traffic across this VPN adapter to the second computer?
4) This is probably not the right place for this question, but how/why would ADC use the virtual adapter at all? The real adapter is still there. I don't configure ADC for this traffic, so I don't think there is an option for me to specify a specific adapter. I will probably need to check with the ADC vendor; I would like to not have to permit the VPN traffic if it heightened the risk of VPN in general.
TIA,
Phil