Log says it all. Client authorization failed. Invalid login/password.

It works from big wippien? If so, can you send me your JID/password to so I can try it out?

Kreso

thank you Kreso. After your response I tried to create a new account and use that on Ubuntu, and is working.
.............................................
The weird thing is that password is working on the big wippien with no problems.
Anyway I can say that I surrounded the issue using a new account. But for me is strange why that password (correct one) is not working just when I use wippien linux version...
but after that not problems at all...

regards,
nologo

I'm able to log on using my normal XMPP account (on the server neko.im), and I am able to establish a connection to a friend, but after some time wipclnt disconnects with the notice "Disconnected from XMPP server" and no further explanation. Re-connecting works fine, until it also disconnects.

You can enable logging and send me last few lines of the log file?

Kreso

Quote:

---

Ok, get linux version again and call wipclnt with -d switch, such as

./wipclnt -d pass

and then send me debug output, everything you see. You can send it on my email if you wish, since password may be shown. Or just hide password in the text.

Kreso

---

Hi Kreso,

I have the same issue, but here it seems it simply doesn't support STARTTLS. I've obfuscated sensitive info from the output...

Thanks, Rob

Code:

---

me@pc:~/Desktop$ ./wipclnt -d j@i.d pwd
JID j@i.d
IP 5.x.y.z
Netmask 255.0.0.0
MAC ff:ff:ff:ff:ff:ff
xmpp DEBUG attempting to connect to i.d
xmpp DEBUG connection successful
conn DEBUG SENT: <?xml version="1.0"?><stream:stream to="i.d" xml:lang="en" version="1.0" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams">
xmpp DEBUG RECV: <stream:stream xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" id="7777777777" from="i.d" version="1.0" xml:lang="en">
xmpp DEBUG RECV: <stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism></mechanisms><register xmlns="http://jabber.org/features/iq-register"/></stream:features>
conn DEBUG SENT: <auth mechanism="DIGEST-MD5" xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/>
xmpp DEBUG RECV: <stream:error><policy-violation xmlns="urn:ietf:params:xml:ns:xmpp-streams"/><text xmlns="urn:ietf:params:xml:ns:xmpp-streams" xml:lang="en">Use of STARTTLS required</text></stream:error>
xmpp DEBUG RECV: </stream:stream>
xmpp DEBUG Closing socket.
Disconnected from XMPP server
event DEBUG Stopping event loop.
event DEBUG Event loop completed.

---

Correct, at thsi time I use open source XMPP library which doesn't suppose TLS.

Kreso

I just installed and tried the linux command line client. First, I had the same problem. But I remembered, that the JID might consist of where resource is used to distinguish different types of 'places' you login from. I used /VPN as resource as I'm also logged in for IM using Pidgin (with /home as resource). Maybe some servers need the resource at all or at least for multiple logins.

Best regards,
Masin

I think it adds 'WippienIM3' automatically for resource, since this resource was required for other Wippien's to locate you. This is changed in last version, but I'm not sure if linux version is updated for this.

Kreso

Quote:

---

I think it adds 'WippienIM3' automatically for resource, since this resource was required for other Wippien's to locate you. This is changed in last version, but I'm not sure if linux version is updated for this.

---

Well, according to the source code of the Linux version it seems to do as you write -- which is quite strange, as it disconnected when I omitted the resource.

Perhaps the servers of web.de block Wippien login attempts, but it seems unlikely -- Wippien is still mostly unknown, I guess.

Masin

And big WIppien for WIndows works ok with your account, and WippienIM3 resource?

Kreso