Target machine refused the connection (dns caching again?)

In the case of a search service disruption the status updates will be shown here.

05 Jun 26: There was an attempt to release v7.8.1 with change in search service protocol, but I noticed something is maybe wrong with the server management version (derivative of UE) and reverted all back out of abundance of caution, it was available for at most 20 minutes. If you downloaded it during the short time period (after trying to use the search service since I didn't set the update notification) downgrade to v7.8 since there is no clear UE notification when the search protocol has been possibly downgraded (which will be now added, since I didn't foresee such scenario, it will be something positive to come out of this). It might be very few users in single digits who are affected. The message will be removed after I sort it out and make the release now maybe as v7.8.2.
Post Reply
jdr1700
Posts: 9
Joined: Sun Oct 21, 2007 5:37 pm

Target machine refused the connection (dns caching again?)

Post by jdr1700 »

v1.9.9 in use here. Search was working yesterday evening, today it isn't - getting a message saying the target machine refused the connection.
Josef K
Posts: 534
Joined: Thu Feb 27, 2003 7:29 pm

Post by Josef K »

It's working here for me (I checked earlier but bassie had already said it worked for him also so I didn't reply).

I did notice my firewall pop up for a confirmation (on ports 2020 and 2022) so check yours in case it's being blocked.
alex
Posts: 4572
Joined: Thu Feb 27, 2003 5:57 pm

Post by alex »

the server was up continuously, i restarted it last time after full backup 300 hours ago.

try to ensure it is not firewall.

i've checked now the last server ip address change - most likely your firewall has dns caching enabled, try to disable it for UE or at least for *.dyndns.org wildcard addresses. or just reset the dns cache but the server ip is not guarantied to be static and so it may change sometimes.

i see here the dynamic address was updated some time yesterday, i'm not sure it is because of ip change or it is monthly refresh, if the former and you have dns caching somewhere it is the reason then.

the same issue had been mentioned already in the search service section, i'll move the thread there - where it belongs - later as well.
Post Reply