cannot connect to jabber.gmx.net

[Oleksij Rempel]

Binary package hint: pidgin

After some update on jaunty i can't connect to jabber.gmx.net . same vkonto working fine with pidgin on hardy

lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

apt-cache policy pidgin
pidgin:
  Installiert: 1:2.5.3-0ubuntu2
  Kandidat: 1:2.5.3-0ubuntu2
  Versions-Tabelle:
 *** 1:2.5.3-0ubuntu2 0
        500 http://de.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.5.3-0ubuntu2
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin
Uname: Linux 2.6.29-rc2-next-20090123-slub x86_64

[deleted (to-delete)]

Version: (using Devel)
OS: Linux
Installed from: Compiled sources

I tried to connect to GMX's jabber server and got the information that this is a unknown host. A quick check with PSI showed me that the server works fine and only kopete isn't able to connect.
My current version of kopete is Version 0.60.82

Further investigations showed that the first packet send to the server differs between kopete and PSI

PSI:
<?xml version="1.0"?>
<stream:stream xmlns:stream="http://etherx.jabber.org/streams" version="1.0" xmlns="jabber:client" to="gmx.de" xml:lang="en" xmlns:xml="http://www.w3.org/XML/1998/namespace" >

Kopete:
<?xml version="1.0"?>
<stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" to="gmx.de" >

I tested it with `cat bad|nc jabber.gmx.net 5222` but both versions showed the same behavior and the server send only

<?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='1839397057' from='dummyhost' xml:lang='en'><stream:error><host-unknown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error></stream:stream>

The next one was to check which server I connect to... and this seems to be the problem. Kopete connects to gmx.de (213.165.65.50) and PSI to xmpp-gmx.gmx.net

A quick check which DNS packets were send showed the really difference. Kopete asks for the ip of gmx.de and PSI asks about `host -t SRV -c IN _xmpp-client._tcp.gmx.de` (and maybe falls back if to kopetes behaviour when it fails).

See http://xmpp.org/rfcs/rfc3920.html#rfc.section.14.3 for more information about that.

[Tobias-winchen (tobias-winchen)]

I don' know if it is the same bug, but I can confirm that kopete can't connect to gmx.net in todays debian lenny version:

Qt: 3.3.8b
KDE: 3.5.10
Kopete: 0.12.7

and the version shipped today in KDE4 4.1.4 (Lenny backports)

I can connect to gmx.net with Pidgin 2.4.3 and to jabber.ccc.de with both kopete versions.

[Cm-i (cm-i)]

I also experience connection problems (unknown host) with gmx.net with Kopete 0.60.82.

[bwalle (bernhard-walle)]

Has anybody found a workaround? That bug is quite annoying for me. :(

[deleted (to-delete)]

I wrote about the workaround in the bug report. Just specify xmpp-gmx.gmx.net with port 5223 in your server and port editbox and enable "Override default server information".

[Oleksij Rempel (olerem)]

Same issue like here:

http://bugs.kde.org/show_bug.cgi?id=181481

[Michael Greifeneder (mikegr)]

Workaround works for me, too. Thanks.

[Entwanzer (entwanzer)]

Tried the workaround, didn't work for me. I get the message "host not found"

[deleted (to-delete)]

Did you use xmpp-gmx.gmx.net or xmpp-gmx.gmx.de?

$ host -a xmpp-gmx.gmx.net
Trying "xmpp-gmx.gmx.net"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47849
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;xmpp-gmx.gmx.net. IN ANY

;; ANSWER SECTION:
xmpp-gmx.gmx.net. 1878 IN A 213.165.65.40

Received 50 bytes from 192.168.1.1#53 in 86 ms

Are you using gmx, 1&1 or web.de?
$ host -t SRV -c IN _xmpp-client._tcp.gmx.de
_xmpp-client._tcp.gmx.de has SRV record 5 0 5222 xmpp-gmx.gmx.net

$ host -t SRV -c IN _xmpp-client._tcp.web.de
_xmpp-client._tcp.web.de has SRV record 5 0 5222 xmpp-webde.gmx.net

$ host -t SRV -c IN _xmpp-client._tcp.online.de
_xmpp-client._tcp.online.de has SRV record 5 0 5222 gmx.net

[Entwanzer (entwanzer)]

(In reply to comment #7)

I used xmpp-gmx.gmx.net

host -a xmpp-gmx.gmx.net
Trying "xmpp-gmx.gmx.net"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12715
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;xmpp-gmx.gmx.net. IN ANY

;; ANSWER SECTION:
xmpp-gmx.gmx.net. 54752 IN A 213.165.65.40

Received 50 bytes from 192.168.1.1#53 in 91 ms

I am using gmx.
host -t SRV -c IN _xmpp-client._tcp.gmx.de
_xmpp-client._tcp.gmx.de has SRV record 5 0 5222 xmpp-gmx.gmx.net.

host -t SRV -c IN _xmpp-client._tcp.web.de
_xmpp-client._tcp.web.de has SRV record 5 0 5222 xmpp-webde.gmx.net.

 host -t SRV -c IN _xmpp-client._tcp.online.de
_xmpp-client._tcp.online.de has SRV record 5 0 5222 gmx.net.

seems to be identical to your output.
Bu still, i get a popup from Kopete "Connection problem with Jabber server xmpp... There was a connection error: Host not found"

[Entwanzer (entwanzer)]

Found the Problem: Trailing whitespace to the server-address :)

now it works

[Gunni (fgunni)]

I have the same bug, tried xmpp-gmx.gmx.net , but still the same (No trailing Whitespace)
The strange thing is, that my 1und1 account still works with jabber.gmx.de

[Gunni (fgunni)]

Ah, sorry, as i am on web.de with this second account, i had to use xmpp-webde.gmx.net , so now it works with this server.

[Gunni (fgunni)]

Some additional info: I had to delete the account and reenterd it, according to the info i found here:

http://meinungen.web.de/forum-webde/post/771208 (german)

[deleted (to-delete)]

> Some additional info: I had to delete the account and reenterd it, according to the info i found here:

This is "Quatsch". Kopete cannot resolve the SRV dns stuff and will not doing anything useful if you delete your account...

[Gunni (fgunni)]

Robert: Thanks for your "kind" post. For me it was useful to delete the account.
Before deleting it did not connect.

[deleted (to-delete)]

So, lets ask the other who had success in connecting to xmpp-gmx.gmx.net by deleting his account and then readd it to kopete 0.60.82 without manually overriding the connection information.

[2kmm (2kmm)]

Same here with kopete 0.70.2 (kde 4.2.2). Unknown host if i use gmx.de, but works with the workaround.

[2kmm (2kmm)]

*** This bug has been confirmed by popular vote. ***

[Sebastien Bacher (seb128)]

do you stil get the issue?

[andi5 (andi5)]

Q: Is this a duplicate of bug 133097?

[andi5 (andi5)]

Pidgin should work out of the box. Just leave the entry box for "Connect server" empty. jabber.gmx.net is not necessarily the correct server anyway.

[Robert Gerlach (khnz)]

(In reply to comment #18)
> Q: Is this a duplicate of bug 133097?

Yes. It works well if your DNS supports SRV records. But there appears no error message if not (connection silently failed).

[Paulo Fidalgo (o-kanniball-o)]

I've came across this through a google search, and at the moment I'm connected with Kopete to gmx.com server. So I think this could be closed.

[Pali (pali)]

Kopete in svn has updated xmpp libiris library. Please test Kopete version from svn if this problem is fixed.