[JDEV] Still can't get the AIM Transport to run

[Tim Ferguson]

I had this same problem and it made a difference when I changed the service
entry in jabber.xml from:

  <service id="aim.cos.cw.net">
    <accept>
      <ip>127.0.0.1</ip>
      <port>7009</port>
      <secret>aimtest</secret>
    </accept>
  </service>

to:

  <service id="aim.cos.cw.net">
    <accept>
      <ip/>
      <port>7009</port>
      <secret>aimtest</secret>
    </accept>
  </service>

Notice the line specifying the ip address
Tim Ferguson
Cable & Wireless

-----Original Message-----
From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of Mark
Hahn
Sent: Thursday, December 14, 2000 8:39 AM
To: jdev at jabber.org
Subject: Re: [JDEV] Still can't get the AIM Transport to run

>
>    It's connecting to port 5269, *NOT* port 7009 as it would appear you
>have it configured for..
>

Well I sure thought I had but when I recompiled everything yesterday
I forgot to reconfigure with the --with-jabber2 switch so 5269 was
the hardcoded port.  Sorry about that!

However, now that I have fixed that little bug, the server is looking
for MX records associated with the transport IP address I assume.
The output looks like the following:

Thu Dec 14 10:20:34 2000  debug/xmlstream.c:222 xmlstream_main: startup
Thu Dec 14 10:20:34 2000  debug/tstream.c:335 tstream_connect:
ADNS[aim.noah.gte.com:7009]
Thu Dec 14 10:20:34 2000  debug/tstream.c:357 tstream_connect: ADNS A
lookup loop
Thu Dec 14 10:20:34 2000  debug/tstream.c:365 tstream_connect: ADNS
found some responses, attempting to connect
Thu Dec 14 10:20:34 2000  debug/tstream.c:492 tstream_socket 7009
132.197.118.26
Thu Dec 14 10:20:34 2000  debug/tstream.c:397 tstream_connect: ADNS
MX lookup loop
Thu Dec 14 10:20:34 2000  debug/tstream.c:435 tstream_connect: failed
ADNS MX lookup
Thu Dec 14 10:20:34 2000  debug/tstream.c:463 tstream_cleanup
Thu Dec 14 10:20:34 2000  debug/xmlstream.c:260 xmlstream_error
Thu Dec 14 10:20:34 2000  debug/xmlstream.c:260 xmlstream_error
Thu Dec 14 10:20:38 2000  error/etherxs Failed to establish
communication with etherxd


Since I had to set up a simple name server in order to have adns
resolve aim.noah.gte.com I never bothered with MX records for the
domain.  I assume I need to provide them or I have something else
configured incorrectly.  Thanks again for your help.

-mark
================================================
  Mark Hahn              |  Verizon Laboratories
  mark.hahn at verizon.com  |  40 Sylvan Road
                         |  Waltham, Ma. 02451
================================================

_______________________________________________
jdev mailing list
jdev at jabber.org
http://mailman.jabber.org/listinfo/jdev