Has anyone experienced this? Some time after I've checked the newsgroups 
on news.povray.org (up to an hour later), ZoneAlarm detects that 
news.povray.org (204.213.191.226) tries to access ports 1070 and 1066 
(and several others, but those are the only two in my current log) on my 
computer. None of the port lists I've checked with mention that these 
ports are assigned to anything. I'm using Netscape 7.1 (although I 
believe that this happened with earlier versions - 4.78 and 7.0 - I 
bypassed 6.0) and it seems to happen only if I keep Netscape running. As 
long as ZoneAlarm blocks the access, I'm not too worried, but I am 
curious as to what is going on.

Post a reply to this message

Tim Riley <tim### [at] netscapenet> wrote in news:3f30388b$1
@news.povray.org:

> Has anyone experienced this? Some time after I've checked the newsgroups 
> on news.povray.org (up to an hour later), ZoneAlarm detects that 
> news.povray.org (204.213.191.226) tries to access ports 1070 and 1066 
> [...]

Probably just the news server timing out your connection.  Some news 
servers have a default timeout of one hour.

When you connect as a client to a news server (or any other server for that 
matter), your PC picks an available port to which the server can send data.  
You connect to a server's service port, but to send data back to you, the 
server needs a client port to send it to.  These client ports are 
arbitrary.  So while you might connect to the nntp port (119, I think) on 
the server, the server sends you back data on an available port selected by 
your PC (usually higher than 1023 (the "well known ports")).

Post a reply to this message

In article <3f30388b$1@news.povray.org> , Tim Riley 
<tim### [at] netscapenet>  wrote:

> Has anyone experienced this? Some time after I've checked the newsgroups
> on news.povray.org (up to an hour later), ZoneAlarm detects that
> news.povray.org (204.213.191.226) tries to access ports 1070 and 1066
> (and several others, but those are the only two in my current log) on my
> computer.

You connected to the sever and left the connection open.  It is about to be
closed by the server because your client is blocking that server resource
for too long without doing anything (not nice).  So the server you are
connected to has to tell your client that the connection will be terminated.
ZoneAlarm just picks this up and generates a false message.  Report it as a
bug to the developers of ZoneAlarm.  It should not report such things
because they are simply the proper way to end a connection that was left
open.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich wrote:
> You connected to the sever and left the connection open.  It is about to be
> closed by the server because your client is blocking that server resource
> for too long without doing anything (not nice).  So the server you are
> connected to has to tell your client that the connection will be terminated.
> ZoneAlarm just picks this up and generates a false message.  Report it as a
> bug to the developers of ZoneAlarm.  It should not report such things
> because they are simply the proper way to end a connection that was left
> open.

Makes sense, however, I don't see the same thing from any of the other 
news servers I frequent. Maybe they don't time-out, or their time-out 
values are longer than I'm on the computer. I don't think that it is a 
bug in ZoneAlarm. It doesn't try to judge the validity of any accesses; 
it's up to me to decide what access I want to allow. I'll trust 
news.povray.org and put it on ZoneAlarm's trusted list.

Thanks for the reply.

Post a reply to this message