cocoaforge

This might not be the right place, but I'm going to try anyways. My AIM is lagging in every single program I use. It'll be fine for the first 5 minutes then start lagging. I know its not my computer because when I'm using my university's wireless, its fine. However, when I'm using my apartment complex's network, it starts to lag. I've tried using Adium, iChat, AIM proper, AIM express won't let me log on, and Meebo. All of them except AIM express will work for a few minutes then start lagging.

Any advice would be awesome.

Thanks!

Addendum:

I even called my service provider and my connection is running fine, diagnostically speaking. We even set up DNS servers and everything. I don't know what's wrong and this is bugging me. ;_;

Oh and I'm running Adium 0.89.1 on a 14 inch iBook.

Same going on here, I'm using 1.0b11 and the first time I noticed it was right after the change on AIM servers. I was starting to think it was because of the same thing that had caused the joscar errors. Seeing as you have the same problem and are using 89.1 as well as everyhing else, than it seems to me to be server side.

If its server side, what does that mean? Sorry, I'm kind of dense when it comes to this kind of stuff.

iceydeville wrote:If its server side, what does that mean? Sorry, I'm kind of dense when it comes to this kind of stuff.

It means the service provider has made a change in their software/equipment that is causing a problem for you and that no one outside the provider can provide a solution [most likely].

Have you tried it with a different service?

You mean like with MSN or like with iChat/Meebo/AIM?

Like MSN.

iChat/Meebo/AIM are clients.

I actually don't have any issues with using other ISPs (ie, I'm at my house now and AIM works fine). However, when I'm using my apartment's service, AIM starts to lag. Do you think its a port issue?

Also: Have not been able to try MSN because I don't really have MSN friends...

iceydeville wrote:I actually don't have any issues with using other ISPs (ie, I'm at my house now and AIM works fine). However, when I'm using my apartment's service, AIM starts to lag. Do you think its a port issue?

Also: Have not been able to try MSN because I don't really have MSN friends...

Make sure you're comparing apples to apples - the iBook and Adium on AIM, wired each time. Or wireless each time. Also check the time of day.

FWIW, I've noticed a lag in AIM also. Mid afternoon and mid evening (east coast US time) seem worse recently. Traceroutes show the 'net between me and AOL's network are fine. The problem is the last few hops within AOL's 'net and the servers themselves.

So try running a traceroute to the AIM server... It might show you where the difficulty is.

- Dan.

Sorry. What is a traceroute and how do I do it?

iceydeville wrote:Sorry. What is a traceroute and how do I do it?

It's a unix command. You can do it from Terminal or from Apple's Network Utility. It shows you the route your packets are taking, by sending out a series of pings and listening for the returns. The times it provides are the round trip lag it took to send the packet and get it back. As each hop progresses, the time should increase by a reasonable amount. When you see one jump wildly, there's something wrong. Google on 'traceroute' and 'ping' to learn more.

First you need to figure out what AIM server you're talking to. The easy way is from Activity Monitor. Select the Adium task and hit cmd-I (view/inspect process). Then click on the open files & ports tab. Give it a bit to fill in. Scroll down, basically to the end. Locate a line that looks like this:

[::192.168.0.16]:58002->[::205.188.1.104]:aol

Copy the IP on the right.
Now go into Terminal and say "traceroute " and hit paste...
You'll get something like this:
traceroute to 205.188.1.104 (205.188.1.104), 64 hops max, 40 byte packets
1 192.168.0.2 (192.168.0.2) 19.539 ms 2.845 ms 9.014 ms
2 72.73.230.1 (72.73.230.1) 6.353 ms 47.505 ms 11.519 ms
3 p1-1.lcr-02.cmdnnj.verizon-gni.net (130.81.32.186) 7.754 ms 7.566 ms 6.433 ms
4 130.81.17.165 (130.81.17.165) 13.010 ms 11.084 ms 14.096 ms
5 pop1-nye-p10-1.atdn.net (66.185.141.17) 106.225 ms 21.809 ms 13.500 ms
6 bb2-nye-p0-0.atdn.net (66.185.151.50) 13.298 ms 13.780 ms 13.443 ms
7 bb2-vie-p12-0.atdn.net (66.185.152.201) 19.394 ms 45.274 ms 20.706 ms
8 pop1-vie-p1-0.atdn.net (66.185.139.83) 20.227 ms 21.141 ms 18.713 ms
9 dar2-dtc-s0-0-0.atdn.net (66.185.141.114) 20.451 ms 125.705 ms 27.156 ms
10 * * *
11 * * *
12 205.188.1.104 (205.188.1.104) 80.953 ms 21.403 ms 22.231 ms

Ignore hops 10 and 11. Those are routers that are configured to not respond to pings. The critical hop is that last one. The times you see above are pretty good. When AIM lags on me, I see those times as over 200 ms.

HTH,
- Dan.

I ran the traceroute and the last one was running at about 60 ms.

I've been talking to some of my friends and they are having timing out/crashing/lagging issues with AIM also. So I really think its the server. However, the problem is more apparent when I'm using my wired connection at my apartment than when using the campus's wireless or my house's wireless. In fact, I don't have issues when I'm connected via wireless.

Thanks!

1 gw (66.135.188.1) 93.656 ms 2.116 ms 1.729 ms
2 s1-0-1-26.c1.dfw.ygnition.net (24.219.240.101) 24.433 ms s1-1-0-26.c1.dfw.ygnition.net (66.135.176.229) 15.876 ms s1-1-0-28.c1.dfw.ygnition.net (66.135.176.237) 44.852 ms
3 mdf1-bi8k-1-ve-170.dal1.attens.net (63.241.199.137) 29.693 ms 40.777 ms 43.815 ms
4 mdf1-gsr12-1-gig-2-1.dal1.attens.net (63.241.192.41) 27.710 ms 28.663 ms 21.119 ms
5 gar5-p330.dlstx.ip.att.net (12.122.255.81) 35.224 ms 30.421 ms 22.764 ms
6 tbr1010801.dlstx.ip.att.net (12.123.16.210) 139.018 ms 37.295 ms 13.728 ms
7 ggr2-p300.dlstx.ip.att.net (12.123.16.1) 24.444 ms ggr2-p340.dlstx.ip.att.net (12.123.16.25) 29.513 ms ggr2-p300.dlstx.ip.att.net (12.123.16.1) 12.120 ms
8 pop1-dls-p3-0.atdn.net (66.185.134.37) 250.934 ms 52.154 ms 21.469 ms
9 bb1-dls-p0-0.atdn.net (66.185.133.80) 21.370 ms 23.928 ms 159.059 ms
10 bb1-hou-p6-0.atdn.net (66.185.152.133) 62.223 ms 27.897 ms 33.044 ms
11 bb1-atm-p7-0.atdn.net (66.185.152.184) 40.774 ms 119.398 ms 147.242 ms
12 bb2-atm-p1-0.atdn.net (66.185.152.181) 45.227 ms 57.925 ms 66.833 ms
13 bb2-rdu-p4-0.atdn.net (66.185.152.31) 231.782 ms 143.195 ms 62.787 ms
14 bb1-rdu-p2-0.atdn.net (66.185.152.2) 179.179 ms 55.452 ms 147.594 ms
15 bb1-vie-p12-0.atdn.net (66.185.152.15) 90.389 ms 60.605 ms 59.090 ms
16 pop2-vie-p0-0.atdn.net (66.185.139.129) 327.320 ms 45.155 ms 164.938 ms
17 dar2-mtc-s0-0-0.atdn.net (66.185.139.134) 85.799 ms 248.335 ms 70.997 ms
18 * * *
19 * * *
20 64.12.31.104 (64.12.31.104) 63.581 ms 67.489 ms 198.055 ms

My life is pain.