Usenet Explorer

I have been getting a search failed because "... the connected party did not properly responde..."
Are there problems right now?

Ditto here. Getting the "Search failed. A connection attempt failed because the connected party did not properly respond after a period of time, or".

I have been getting this one for the last 30 min.

Same here, since 18.00 GMT

I'm getting the same error mariala06

12:10 CDST here in USA and it is still giving "Connection attempt failed because the connected party did not respond after a period of time."

Querry, Alex.
Keep up good work.

10065 here "unreachable host"

Same here "search failed, a connection attemp failed..".
Homepage says the server is up, must be error somewhere.

a server computer went down. exact reason i don't know yet, there appears to be connectivity in general (maybe not cannot tell for sure yet), but few days ago i noticed connectivity was shortly lost on that connection.

i accidentally forgot to switch on the search service monitor after the last database backup few days ago (switched it off during backup to avoid alarm sound, was night time), so there was no alarm when the problem started. in addition transformer burned around so there was outage during the day hours and i didn't check the forum, but if the search service monitor were on, i would be notified in time before the power went down.

i've switched to 150 day backup configuration, until i have the server computer up again.

the computer which went down is up again, i'm restarting the service with regular retention now.

the reason was winxp stuck in reboot with choose single hardware profile choice (such error is only documented by microsoft only for win2k).

i've restarted the computer to ensure it reboots ok, no error.

my speculation is there was some problem with power supply (some fluke in the voltage) which caused reboot and persisted while the computer was rebooting.

Message still says that server is being restarted.
May still be a problem.

it has restarted already, just took a while, reboot then restart, all works.

i needed to check the reboot condition, apparently it is some kind of undocumented microsoft bug, they documented it for win2k but didn't really fix it.

Ok. Working now. Thanks.