Usenet Explorer

connection actively refused..... I reset configuration, and am still getting error 10061. What's up?

i don't see any problem, server appears to be up continuously since the last maintenance when i restarted it quite a time ago.

do you still experience this?

maybe connectivity from your ISP is / was somehow temporarily affected.

Yes - still can't connect. I suppose it could be an ISP problem, but this seems to be the only thing affected.

try ping (see pm)

if none works it is most likely your firewall or router to blame.

if one works and another doesn't it may be temporary connectivity problem from your ISP to the server, usually they are resolved at most within few hours.

Both URLs ping ok.

Still can't connect this morning.

When did you last do a search? I had to add a new IP to my firewall recently when I did a search so if you haven't searched in the past few days it could be that. Check your firewall if you have one: either disable it temporarily, allow UE full access or remove UE from the rules and try again. If you have a router, remove that and connect directly if you can to test.

yes, it must be some problem with router or firewall then.

i've sent you pm with more concrete diagnostics checks, something must not work with them. again the question is whether everything or only part doesn't work.

Found that I could telnet from my Lilnux machine, but not from Windows.
Both, of course, go through same firewall and router.

Noticed I had put dyndns entries in the "hosts" file on the Windows box a while back... why? I don't know (probably trying to get things to run a wee bit faster), I don't even remember doing it. They're gone now and all is well.

Thanks, y'all.

maybe i'll connect the search service ip resolution to UE caching dns capability as with news servers with resetting resolved ip after a socket error but using once resolved dns during current session as long as all is ok.

I am trying to use UE on my work PC, and I can download headers from GigaNews, using port 443 (SSL and open on our work network), but my searches are failing:

Search failed - A connection attempt failed because the connected party did not properly respond after a period of time

Is this a setup issue, or the search service not working?

KB

The ports in use by the Search Service are (or at least were) 2020, 2021 and 2022. Check that they are open in any firewalls on the network. It's a pity UE doesn't use something common like port 80 to simplify matters.

Those ports are closed in our enviroment:(

Is there a way to change the port for the Search Service?

KB

KillerBob wrote:Is there a way to change the port for the Search Service?

There used to be but you could only change between the three I mentioned earlier anyway. Now it's all done dynamically. There may be some way of doing it through a proxy and port forwarding or the like. However, this would be a workaround and may or may not be reliable and, at best, slow.

The only sure way of doing this would be for the Search Service to use a more commonly open port. The advantage to using an HTTP port would be that you could then add UE.exe to a firewall using a web browser template (of which most firewalls have built in) which would then not be picky when it comes to IP address changes.

search service ports may change.

in principle i can engage any ports, but as it set now it is around 2020+.

it is possible to direct all search service requests through a proxy, properties->proxies, search service in the access proxies pane.

e.g. you can run a socks proxy server on your home computer using a port which is accessible from your work computer.

if it would be an option to use an optional set of ports it would be essentially the same as if you run a proxy yourself.