&RQ connect problem

êðþõà-ãâåñò · **Reply #30 on:** December 04, 2003, 03:56:58 PM

êîðî÷å, ÿ *.bat ôàéë çàáàöàë ÷òîá ìíå common.ini çàìåíÿë, â êîòîðîì ïðîïèñàë íîðìàëüíûé ip, íåìíîãî ãåìîððà è âñ¸ òåïåðü îê

[/quote]

Õåõ ... Äîâàé ïèøè êîä áàòíè÷êà :lol: , à òî ãåìîðîåì íåò âðåìåíè ñòðàäàòü, êîïàòü è êîïàòñÿ â ÄÎÑ êîìàíäàõ, ëåíü âñïîìèíàòü. :eek: À ÷åðåç Ñîêñ øëþç îòñòîéíî çàïóñêàòü ïðîãó ... ãèìîðîéíî êàê òî, îäíó çàïóñêàé ïðîãó ïîòîì âòîðóþ, ëåíü ..

)))

@ECHO OFF
copy mycommon.ini common.ini /y
D:\Program Files\&RQ\&RQ.exe

Pofigator · **Reply #31 on:** December 05, 2003, 06:28:39 AM

We have the same problem with &RQ in our organization.
Almost all of our &RQ users have trouble whith connecting (48%).
After analize all that was written in this tipoc I think that this is a DNS server problem of AOL. So when &RQ request ip-address of login.icq.com host, and receive bad (or may be empty) ip-address, then it will try to connect to that bad ip-address.
It seems that other ICQ clones check the ip address about it correct.
Or may be after unsuccessfull connect timeout try to resolv DNS and connect again.

Good luck!

Still waiting unicode pathching.
And now waiting resolving current serious connect problem.

&RQ forever :-)

UM_ · **Reply #32 on:** December 05, 2003, 06:59:18 AM

×óóóóìààààà

)
ó ìåíÿ âñ¸ îòïóñòèëî ñåãîäíÿ =)

óôôôôô.....

Pofigator · **Reply #33 on:** December 05, 2003, 07:22:46 AM

Quote from: "UM_"

×óóóóìààààà )
ó ìåíÿ âñ¸ îòïóñòèëî ñåãîäíÿ =)

óôôôôô.....

Åùå îäíî ïîäòâåðæäåíèå - DNS ïî÷èíèëè

rejetto · **Reply #34 on:** December 05, 2003, 11:54:05 AM

i did not understand the problem
&RQ, after a DNS failure, use a cached IP address for connecting

Pofigator · **Reply #35 on:** December 05, 2003, 01:08:35 PM

Quote from: "rejetto"

i did not understand the problem
&RQ, after a DNS failure, use a cached IP address for connecting

May be it was my mistype.
May be there was not failure. Who knows...
As I see AOL return on DNS requests different IP at different time.
This usually doing for dividing workload between several servers.
For example DNS reply at time i've writing this msg:
[login.icq.com]
Translated Name: login.login-grt.messaging.aol.com
IP Address: 64.12.161.153
IP Address: 64.12.161.185
IP Address: 64.12.200.89
IP Address: 205.188.179.233
Alias: login.icq.com

So really this may be situation when one of this server was down,
or incorrectly working.
&RQ try to connect and can't connect.
then get IP from cache, but cached address already not actual
(may be AOL switch workload to another server with different IP).
So what &RQ will do? I don't know :eek:

I think &RQ must try to connect on all returned by DNS-reply IP-addresses sequencely.
Getting IP from cache is economical but there may be probability of errors.

rejetto · **Reply #36 on:** December 06, 2003, 02:42:16 PM

i will try to do this

&RQ connect problem

êðþõà-ãâåñò

UM_