Re: without selecting the right interface communication won't work ?

From: David (davidwnh_at_adelphia.net)
Date: 10/27/03


Date: Mon, 27 Oct 2003 22:50:42 GMT

Zone alarm does not open the ports. When you use netstat or similar to
look at sockets this is a representation of the OS and not the firewall.
 So a socket showing 0.0.0.0 means the OS is listening on all adapters
for traffic for that UDP port. This has nothing to do with the settings
of your firewall. You firewall operates separately from this aspect of
the OS. In order to get things to work with ZA you will have to
configure it to either explicitly allow it to pass unsolicited traffic
for UDP on the specific port(s), or lower your security setting so that
it is allowed. I think the lower security settings only pertains to the
high ports(not sure don't use it)so this would have to be the case. You
will also have to accept incoming unsolicited traffic for the specific
application when you receive the alert from ZA for the application
executable.

>
> In this scenerario communication won't work with UDP.
>
> Computer 1 <-> Computer 2
>
> Both computers have zone alarm pro 4 firewall.
>
> Each computer opens a udp port/socket with interface address set to any
> address and interface port set to any port.
>
> Once they are opened the user sets the destination address and destination
> port on both computers to match the address and port selected by winsock/the
> system.
>
> After winsock has opened the sockets... both interface addresses are still
> 0.0.0.0 ???
>
> What happens is one of the firewalls blocks the traffic. ( At computer 2
> that has 2 network cards )
>
> Zone alarm pro firewall will say it blocked the traffic. ( routed ? )
>
> Any idea what is going on here ?
>
> Why does zone alarm pro firewall block it... first it seems zone alarm opens
> the port... but when something is received it will still block it ?
>
> Skybuck.
>
>



Relevant Pages

  • Re: Port scanning?
    ... I am running both Zone Alarm and the XP firewall. ... the log when a port is opened while XP firewall also logs the port closure ... Anyway, now when I have disabled the network access of that process, the ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Constant Hacking Attemps - Pacific Bell DSL customer
    ... I use ZoneAlarm Pro as a for Firewall and just ... >What is Zone Alarm NOT protecting? ... >Port: 139 ... port doesn't mean that a probe of that port is an "attack". ...
    (comp.security.firewalls)
  • Re: ZoneAlarm blocks FTP apps
    ... > are accepted) but then it prevents the remote file listing from showing in FTPX's pane. ... FTP connects on a "control" port, to exchange IDs/password, ... Turn on the Windows XP Firewall, and turn off the Zone Alarm firewall. ...
    (comp.security.firewalls)
  • Re: Zone Alarm Pro and Outlook Web Access thru IE6
    ... With IE 6 I had the similar problem, in conjunction with zone alarm. ... additional firewall like ZA is neccessary. ... >> using IE (See error message below). ... >> The guy who administers our network says I need to open "Port 8080 ...
    (comp.security.firewalls)
  • Re: Zone Alarm Pro and Outlook Web Access thru IE6
    ... With IE 6 I had the similar problem, in conjunction with zone alarm. ... additional firewall like ZA is neccessary. ... >> using IE (See error message below). ... >> The guy who administers our network says I need to open "Port 8080 ...
    (comp.security.firewalls)