[JDEV] jabberd behind NAT fails s2s interoperation

[Tijl Houtbeckers]

"matthew c. mead" <mmead at goof.com> wrote on 4-10-2002 0:06:37:
>
>So sitting behind a NAT box doesn't sound like it should affect
>things.
>
>Just to be sure I hadn't done something wrong I extracted to
>another directory, rebuilt, and started from the stock
>configuration file.  All I changed in it were the admin addresses
>and the <host> and <update> contents so they matched my FQDN.
>I'm still getting this at startup:
>
>20021003T22:03:22: [notice] (-internal): initializing server
>20021003T22:03:22: [notice] (update.jabber.org): failed to establish 
>connection 20021003T22:03:22: [notice] (update.jabber.org): bouncing a 
>packet to jsm at update.jabber.org/1.4.2 from goof.com: Server Connect 
>Failed 
>
>
>-matt

Update.jabber.org has been dead for many, many months now. Some clients 
still try to connect to it though. Also if you're testing if S2S works 
you're better of using another server as jabber.org wich runs the CVS 
version of jabberd. S2S has been broken on it more then once.