You are not logged in.

Can't login to AIM with Kopete, can login with official AIM

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

LightStruk

Beginner

  • "LightStruk" started this thread

Posts: 3

  • Send private message

1

Wednesday, January 28th 2004, 6:21am

Can't login to AIM with Kopete, can login with official AIM

This problem has been dogging me ever since I dumped Windows. I have never been able to log into AIM, using OSCAR, with an unofficial client. I have no trouble with AOL's Linux AIM client or with Apple's iChat client (which is effectively an official client), but I cannot log in to AIM with Kopete, Gaim, caim, or any other open-source IM client.

* When I try to login with Kopete, I get "Sign on failed because the password supplied for this screen name is invalid. Please check your password and try again."
* When I try to login with caim, I get "Received unknown packet: 0x 0 0x 1 0x 0 0x 1 0x 0 0x 0 0x 0 0x 0 0x 0 0x 4 0x 0 0x 8"
* When I try to login with naim, it works! However, naim uses TOC, not OSCAR, to connect to AIM.
* And of course, if I try to login with AOL's client or Apple's client, it just works.

The only thing I can think of that could be getting in the way is that my IM name was once an AOL subscriber name, but I left AOL and just kept my AIM name. I suppose that may be a rare scenario, but I don't see how it would affect the login process.

Does anyone have any ideas? I'm currently using Kopete 0.8 RC1 but I had these problems with older versions too.

Twiggy794

Trainee

Posts: 101

  • Send private message

2

Wednesday, January 28th 2004, 7:30am

Kopete 0.8rc1 has a tendency to flip out if your AIM screenname has an insanely large buddy list...figured I'd give you some forewarning...

As far as not connecting ~ The fact that your connecting with an official AOL screenname could very well be the problem. Are you still on AOL? If not, cancel the account and re-register that name as an Oscar name instead. Otherwise, try a new name from the AIM website.

Another possible remedy to pinpoint the situation is to try logging onto ICQ. ICQ and AIM are both based on Oscar, so this will tell you whether or not you have a problem logging on to Oscar, or maybe it's just your SN.

LightStruk

Beginner

  • "LightStruk" started this thread

Posts: 3

  • Send private message

3

Wednesday, January 28th 2004, 9:19am

I'm certainly no longer an AOL subscriber; I haven't been one for years. My buddy list is not "insanely" long, just 102 names. Is there a way to find out if the official clients are using TOC for my username instead of OSCAR? Is the TCP port different, for example?

Twiggy794

Trainee

Posts: 101

  • Send private message

4

Wednesday, January 28th 2004, 2:06pm

100+ is considered insane ~ I had to reduce mine from 181 diown to 53.

As far as I know, there isn't. Your best bet is just to try ICQ, and register a new name and try that.

djtrippin

Trainee

Posts: 142

  • Send private message

5

Wednesday, January 28th 2004, 4:58pm

I have over 220 people in my AIM list, which is supposedly over the limit imposed by aol, yet kopete works fine for me. Since you said that the official clients work, and you also said that the TOC clients work, is it possible that since your screenname is originally an aol screenname, that you may only be able to log in with that name over TOC? Try registering a new name just to test if your third party clients are working over oscar at all.
Simplicity is the staple of the working man.

LightStruk

Beginner

  • "LightStruk" started this thread

Posts: 3

  • Send private message

6

Thursday, January 29th 2004, 4:05am

I fixed it!

I fixed it!

In perhaps a moment of inspired brilliance or just plain dumb luck, I reasoned that perhaps AOL needed to update my screenname somehow to make it act like a new name.

So I changed my password, and then changed it back.

Now Kopete works!

Yay!

This solution should be added to Kopete's FAQ, methinks.

shock_ez

Beginner

Posts: 37

  • Send private message

7

Friday, February 6th 2004, 3:31pm

I have been having this problem for days, ever since updating to KDE 3.2. It's annoying as hell. I believe I'll try what you suggested, changing the password and changing it back...

Wish me luck!