From: Ingo P. <in...@it...> - 2005-09-13 14:15:32
|
On Tue, 13 Sep 2005, Ed Kasky wrote: > On Tue, 13 Sep 2005, Ingo Preiml wrote: > >> On Tue, 5 Jul 2005, Ed Kasky wrote: >> >>> > # pyzor ping >>> > 66.250.40.33:24441 TimeoutError: >>> > [root[# pyzor discover >>> > downloading servers from >>> http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x >>> > [root]# pyzor ping >>> > 66.250.40.33:24441 TimeoutError: >>> > [root]# >>> > >>> > What is wrong ? >>> > Looks like this has been the case since June 23rd. >>> >>> Looks good from this end: >>> $ pyzor ping >>> 66.250.40.33:24441 (200, "OK") >>> >>> Maybe a firewall issue? >> >> >> But tracepath 66.250.40.33/24441 did not succeed with the following >> output: >> >> 15: Quatro_Systems.demarc.cogentco.com (66.250.4.54) asymm 20 >> 116.956ms >> 16: no reply >> 17: no reply >> ---- snip ----- >> >> Is this a firewall problem on my local network or on 66.250.4.54? Am >> I doing >> something wrong? > > > Hard to say not knowing your setup. Is there a firewall installed and > if so if all outbound traffic is not trusted, have you allowed inbound > traffic on 24441? > > Also, can you do a successful "pyzor ping"??? > Oh dear, I am sorry to tell you that I had made a mistake. I have two mailserver (a productive server and a test system) that are in different networks. The test system is in a subnet with very restricted access to the internet and the productive server is located in our DMZ. I had no access from my test system and so I supposed (without checking :( )the productive server has no access too... But as I tried pyzor ping on my productive one, it says: 66.250.40.33:24441 (200, 'OK') So everything works fine for me, only the test system has no access, but that is not very important. Sorry and thanks for the quick reply. Ingo Preiml |