cocoaforge

I am having this EXACT problem except for one major detail--I am NOT using leopard, I am still using Tiger! Adium will not connect to my msn account--no error message, just never connects. If I check the "accounts" menu in status, it says "syncing with server...50%" and just stays stuck there. This started yesterday and hasn't gone away in spite of all my tinkering.

Will that terminal solution work for me? Any idea what might be causing my problem, since I can't blame i on leopard?

Edit: Nevermind, it started working again! ...weird.

I'm also having this problem and still using Tiger. Only started Friday for me. Also affects my AOL account. Tried the terminal fix but doesn't work for me.

1.1.4
OSX 10.5.1
linksys 54wrtgl

I was having the same problems as many others have reported on this forum. As Zac explained it has something to do with how 10.5 calls for the network through a router.

I tried adding entries to the hosts file, not sure why it didn't work - I thought it should have (unless MSN has changed IP's since that post), but it didn't.

My solution:

Visit the router's configuration page and make note of the DNS server IP's (there should be 2 or three of them). Each router will be different on how you need to access the info, so use google if you don't know.

Open network preferences, click on the connection you are using and select advanced.

Click on the DNS tab and add the DNS entries that you got from your router. (Your router's IP should already be listed there.)

You should now be able to connect.



Why this works: your computer will look for the address in the first address listed, for whatever reason it is not found in the first one, and because there are no other places to look it doesn't connect. Now that we have added 2 or three alternatives, if OSX can't find it in the first one (which we know it can't because of some new 10.5 problem) then it will look in the 2nd/3rd DNS server where it finds the info it needs to connect.


Hope this helps.

If it's the case that Leopard is at fault, please explain why the official msn client will connect just fine.

Ali wrote:If it's the case that Leopard is at fault, please explain why the official msn client will connect just fine.

The MSN client probably uses a different mechanism for resolving addresses, or has built-in IPs hardcoded to connect to. It's definitely a Leopard issue that the hostname won't resolve. Other errors when connecting are probably not the Leopard issue being referred to as such.

Ali wrote:If it's the case that Leopard is at fault, please explain why the official msn client will connect just fine.

I'll be honest I don't care who's fault it is, all I know it wasn't working regardless of leopards/adium's fault (and that I found a way to fix it thanks to reading this thread - and posted it here so others could make use of it).

Ask the MSN developers why MSN works with leopard - doesn't make sense to Adium users and developers to explain the inner workings of some other product they have no part in developing.

zac wrote:

Ali wrote:If it's the case that Leopard is at fault, please explain why the official msn client will connect just fine.

The MSN client probably uses a different mechanism for resolving addresses, or has built-in IPs hardcoded to connect to. It's definitely a Leopard issue that the hostname won't resolve. Other errors when connecting are probably not the Leopard issue being referred to as such.

I must be experiencing these other errors then, since editing the hosts file doesn't fix the issue for me. I wish I knew what they were.

Thanks.. for taking time to help