Chuck Simmons wrote:
> DeMoN_LaG wrote:
>
>>Holger Metzger wrote:
>>
>>
>>>On 6/10/01 6:20 PM, Chuck Simmons wrote:
>>>
>>>
>>>
>>>>Holger Metzger wrote:
>>>>
>>>>
>>>>
>>>>>On 6/10/01 4:19 PM, Mark wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>After calling Netscape Communications on Friday evening when
>>>>>>Netscape's secured news servers (secnews.netscape.com, port 563)
>>>>>>when it become inaccessible, John from Netscape Communications
>>>>>>informed me that Netscape is no longer interested in continuing
>>>>>>the news server service and has pulled the service. He asked me
>>>>>>if I read the recent news story about Netscape no longer being in
>>>>>>the web browser business. I said Yes and he said that is probably
>>>>>>why Netscape has ceased the secnews.netscape.com service.
>>>>>>
>>>>>>What are we supposed to do for good end user support for
>>>>>>Netscape Communicator 4.x support?
>>>>>>
>>>>>>Contacting Netscape Communications
>>>>>>http://home.netscape.com/company/contacts/index.html?cp=cmp
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>The news server still works on port 119. They should make
>>>>>netscape.communicator and the netscape.netscape6.* groups available for
>>>>>that port as well.
>>>>>
>>>>>Holger
>>>>>
>>>>>
>>>>>
>>>>They were specifically asked not to. The news admins, however, are not
>>>>answering pages and fail to reply to email. I think one may be on
>>>>sabatical but there should be coverage. I suspect either a DNS screwup
>>>>or apathy. History says the latter is fairly likely but the former is
>>>>possible.
>>>>
>>>>
>>>The latter sounds logical, yes. Most ISPs use the oldest machines they
>>>have to set up a news server, and then it stands in the corner. When I
>>>was asked to set up a news server for the company I work for they gave
>>>me a Pentium/133mhz with 64mb and a 2 gig hard drive. If it breaks, and
>>>I'm on vacation it won't be fixed until I'm back. Maybe same thing
>>>happened at Netscape. Let's hope :)
>>>
>>>Holger
>>>
>>>
>>well it can't be completely down... I'm reading this via
>>secnews.netscape.com
>>
>
> You are using port 119 which does not have some of the groups in
> question. The secure server on port 563 is refusing connections.
>
My post was in response (indirectly) to someone who said that the server
was being taken offline permanently, or something to that affect. Sorry
for piggy backing my answer, I couldn't find the original I wanted to
reply to
