Bug 132002 - MSN connectivity problems behind firewall
Summary: MSN connectivity problems behind firewall
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: MSN Plugin (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-07 13:23 UTC by Matthew Williams
Modified: 2008-11-15 06:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Williams 2006-08-07 13:23:50 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    Ubuntu Packages
OS:                Linux

If I try and use Kopete to connect to MSN from behind my corporate firewall, I get connection problems when trying to talk to people that are not using Kopete as well, such as if the other contact is using the Microsoft client or Trillian. 

If I open a chat window to a contact using a different client, I get the following message in the chat window;

         <Contact> has left the chat (connection closed).

and on the stderr, kopete prints the following;

         kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (remote host closed connection)

This problem isn't seen if the other contact is using Kopete as well.

I also don't see this problem if I use the same laptop, connecting via my home broadband connection, which makes me think it is an interaction problem between the firewall here and Kopete. 

However, people using other clients, such as Gaim under Linux or Trillian or the Microsoft client under Windows don't see any problems from behind our firewall.
Comment 1 Matthew Williams 2006-08-07 13:26:53 UTC
I should add that other people who try and use Kopete behind our network are seeing similar problems.
Comment 2 Olivier Goffart 2006-08-07 16:55:53 UTC
Can you paste the debug that happen before the disconection ?
Comment 3 Matthew Williams 2006-08-07 16:59:55 UTC
The message;

kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (remote host closed connection)

is the only message I see on stderr when I just run 'kopete' and open the chat window. Is there a flag I can give to kopete to produce more verbose output? 'kopete --help' doesn't seem to suggest anything obvious.
Comment 4 Cade Robinson 2006-08-24 20:49:31 UTC
I get the same thing.
I get bug #123726 quite a bit as well.

kopete 11.3 (kde 3.5.4) in debian.
Comment 5 Cade Robinson 2006-08-24 20:50:56 UTC
I should also not that I do not see any MSN issues with GAIM on the same machine.
Comment 6 Jérôme Guelfucci 2007-07-05 21:33:55 UTC
Any news on this ? This still happens with Kopete on Kubuntu Feisty, see : https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/53336.
Comment 7 Henrik Segesten 2008-04-15 16:34:17 UTC
I can't connect at all with MSN when I am behind the firewall with neither Kopete 0.50.1 or 0.12.7. It does not work with HTTP method enabled either. Could this be a related problem?
Comment 8 Ruud Koolen 2008-07-07 16:17:43 UTC
Any information on what firewall is being used where you work? Problems with "some firewall" are hard to debug.
Comment 9 Matthew Williams 2008-09-15 21:02:20 UTC
Unfortunately I no longer work at the same company so am unable to reproduce this bug any more.
Comment 10 إسلام الشيخ 2008-10-28 07:11:54 UTC
I have same probelm in my company.

Kopet is not connecting to MSN but pidgin can connect to MSN in same pc, same network

The err message is:

There was an error while connecting to the MSN server.
Error message:
Unable to lookup gateway.messenger.hotmail.com

Kopet is working fine at home
Comment 11 Matt Rogers 2008-11-15 06:08:52 UTC
We've completely replaced the current MSN implementation with a new MSN implementation which  If you continue to experience this bug after testing the new implementation (which can be gotten from our subversion repository or with the KDE 4.2 Beta 1 release), PLEASE, open a new bug rather than reopening this bug. Thank you for your time and efforting in helping us find and fix problems in Kopete.