You are not logged in.

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.

STiAT

Beginner

  • "STiAT" started this thread

Posts: 2

Location: Vienna, AUSTRIA

  • Send private message

1

Sunday, December 11th 2005, 5:15am

[kopete] MSN connection error (SOLVED)

Since about two days i experience a problem connecting to MSN servers.

Kopete tries to connect for a quite long time, and finally drops the following error:

Source code

1
2
3
4
5
There was an error while connecting to the MSN server.

Error message:

operation is not supported


Also i'm experiencing the problem when receiving files, the first file works properly, but if i receive two files, the 2nd won't receive. So i've to receive the files one by one, what can be quite annoying. Even when we finally agreed in packing the source (for just 6 files).

Is anyone experiencing similar problems?

Also, i've the ICQ bug when adding new users described here
Ability is nothing without opportunity.

This post has been edited 1 times, last edit by "STiAT" (Dec 13th 2005, 12:35pm)


STiAT

Beginner

  • "STiAT" started this thread

Posts: 2

Location: Vienna, AUSTRIA

  • Send private message

2

Tuesday, December 13th 2005, 12:37pm

Edited the message. The problem solved itself, seems as if i had a local error with one of my routers. An interruption of the power supply of my flat actually solved the problem - it did reset the router. Seems as if the port or something was hanging.

// STi
Ability is nothing without opportunity.

3

Thursday, April 6th 2006, 9:50pm

would like to corroborate this error

using mandriva 2006, with a linksys befsr41 router.

kopete ( kopete v 0.10. 3 , kde v 3.4.2 ) worked great . a day later, it would not connect, displaying the same error as the above poster displayed.

rebooting the router solved the problem.