You are not logged in.

[kopete] Timeout when connecting to IRC

David Simmons

Beginner

  • "David Simmons" started this thread

Posts: 2

  • Send private message

1

Monday, July 12th 2004, 8:18pm

[kopete] Timeout when connecting to IRC

I'm not able to connect to IRC servers using the 0.8.2 or 0.8.4 release. It looks like it's timing out.

Per the FAQ for Kopete:

----------

IRC

I can't connect with IRC. The icon stays in the blinking connecting state, but never connects. What's the problem?

You need to upgrade Kopete, or install an identd. Some IRC servers require an identd, and wait 60 seconds or so to find one before continuing. Older versions of Kopete IRC time out after 30 seconds, so the connection is never established. The latest versions (0.8.2) use the KDE wide socket timeout setting

----------

I've tried to find where this "KDE wide socket timout" setting is, but so far haven't found it.

Where do I increase this timeout so that I can connect to IRC servers again?

Thanks!

David Simmons

matdoc

Beginner

Posts: 5

  • Send private message

2

Wednesday, July 14th 2004, 10:18am

I have kopete 0.8.2 with KDE 3.2.2 and all I had to do was to add a line in ~/.kde/share/config/kioslaverc
[code:1]
ConnectTimeout=70
[/code:1]
Restart kopete afterwards and you should be able to connect to IRC (although with a long delay. But installing identd - as suggested by some other poster - didn't work for me ...).

Hope that helps,

Matthias

David Simmons

Beginner

  • "David Simmons" started this thread

Posts: 2

  • Send private message

3

Wednesday, July 14th 2004, 11:38am

I haven't had a chance to see if your fix works, but I found a work around that may help others.

I'm connecting behind a firewall that dropped the ident request from the IRC server. I changed my firewall rule to reject ident rather drop it, and I'm able to connect to IRC very quickly now.

The suggestion to install identd was something I had gotten also, but of course, being behind a firewall doing NAT, the address seen by the IRC server wasn't mine, but the firewall, thus the reason that I looked into modifing the firewall.

David