[JDEV] Internal Timeout Error

Kevin Limperos kevin at omnipod.com
Sat Feb 10 17:25:08 CST 2001

    I've just installed the Jabber 1.4/final server with the AIM 0.9.0 transport on RH 6.2. Whenever I connect with WinJab, the server consistently generates 'Internal Timeout' and 'Server Connect Failed' entries, despite actually logging the WinJab clients into the AIM transport. For instance:

20010211T00:16:03: [notice] (aim.themonitor.omnipod.com): bouncing a packet to aim.themonitor.omnipod.com/registered from zod5000 at themonitor.omnipod.com/Home; Internal Timeout
20010211T00:18:25: [notice] (update.jabber.org): bouncing a packet to 959967039@
update.jabber.org/ from zod6000 at themonitor.omnipod.com/Home; Server Connect Failed

What is the likely culprit: a problem with the installation, the O/S version, the jabber.xml file or some other element? 

These messages also appear over and over like a plague of locusts:

20010211T00:18:25: [alert] (s2s): We were told by update.jabber.org that our sending name themonitor.omnipod.com is invalid, either something went wrong on their end, we tried using that name improperly, or dns does not resolve to us

The server is behind a firewall - how can I shut this off?

Thank you.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20010210/9deb52ae/attachment-0002.htm>

More information about the JDev mailing list