Can't fully connect

Hey,

I have been following this tutorial: http://dev.aol.com/creating-aim-enabled-applications-java1
trying just to get a screen name to connect fully to AIM. I'm not worried about the rest yet because I'm going in a different direction with it anyway.

So I set up my environment in Eclipse, using JRE 1.6, and I thought I had everything working until I tried to connect. Things go well at first, but I can't get the connection to finish. Here is the output:
ConnectingACC_S_OK
ValidatingACC_S_OK
TransferringACC_S_OK
OfflineACC_E_DISCONNECTED

and the sn never shows up as being online.

according to the tutorial, it's supposed to be
ConnectingACC_S_OK
ValidatingACC_S_OK
TransferringACC_S_OK
NegotiatingACC_S_OK
StartingACC_S_OK
OnlineACC_S_OK

I tried running accbot.exe, from under the dist directory of the SDK, in a terminal, and it didn't fully work either. Here is the output:
accbot initializing...
accbot connecting...
accbot offline, qutting.
accbot shutting down with hr=8004023F.

Because accbot failed too, I'm guessing this problem is on my end. Could this have anything to do with ports being closed? Our network admin here is not really willing to open any ports, so I'm hoping there is another fix for this.

Any ideas?

Thanks!

Thanks for the help, but

Thanks for the help, but this is definitely a network problem. I ran my code from another location and everything worked fine. As annoying as it is, I'm just going to work from somewhere else.

Thanks again!

(this is AndrAIM1, btw)

TCP Log

Ok, I captured a tcp log, but i'm really not sure what to do now. It seems to be coming up with checksum errors all over the place.

I posted it here: http://straightforwardcode.com/aim/tcp%20cap_img.png

Please let me know if you know what that means or if you need more info.

The errors all look something like this, though obviously the actual checksums vary:

Checksum: 0x4b04 [incorrect, should be 0x4ddc (maybe caused by "TCP checksum offload"?)]

Thanks

Re: Can't fully connect

You don't need any ports open locally to login. Yeah, 0x8004023F is ACC_E_DISCONNECTED, which implies a networking issue. Maybe try an official AIM client to see what happens. If AIM traffic is being blocked you might have to connect through a proxy.

Thanks irabiz. The official

Thanks irabiz.

The official release of AIM does work on the same computer on the same network with no problems at all.

Any other advice on debugging the problem? I'm going to see if I can try it on another network, but if that doesn't work, I'm kind of at a loss for what to do.

Help appreciated.

Re: Thanks irabiz. The official

That narrows it down some. AIMCC 1.6 has a bug that login fails if the local machine's system clock is way off. Is your system clock way off?

Now I wish it was, but no,

Now I wish it was, but no, my system clock is synchronized with Windows time and is accurate.

Re: Now I wish it was, but no,

Ugh! The next step may be to capture a TCP log using Ethereal or similar, if you're willing.