MSN Timeout Problems When Going Wireless

[verselines]

Hi,

I'm running MSN messenger on Adium version 1.3.10 on Mac OSX 10.5.8

Problems started when I switched to a wireless set up with a Belkin N+ router. Everything runs okay when I'm wired up.

The main problem is that when a conversation pauses for a couple of minutes and I try to send an IM after that, around 1 minute later, Adium responds with the "Message may have not been sent because a timeout occurred:". This is sometimes followed shortly after with "Message could not be sent because a connection error occurred:"

Sometimes, contacts aren't able to see that I'm online even though my status is 'available'. Sometimes I'm also unable to receive IMs from others...they send me a bunch of IMs and there's absolutely not sign of it on my screen.

I've noticed that sometimes the IMs do get through to the other party, but only after a long while, which makes for weird conversations.

What I've tried:
-turning the firewall of my router off
-trying 'connect via http' on adium (which makes it worse cos I can't even log in when that option is checked)
-reset my router settings
-updated to the latest 1.4 beta version of Adium. Same thing happens except the error message this time is "Message could not be sent because an error with the switchboard occurred:"

So far nothing's worked and being a technology idiot, I'm at my wits end. Any help would be appreciated!

PS I've googled for ages and this problem has popped up before but there seems to be no definitive solution.

[verselines]

An add on:

No problems when using MSN Messenger for Mac. But I really dislike the interface for that and would much rather use Adium.

Thanks!

[Robby]

From my experience the "timeout" error occurs with unstable internet connections. I believe the Adium 1.4 beta is less sensitive. You might want to check that out.

[strangetml]

i suspect that relates to proxy/connection config. please, can someone tell the reason? i find nothing in "adium help" and Google shows no solution about this problem. I was like "what the..."

[verselines]

just checking in to say that this problem is still here.

it disappeared magically without me seemingly doing anything...but i went to reinstall adium and it's started up again. i've tried using a clean slate of preferences but it's still screwed up.

[Robby]

This is an issue in libpurple which "uninstalling" Adium and the like shouldn't help. As I said, the issue should be better in Adium 1.4 but according to verselines updating didn't resolve the problem for him.

One thing you could try would be "connecting via http": http://trac.adium.im/wiki/ServiceFeatur ... ononandoff.

[strangetml]

in fact i am guessing this issue has something to do with the wireless/wired router's proxy setting. since I'd changed to connect another wireless router from one which I used to connect to. this problem occurred really often. but the most ridiculously thing is that this issue is annoying to most of the users who have encountered it, yet there is no one steps out and say something helpful about it. OMG

[verselines]

it's happening to me now as i type this. go figure.

log out and logging in again solves it but it's fast getting on my nerves.

[strangetml]

it's happening to me now as i type this. go figure.

log out and logging in again solves it but it's fast getting on my nerves.

there're just bunch of people having the exact same problem. Unfortunately, I can't find any official answer for that. sigh.

[tennisbold]

I have the exact same problem. However, Microsoft MSN Messenger timeouts as well. The problem also occurs in WIndows XP. Thus, I suspect my router to be the culprit. It's a Netgear something I find it ridiculous to buy a new router, just because MSN acts up!