Ichat/login to AIM too often

I continue to get an error message from iChat that i have logged in to AIM too often in a short period of time and need to wait to log in again. When i wait, I can occassionally get in, but then I get kicked out again and start the process over. Has anyone else had this problem? Any settings that might help with this?
Thanks
drew

http://discussions.apple.com/search.jspa?threadID=&q=too%2Boften&objID=f902&date Range=last90days&userID=&numResults=15&rankBy=10001
5:46 PM Monday; March 24, 2008

Similar Messages

IChat login problems AIM vs .Mac account

I am having problems logging in to iChat AV 3.1
Using my AIM profile I can log in with no problems whatsoever, but if I try to login using my .mac account, I get the "unable to login - username or password incorrect". I know for a fact that I'm typing my username and pass correctly because I can still login to .mac on the web. Any suggestions? The only thing I can come up with is that maybe it doesn't work with .mac trials? Getting this program to run is the only thing stopping me from dropping the $99 for the account. And yes, I have visited Ralph's awesome website, but still no help.

HI Jimmy,
Is the password for the .Mac account over 16 characters ?
AIM only allows upto 16 - whereas .mac allows more than 20.
Ralph

Can't connect to AIM - Login too often in short period of time

Just recently my iChat AIM connection has been giving me this error message
"Could not connect to AIM
You have attempted to login too often in a short period of time. Wait a few minutes before trying to login again."
The first message came up at 7.25pm. I waiting until 7.30pm. Same message.
I waited until 7.40pm. Same message
I quit iChat and tried again at 7.45pm. Same message.
I've restarted twice. Same message.
I've "reset iChat" by moving the .plists for ichat. Same message.
What should i do? You'd think 10 minutes would be ok to try logging in again.

Hi
He might of done this.
Try this log on to AIM on port 443 rather than port 5190
Go to IChat > Preferences > Accounts.
Log out of AIM and then use the Server Settings tab
Set the port to 443.
Log back in again.
Tony

You have attempted to login too often...

We recently got Wi-fi set up in our house, since then ichat will not work. I will log in and it shows that none of my friends are online, then after about 2 or 3 minutes Ichat will log out then log in rapidly on its own. Then I get a message that says. "You have attempted to login too often in a short period of time. wait a few minutes before trying to login again." Then when I try to login again the same thing happens. can anyone help?

Hi,
It can be for a Number of reasons.
One speculation is that the AIM servers get busy with AIM and ICQ members and now BEBO all using the same port. (not to mention all the apps that can log into AIM and the AOL ISP Browser that can IM)
As iChat uses port 5190 on the TCP Protocol to Login but uses port 5190 on UDP to Send Files, Pics in Chats & Direct Messaging and certain Buddy List updates Buddies coming and going) - some routers and modems that route do not seem to like this double use of port 5190 (it certainly effects Zyxels devices).
Sort of related, with Devices set up to Port Forward, a port can normally only be forwarded once (to one IP), so this seems, to some that specify Protocols as well, as doing it twice.
Apple have an Article that I don't have link for about Some Netgears needing to change this port.
More generally though port 443 is open in most routers and routing modems as it is under the threshold of 1024.
All ports below this are open.
It allows Web Browsers and Mail apps to use the ports they use without any set up.
Several routers can be linked together without any input and these apps will still work.
Port 443 is used by secure Web Sites such as Banks and the like and the Apple Discussions Login Page.
It is also used by mail apps to access some mail servers.
Therefore dropping the login port in iChat to this port is likely to find it is open in any router.
Pre Leopard the above also used to apply to the way the Mac Firewall worked as ports had to be specifically listed. This means if a ports is open for one app other apps can "Piggy Back" that usage.
In Leopard the App is "Certificated" and even if it allows a Port it will not be open for another app that is nt allowed to use the firewall.
Hope this helps.
5:48 PM Saturday; May 9, 2009

Error message - could not connect to aim - too many attempts to login

Today when I tried to iChat, I got a message I haven't seen before. The error message reads "You have attempted to lgin too often in a short period of time. Wait a few minutes before trying to login again." I did notice my window continuing to try and login -- not sure why it wouldn't. I did install a new router yesterday and my internet works fine. Would this have some impact on iChat? Or are there certain settings I might need to change?

Hi,
If you are on 10.6.x did the port change stick ?
SSL tends to have to be On and the Enter key needs to be used to "Set" the port.
On the Netgear access the WNA set up page.
Turn Off the Port scan and DOS (Or SPI) and Disable the Ping Blocking.
(Apply/Save Settings)
9:12 PM Tuesday; May 4, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

Ichat won't login to aim account

I have snow leopard. and ichat was working fine. then my router died so I bought a new on a netgear wnr3500v2. everthing works great, except ichat. I can use aim software to see aim buddies, but when I try to use ichat to see aim buddies, I get disconnect error.
I replaced netgear router with a linksys router and the problem went away.
I tried all of the suggestions posting at netgear, and other websites before buying a new router, and I called netgear, who stated that it was a aim issue.
so my advice is avoid netgear routers if you use ichat.

Hi,
Welcome to the  Discussions
Netgears on the whole come with UPnP turned On so that the iChat Login on port 5190 would normally work.
(AIM uses fall back ports to get around firewall setting using Mail and Web Browsing ports if port 5190 is not open)
Not all Netgears though have UPnP enabled and this may have been the issue.
There about two models that have difficultly with iChat Audio Only and Video Chats but this can depend on which version of those model you have.
Having had a Netgear DG834G and knowing other people who post regularly in the iChat Forums have also had various Netgears I would have a different view to yours.
3:07 PM Saturday; February 20, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

IChat login problem. Anyone know how to fix it?

I've got iChat 4 and it usually works just fine for me with my AIM account but for some reason today every time i try and log in it first appears like it's logged in successfully but doesn't show any buddies online when they are and then a few seconds later it starts connecting & disconnecting over and over until i get a iChat Connection Alert saying:
Could not connect to AIM
you have attempted to login too often in a short period of time. Wait a few minutes before trying to login again.
I then wait for a while and try and log in again but the same thing keeps happening and i haven't the slightest idea how to stop this from happening.
Does anyone know how to stop this from happening?

At this stage there seems to be three levels of this problem.
1) You have Logged in Too many times is normally solved by deleting com.apple.iChat.AIM.plist and restarting iChat
2) The extreme is to have no displayed Buddy List despite looking like you are logged in. This require ichat to be Quit - Activity Monitor used to Force Quit iChatAgent as it does not quit with iChat - The deletion of both com.apple.iChat.AIM.plist and com.apple.iChatAgent.plist
3) Anything else is sort of in between and should get away with just the double .plist deletion.
The .plists are in User/(your account)/Library/Preferences
Restart iChat afterwards
8:54 PM Friday; January 18, 2008

Can and Can't login to AIM

I've upgraded to a 27" iMac and am having problems with iChat and AIM. When I first got the new iMac I was able to login to AIM using iChat. Now I can't -- it keeps reporting that I'm using the wrong password. BUT, I CAN still login to AIM using my old iMac and the same PW on the same Network, so I know it's not the PW [the PW works on my iPhone, too].
I'm using the same settings on each machine. I've changed the port to 443 on the new iMac [same as the old one], I've followed the advice I've seen in other posts and confirmed that the Keychain has the correct PW and I deleted com.apple.ichat.AIM.plist.
I even checked the Firewall setting to make sure that signed software can receive incoming connections.
Is there anything else I can try?

Hi,
Any AIM valid account/Screen Name which in this case includes those from Apple (MobileMe and @mac.com IDs) will report there is a second Login if in the iChat > Preferences > Accounts you have not got Allow Multiple Logins ticked.
A Multiple Login can be caused by a AIM Express Login with the same Screen Name or from a Second computer using iChat or any other AIM client.
Of course a Phone that can login to AIM messaging of any sort can also be Second Login.
It is strange that you had the message show up on the computer that was already Logged in.
The Presumption is you get the message at work for Instance if you leave your Home computer logged in or vice versa and you get the message on the computer/device you are trying to Login.
The Message from AIMSysteMessage (the Screen Name that sends you the Message) allows you to type a " 1 " as the response and will then log out the First computer/device (if you type " 2 " then the current attempt to login is ended).
Also logging on to the AIM web site and not specifically logging out may get the default Login period to kick in (two weeks) and may also be the cause of a Second Login.
Another cause may be using sites like Meebo and BeBo and other social sites that allow Linking to your Buddy Lists.
If one iChat is reporting that the @me.com name is logged in twice then it will be that Screen Name not the plain AIM one.
Other things to look at.
On the new computer that is using the MobileMe name what is the Login port that the Screen Name is using ?
iChat > Preferences > Accounts > Server Settings
What ports is the AIM Name managing to Login with on the other Computer ?
Are you setting the Screen Name to allow Multiple Logins ?
4:00 PM Tuesday; February 16, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

IChat login/timing out. . . .Only on one account

Ok so i turn on my computer this morning and it times out when ever i try to login to aim using ichat. i though it might because i had i updated ichax last week so i uninstalled ichax and still it times out so then i signed using another aim account and it worked with no probelm. deleted all accounts and then tried my account info again but it still timed out. i also tried switching the ports
i am running 10.4.6
ichat v. 3.1.4
i looked at a bunch of threads involving ichat timing out but nothing seemed to anwser is prob thanks

Hi Rick,
I am aware that you are posting in serveral threads with an issue you have.
I am unable to gauge what the exact issue is with this fragmented approach.
Could you start your own thread and list what the problem is is as much detial as you have and what you have tried please
This item may help
http://discussions.apple.com/thread.jspa?threadID=527902
1:41 PM Wednesday; August 2, 2006

IChat 5 to AIM (Any version) frustrations

This has been driving me insane for a week.
I can connect PC to PC on AIM for video conference. I can connect Mac to Mac for an iChat conference. They work when both computers are on the same office network. They work when one of the computers is remote, so it even traverses our firewall and routers without issue. Under no circumstances will an AIM to iChat video conference fully connect.
I've used multiple computers, and no computer has a software firewall enabled. I have tried AIM 5.5, 5.9, 6.5, 6.9, and currently have the latest 7.2.61 installed.
Here is a trace from a PC initiated Video Chat request (it ends with "There was a comm. error during your chat" on the Mac, and the PC remains sitting on "Waiting for Buddy Confirmation"):
Sorry about the ludicrous length of this log file...
sl-masterimage:~ dkephart$ /Applications/iChat.app/Contents/MacOS/iChat -errorLogLevel 7
133405.617376 ER_AddFilter (0): Adding [Dave [email protected]]->[0]
133405.617408 setLocalUserName: Dave [email protected]
133405.626036 Default video size is (640 x 480)
133405.627519 H264: (640 x 480) @ 30 fps
133405.630423 H264: (320 x 240) @ 30 fps
133405.633236 H263: (352 x 288) @ 30 fps
133405.634654 H263: (176 x 144) @ 30 fps
133405.634788 ######################################
133405.634796 # SoundDec_Create(16000 --> 3) #
133405.634800 ######################################
133405.688435 Leaving SoundDec_Create
133405.690785 ### NEW STATE: to: VC_INIT, from: VC_INVALID
133405.690825 ### NEW STATE: to: VC_IDLE, from: VC_INIT
133405.690842 ++++++++ confStatusMapRemoveAll
133405.690848 ( ) -- mapUserIDToSecurityInfo cleared --
133405.691244 dispatch_CommNATProc
133405.719894 selectedCamera: no camera has been set yet.
133405.719930 selectedCamera: no camera has been set yet.
133405.719940 selectedCamera: no camera has been set yet.
133405.719954 selectedCamera: no camera has been set yet.
133405.719962 Selected microphone is the null device microphone.
133405.720020 vcCapabilitiesOfCPU returns: 0x00000fff
133405.720130 BWD: GotBandwidth: 4189237/3516856 (up/down) @[227.3.16.172:0.0.255.255]
133405.720221 BWD bandwidth: 4189 kbits up, 3516 kbits down.
133405.720230 videoNetworkCapable: 1 -- 3 max participants.
133405.720234 audioNetworkCapable: 1 -- 9 max participants.
133405.720239 Supports PCMU wideband for audio: 1 / video: 1
133405.720258 vcCapabilitiesOfNetwork returns: 0x00000fff
133405.720265 vcCapabilitiesOfRouter returns: 0x00000000
133405.720269 vcCapabilities returns: 0x00000fff
133405.721587 Found 2 cameras:
133405.721617 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)
133405.721664 HP Deluxe Webcam KQ246AA - 0xfd40000004f2a13c (0x104, 0x0)
133405.721676 selectedCamera: no camera has been set yet.
133405.721693 selectCameraWithTundraDeviceID: 0x104 returned 1
133405.730783 Microphone devices:
133405.730924 Line In
133405.730986 Digital In
133405.731054 HP Deluxe Webcam KQ246AA
133405.731141 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133405.731176 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133405.731202 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133405.731402 Selected mic: HP Deluxe Webcam KQ246AA
133405.731461 Found 2 cameras:
133405.731491 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)
133405.731519 HP Deluxe Webcam KQ246AA - 0xfd40000004f2a13c (0x104, 0x0)
133405.731542 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133405.731559 selectCameraWithTundraDeviceID: 0x104 returned 1
133405.739837 Microphone devices:
133405.739942 Line In
133405.740002 Digital In
133405.740067 HP Deluxe Webcam KQ246AA
133405.740135 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133405.740165 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133405.740199 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133405.740389 Selected mic: HP Deluxe Webcam KQ246AA
133406.240786 Selected microphone is HP Deluxe Webcam KQ246AA.
133406.240995 Selected microphone is HP Deluxe Webcam KQ246AA.
133406.244428 Found 2 cameras:
133406.244466 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)
133406.244510 HP Deluxe Webcam KQ246AA - 0xfd40000004f2a13c (0x104, 0x0)
133406.244539 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133406.244557 selectCameraWithTundraDeviceID: 0x104 returned 1
133406.252700 Microphone devices:
133406.252825 Line In
133406.252885 Digital In
133406.252951 HP Deluxe Webcam KQ246AA
133406.253041 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133406.253077 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133406.253112 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133406.253309 Selected mic: HP Deluxe Webcam KQ246AA
133406.253794 Selected microphone is HP Deluxe Webcam KQ246AA.
133406.264034 Found 2 cameras:
133406.264078 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)
133406.264124 HP Deluxe Webcam KQ246AA - 0xfd40000004f2a13c (0x104, 0x0)
133406.264153 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133406.264172 selectCameraWithTundraDeviceID: 0x104 returned 1
133406.272673 Microphone devices:
133406.272801 Line In
133406.272866 Digital In
133406.272935 HP Deluxe Webcam KQ246AA
133406.273039 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133406.273072 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133406.273099 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133406.273295 Selected mic: HP Deluxe Webcam KQ246AA
133406.273800 Selected microphone is HP Deluxe Webcam KQ246AA.
133420.985694 Comm reporting flags: 000000EC
133421.158867 CommNAT result:
External IP: 63.161.132.29
External Ports: 36870, 36872, 36871
CNAT_BADTEST ....... 0
CNAT_ISFULLCONE .... 0
CNAT_ISPAT ......... 1
CNAT_ISPATHOST ..... 1
CNAT_TRYPRESERVE ... 0
CNAT_PATINORDER .... 1
CNAT_BLOCKIP ....... 1
CNAT_BLOCKPORT ..... 1
CNAT_LOOPBACK ...... 0
133421.439173 vcCapabilitiesOfCPU returns: 0x00000fff
133421.439312 BWD: GotBandwidth: 4189237/3516856 (up/down) @[227.3.16.172:0.0.255.255]
133421.439329 BWD bandwidth: 4189 kbits up, 3516 kbits down.
133421.439336 videoNetworkCapable: 1 -- 3 max participants.
133421.439340 audioNetworkCapable: 1 -- 9 max participants.
133421.439344 Supports PCMU wideband for audio: 1 / video: 1
133421.439357 vcCapabilitiesOfNetwork returns: 0x00000fff
133421.439362 vcCapabilitiesOfRouter returns: 0x00008000
133421.439367 vcCapabilities returns: 0x00008fff
133421.481315 TundraCapture_SetImageSize: requested size (640x480) new size (640x480:25.000000) vide:yuvs
133421.526821 Microphone: callback thread: STANDARD; EXTENDED timeshare: 0; PRECEDENCE importance: 17
133421.527095 Microphone: null device thread: STANDARD; EXTENDED timeshare: 0; PRECEDENCE importance: 17
133421.571776 Microphone devices:
133421.571918 Line In
133421.571981 Digital In
133421.572051 HP Deluxe Webcam KQ246AA
133421.572140 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133421.572178 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133421.572204 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133421.572497 Selected mic: HP Deluxe Webcam KQ246AA
133421.573021 VTPRecvProc thread(682356736) started...
133421.573205 SIPManager init with protocol: 0.
133421.573296 1 interfaces found.
133421.573386 VTP set fd(10) buf size send[9216->225000] recv[42080->225000]
133421.573477 Start listening on 172.16.3.227:16402(en1) sock 100
133421.573517 1 valid interfaces found.
133421.573743 Transport(UDP) Thread start...
133421.573758 Transport checking map for interface = en1, port = 16402
133421.573835 [0]Creating a port mapping from on interface 0 from external port 57110 to local port16402...
133421.574171 TPListen on port 16402
133421.574229 dispatch_AcquireSNATMAPConfigurationProc
133421.574934 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133421.676392 Diffusion prefilter disabled
133421.676428 Temporal prefilter disabled
2010-03-19 13:34:21.676 iChat[30194:14003] ------ startPreview: previewing: 2
133421.676906 startPreview returned 0
133421.809869 SNATMAP Configuration: snatmap.mac.com:5678
133422.501177 Video size change from 0x0 to 640x480(1280)
133425.074710 in callback
133425.074740 -sdRef 0x1248499c0 ?
133425.074745 -flags = 00000000
133425.074750 -IFIndex 0 ?
133425.074753 -errorCode == 00000000
133425.074761 -publicAddr == 0.0.0.0
133425.074765 -proto == 16
133425.074771 -privPort == 16402
133425.074775 -publPort == 0
133425.074778 -ttl == 0
133427.412491 VCDelegate conforms to VideoConferenceDelegate protocol.
133427.412537 ER_AddFilter (1): Adding [thekephart]->[0]
133427.412549 setLocalUserName: thekephart
133427.412559 ( ) setValidatedIdentity: [00000000]
133427.414409 external IPInfo collection start : 21.720540
133427.415579 SNATMAP server [17.250.248.149:5678]
133427.415666 sent SNATMAP request for [172.16.3.227:16402]
133427.456962 Found 2 cameras:
133427.457009 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)
133427.457057 HP Deluxe Webcam KQ246AA - 0xfd40000004f2a13c (0x104, 0x0)
133427.457097 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133427.457135 selectCameraWithTundraDeviceID: 0x104 returned 1
133427.464427 Microphone devices:
133427.464528 Line In
133427.464588 Digital In
133427.464650 HP Deluxe Webcam KQ246AA
133427.464723 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133427.464755 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133427.464782 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133427.465040 Selected mic: HP Deluxe Webcam KQ246AA
133427.478902 Selected microphone is HP Deluxe Webcam KQ246AA.
133427.874011 VTP_IFIndexToName mapping [if_index:5 if_name:en1]
133427.874125 SNATMAP mapping [63.161.132.29:36985]
133427.874154 external IPInfo collection done : 22.180265
133427.874173 LOCAL: ifname=[external], IPPORT=[63.161.132.29:36985]
133427.874179 LOCAL: ifname=[en1], IPPORT=[172.16.3.227:16402]
133427.874184 LOCAL: ifname=[en1~], IPPORT=[83.239.252.28:16402]
133427.874205 Obtained 120 bytes of local IP and port data (3 entries). Remote data was 0 bytes (0 entries).
133429.692042 Initiate conference to user: [email protected] with 80 bytes of connection data.
2010-03-19 13:34:29.692 iChat[30194:150c3] Connection dictionary: {
IPAndPortData = <00000000 656e3000 00000000 00000000 00000000 3fa1841b 00000000 00000000 00000000 1f700000 00000000 656e3000 00000000 00000000 00000000 ac1003b4 00000000 00000000 00000000 1f700000>;
version = 1;
133429.692709 [[** sMT - MTHelper_AttemptCall] [0][user:[email protected]][Caller] [total_current user = 0][Non-SL][remoteCommNAT 0][isRelay 0]
133429.692756 Invoke delegate method vcc:initiateConferenceStartedForParty:([email protected])
133429.692784 ### NEW STATE: to: VC_SIGNALING, from: VC_IDLE
133429.692792 initiateConferenceCallUsingConnectionDataWithErrorInfoToUser - start
133429.692804 Callee connection data 277 bytes. Caller connection data 0 bytes.
133429.692817 ( )( )( ) ---- <nil> valid returned 0
133429.692851 Remote party is using AIM 5.9 client.
133429.692935 =========== OpenPorts!
133429.698833 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133429.699284 * Caller SDP *
133429.699463 v=0
o=dkephart 0 0 IN %RTP-IP-AF% %RTP-IP%
s=thekephart
c=IN %RTP-IP-AF% %RTP-IP%
b=AS:2147483647
t=0 0
a=hwi:1056:4:2660
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio %ARTP-PORT% RTP/AVP 110 12 124 3 0
a=rtcp:%ARTCP-PORT%
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:124 iLBC/8000
a=fmtp:124 mode=30
a=rtpID:2980891041
m=video %VRTP-PORT% RTP/AVP 123 126 34
a=rtcp:%VRTCP-PORT%
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO %ARTCP-PORT% VIDEO %VRTCP-PORT%
a=fmtp:126 imagesize 0 rules 30:640:480:640:480:30
a=fmtp:123 imagesize 0 rules 30:640:480:640:480:30
a=rtpID:2387265385
133429.699481 <<<<<<<<<< Conference initiation API version 1 >>>>>>>>>
133429.699499 [ipAndPortData length] = 80
133429.699505 Length is valid: YES
133429.699526 CALLEE: ifname=[en0], IP=[63.161.132.27:8048]
133429.699540 CALLEE: ifname=[en0], IP=[172.16.3.180:8048]
2010-03-19 13:34:29.699 iChat[30194:1550b] IPAndPortList: (
ip = "63.161.132.27";
port = 8048;
ip = "172.16.3.180";
port = 8048;
133429.699808 SIPConnect start...
133429.699818 ER_AddFilter (2): Adding [[email protected]]->[u0]
133429.700057 SIP IPPort: local=[172.16.3.227:16402] src=[63.161.132.29:36985] remote=[63.161.132.27:8048] dst=[63.161.132.27:8048]
133429.700073 ER_AddFilter (3): Adding [172.16.3.227]->[lip]
133429.700080 ER_AddFilter (4): Adding [172-16-3-227]->[lip]
133429.700086 ER_AddFilter (5): Adding [63.161.132.27]->[rip]
133429.700092 ER_AddFilter (6): Adding [63-161-132-27]->[rip]
133429.700098 ER_AddFilter (7): Adding [63.161.132.29]->[sip]
133429.700103 ER_AddFilter (8): Adding [63-161-132-29]->[sip]
133429.700206 TAInviteClientProc Thread start...
133429.700312 ( )( )( )( )( ) TP IS BINARY? (0)
133429.700326 RTP using 172.16.3.227:16402 and 63.161.132.29:36985 as hints
133429.700439 VTP set fd(16) buf size send[9216->225000] recv[42080->225000]
133429.700609 RTP vfd (102) accepts pkt (0010)
133429.700622 RTCP vfd (103) accepts pkt (0040)
133429.700627 RTP/RTCP ports for PayloadType 1 are 16402(102) and 16401(103)
133429.700691 VTP set fd(17) buf size send[9216->225000] recv[42080->225000]
133429.700820 RTP vfd (104) accepts pkt (0008)
133429.700838 RTCP vfd (105) accepts pkt (0020)
133429.700844 RTP/RTCP ports for PayloadType 0 are 16402(104) and 16400(105)
133429.700850 Overriding Video RTCP port from 16402 to 16401
133429.700856 Overriding Video RTCP port from 16402 to 16400
133429.700932 sent SNATMAP request for [172.16.3.227:16401]
133429.700958 sent SNATMAP request for [172.16.3.227:16400]
133430.153273 SNATMAP mapping [63.161.132.29:37044]
133430.153307 SNATMAP mapping [63.161.132.29:37045]
133430.153347 Send to 63.161.132.27:8048 [INVITE sip:[email protected]:8048 SIP/2.0
Via: SIP/2.0/UDP 63.161.132.29:36985;branch=z9hG4bK318a6e63668dd3b6
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:8048>
From: "thekephart" <sip:[email protected]:16402>;tag=1199148638
Call-ID: 1df337dac2d9482-337d-11df-9fd0-a8382a8c4012@172-16-3-227
CSeq: 1 INVITE
Contact: <sip:[email protected]:36985>;isfocus
User-Agent: Viceroy 1.4
Content-Type: application/sdp
Content-Length: 695
v=0
o=dkephart 0 0 IN IP4 63.161.132.29
s=thekephart
c=IN IP4 63.161.132.29
b=AS:2147483647
t=0 0
a=hwi:1056:4:2660
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 36985 RTP/AVP 110 12 124 3 0
a=rtcp:37045
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:124 iLBC/8000
a=fmtp:124 mode=30
a=rtpID:2980891041
m=video 36985 RTP/AVP 123 126 34
a=rtcp:37044
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 37045 VIDEO 37044
a=fmtp:126 imagesize 0 rules 30:640:480:640:480:30
a=fmtp:123 imagesize 0 rules 30:640:480:640:480:30
a=rtpID:2387265385
133430.653514 ( )( )( )( )( ) TP IS BINARY? (0)
133430.653561 Send to 63.161.132.27:8048 [INVITE sip:[email protected]:8048 SIP/2.0
Via: SIP/2.0/UDP 63.161.132.29:36985;branch=z9hG4bK318a6e63668dd3b6
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:8048>
From: "thekephart" <sip:[email protected]:16402>;tag=1199148638
Call-ID: 1df337dac2d9482-337d-11df-9fd0-a8382a8c4012@172-16-3-227
CSeq: 1 INVITE
Contact: <sip:[email protected]:36985>;isfocus
User-Agent: Viceroy 1.4
Content-Type: application/sdp
Content-Length: 695
v=0
o=dkephart 0 0 IN IP4 63.161.132.29
s=thekephart
c=IN IP4 63.161.132.29
b=AS:2147483647
t=0 0
a=hwi:1056:4:2660
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 36985 RTP/AVP 110 12 124 3 0
a=rtcp:37045
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:124 iLBC/8000
a=fmtp:124 mode=30
a=rtpID:2980891041
m=video 36985 RTP/AVP 123 126 34
a=rtcp:37044
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 37045 VIDEO 37044
a=fmtp:126 imagesize 0 rules 30:640:480:640:480:30
a=fmtp:123 imagesize 0 rules 30:640:480:640:480:30
a=rtpID:2387265385
133431.653715 ( )( )( )( )( ) TP IS BINARY? (0)
133431.653755 Send to 63.161.132.27:8048 [INVITE sip:[email protected]:8048 SIP/2.0
Via: SIP/2.0/UDP 63.161.132.29:36985;branch=z9hG4bK318a6e63668dd3b6
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:8048>
From: "thekephart" <sip:[email protected]:16402>;tag=1199148638
Call-ID: 1df337dac2d9482-337d-11df-9fd0-a8382a8c4012@172-16-3-227
CSeq: 1 INVITE
Contact: <sip:[email protected]:36985>;isfocus
User-Agent: Viceroy 1.4
Content-Type: application/sdp
Content-Length: 695
v=0
o=dkephart 0 0 IN IP4 63.161.132.29
s=thekephart
c=IN IP4 63.161.132.29
b=AS:2147483647
t=0 0
a=hwi:1056:4:2660
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 36985 RTP/AVP 110 12 124 3 0
a=rtcp:37045
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:124 iLBC/8000
a=fmtp:124 mode=30
a=rtpID:2980891041
m=video 36985 RTP/AVP 123 126 34
a=rtcp:37044
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 37045 VIDEO 37044
a=fmtp:126 imagesize 0 rules 30:640:480:640:480:30
a=fmtp:123 imagesize 0 rules 30:640:480:640:480:30
a=rtpID:2387265385
133432.153913 Dialog(CREATED) Match(STATUS) [1df337dac2d9482-337d-11df-9fd0-a8382a8c4012@172-16-3-227]=[1df337dac2d9482-337 d-11df-9fd0-a8382a8c4012@172-16-3-227], [1199148638]=[1199148638]
133432.153957 TAInviteClientProc Thread end(800B0017)...
133432.153992 SIPConnect stop(900A0015)...
133432.154004 SIPConnect start...
133432.154230 SIP IPPort: local=[172.16.3.227:16402] src=[172.16.3.227:16402] remote=[172.16.3.180:8048] dst=[172.16.3.180:8048]
133432.154246 ER_AddFilter (9): Adding [172.16.3.180]->[rip]
133432.154254 ER_AddFilter (10): Adding [172-16-3-180]->[rip]
133432.154333 TAInviteClientProc Thread start...
133432.154372 ( )( )( )( )( ) TP IS BINARY? (0)
133432.154387 RTP using 172.16.3.227:16402 and 172.16.3.227:16402 as hints
133432.154411 Send to 172.16.3.180:8048 [INVITE sip:[email protected]:8048 SIP/2.0
Via: SIP/2.0/UDP 172.16.3.227:16402;branch=z9hG4bK168a0a5e20854b1c
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:8048>
From: "thekephart" <sip:[email protected]:16402>;tag=532265527
Call-ID: 1df337dada40ddc-337d-11df-9fd0-81d124d14012@172-16-3-227
CSeq: 1 INVITE
Contact: <sip:[email protected]:16402>;isfocus
User-Agent: Viceroy 1.4
Content-Type: application/sdp
Content-Length: 693
v=0
o=dkephart 0 0 IN IP4 172.16.3.227
s=thekephart
c=IN IP4 172.16.3.227
b=AS:2147483647
t=0 0
a=hwi:1056:4:2660
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 12 124 3 0
a=rtcp:16400
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:124 iLBC/8000
a=fmtp:124 mode=30
a=rtpID:2980891041
m=video 16402 RTP/AVP 123 126 34
a=rtcp:16401
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 16400 VIDEO 16401
a=fmtp:126 imagesize 0 rules 30:640:480:640:480:30
a=fmtp:123 imagesize 0 rules 30:640:480:640:480:30
a=rtpID:2387265385
133432.654559 ( )( )( )( )( ) TP IS BINARY? (0)
133432.654605 Send to 172.16.3.180:8048 [INVITE sip:[email protected]:8048 SIP/2.0
Via: SIP/2.0/UDP 172.16.3.227:16402;branch=z9hG4bK168a0a5e20854b1c
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:8048>
From: "thekephart" <sip:[email protected]:16402>;tag=532265527
Call-ID: 1df337dada40ddc-337d-11df-9fd0-81d124d14012@172-16-3-227
CSeq: 1 INVITE
Contact: <sip:[email protected]:16402>;isfocus
User-Agent: Viceroy 1.4
Content-Type: application/sdp
Content-Length: 693
v=0
o=dkephart 0 0 IN IP4 172.16.3.227
s=thekephart
c=IN IP4 172.16.3.227
b=AS:2147483647
t=0 0
a=hwi:1056:4:2660
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 12 124 3 0
a=rtcp:16400
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:124 iLBC/8000
a=fmtp:124 mode=30
a=rtpID:2980891041
m=video 16402 RTP/AVP 123 126 34
a=rtcp:16401
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 16400 VIDEO 16401
a=fmtp:126 imagesize 0 rules 30:640:480:640:480:30
a=fmtp:123 imagesize 0 rules 30:640:480:640:480:30
a=rtpID:2387265385
133433.654787 ( )( )( )( )( ) TP IS BINARY? (0)
133433.654837 Send to 172.16.3.180:8048 [INVITE sip:[email protected]:8048 SIP/2.0
Via: SIP/2.0/UDP 172.16.3.227:16402;branch=z9hG4bK168a0a5e20854b1c
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:8048>
From: "thekephart" <sip:[email protected]:16402>;tag=532265527
Call-ID: 1df337dada40ddc-337d-11df-9fd0-81d124d14012@172-16-3-227
CSeq: 1 INVITE
Contact: <sip:[email protected]:16402>;isfocus
User-Agent: Viceroy 1.4
Content-Type: application/sdp
Content-Length: 693
v=0
o=dkephart 0 0 IN IP4 172.16.3.227
s=thekephart
c=IN IP4 172.16.3.227
b=AS:2147483647
t=0 0
a=hwi:1056:4:2660
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 12 124 3 0
a=rtcp:16400
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:124 iLBC/8000
a=fmtp:124 mode=30
a=rtpID:2980891041
m=video 16402 RTP/AVP 123 126 34
a=rtcp:16401
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 16400 VIDEO 16401
a=fmtp:126 imagesize 0 rules 30:640:480:640:480:30
a=fmtp:123 imagesize 0 rules 30:640:480:640:480:30
a=rtpID:2387265385
133434.155024 Dialog(CREATED) Match(STATUS) [1df337dada40ddc-337d-11df-9fd0-81d124d14012@172-16-3-227]=[1df337dada40ddc-337 d-11df-9fd0-81d124d14012@172-16-3-227], [532265527]=[532265527]
133434.155065 TAInviteClientProc Thread end(800B0017)...
133434.155118 SIPConnect stop(900A0015)...
133434.155155 SIP connect returned 21
133434.155357 SIPCloseCall start...
133434.155366 (SIP.c:4278) Cannot find call ID(1)
133434.155372 SIPCloseCall stop(800C0016)...
133434.155490 [[** sMT - MTHelperEarly_EndCall] [0][user:[email protected]][RemoteUA:(RemoteUA - unknown)][Non-SL]
133434.155517 ### NEW STATE: to: VC_IDLE, from: VC_SIGNALING
133434.155535 ++++++++ confStatusMapRemoveAll
133434.155544 ( ) -- mapUserIDToSecurityInfo cleared --
133434.155559 [[** sMT - MTHelper_Relay] retCode = 0, desc = SIP Message Exchange (-8)]
133434.155566 Preparing to send VCInitiateConferenceCompleted
133434.155587 Invoke delegate method vcc:initiateConferenceCompletedForParty:([email protected]) - retcode: -8
133434.518610 endConference with userIDToCallIDMap count = 0
133434.748811 cancelPreview returned 0
133434.751237 Found 2 cameras:
133434.751275 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)
133434.751320 HP Deluxe Webcam KQ246AA - 0xfd40000004f2a13c (0x104, 0x0)
133434.751348 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133434.751365 selectCameraWithTundraDeviceID: 0x104 returned 1
133434.758695 Microphone devices:
133434.758799 Line In
133434.758860 Digital In
133434.758927 HP Deluxe Webcam KQ246AA
133434.759002 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133434.759038 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133434.759064 selectedCamera2 GUID returned HP Deluxe Webcam KQ246AA
133434.759255 Selected mic: HP Deluxe Webcam KQ246AA
133434.768973 Selected microphone is HP Deluxe Webcam KQ246AA.

Hi,
This has never been as simple as it should have been.
It in fact seems to have gotten more difficult as time has gone on.
iChat 3 to AIM 5.9 or 6.1 seemed to be the best it ever was.
This is about as much as we know to try
http://discussions.apple.com/thread.jspa?threadID=1968438
AIM on the PC uses port 5190 to Login, as does iChat (both Default settings)
Both can have this changed to port 443 - AIM uses it as "Fall Back" port if a firewall or router does not have the ports open.
AIM then goes on to use a random sort of port between port 1024 and 5000
These ports have to be opened in any routing device.
The PC firewall since XP service pack 2 has required you allow Exceptions through the firewall (any NON Microsoft app) and preferably also turn On UPnP hare as well so that any routing device can also use UPnP.
The SIP connection Process is supposed to "Negotiate" the ports to be used.
It usually or rather used to show on the Mac end and using the ichat ports (in ichat 3 Audio and Video where on 4 different ports in and out - 16384-16387 as first choices.
In later versions of iChat (4 and up) Video and audio is on one and it is used for both In and Out (port 16402)
However I use Little Snitch and this does not seem to be constant now and iChat will connect on seemingly random port if UPnP is used.
Your Log shows both ends moving ports during the connection Process.
In fact one part of the Log says this
133429.692851 Remote party is using AIM 5.9 client.
133429.692935 =========== OpenPorts!
It suggests that the ports are not open somewhere.
This info is also important
133421.158867 CommNAT result:
External IP: XX.XXX.XXX.XX
External Ports: 36870, 36872, 36871
CNAT_BADTEST ....... 0
CNAT_ISFULLCONE .... 0
CNAT_ISPAT ......... 1
CNAT_ISPATHOST ..... 1
CNAT_TRYPRESERVE ... 0
CNAT_PATINORDER .... 1
CNAT_BLOCKIP ....... 1
CNAT_BLOCKPORT ..... 1
CNAT_LOOPBACK ...... 0
Your routing device is not Full Cone (0) which is iChat's Preferred stated method of doing NAT in iChat 5
(our belief is that this is always been the case but only iChat 5's Connection Doctor tell us this).
This is not to say other methods don't work.
My own routing Modem says it is Port Restricted and does fine for iChat to iChat Video (it's a long time since I did an AIM/PC test).
The detail also suggests ports are blocked.
I ma also not sure of the significance of the ports listed at this stage.
However the log also does not seem to state it is mapping those to 16402 (and down to 16393 as it start top down).
133421.573835 [0]Creating a port mapping from on interface 0 from external port 57110 to local port 16402...
133421.574171 TPListen on port 16402
The @mac name seems to be on a Public IP where as the PC (AIM Name ?) seems to be behind a router when the info is first reported in the log.
Later the @mac name appears to be behind the same router.
This info about the LAN IPs seems to be Odd.
133432.154387 RTP using 172.16.3.227:16402 and 172.16.3.227:16402 as hints
133432.154411 Send to 172.16.3.180:8048 [INVITE sip:[email protected]:8048 SIP/2.0
Via: SIP/2.0/UDP 172.16.3.227:16402;branch=z9hG4bK168a0a5e20854b1c
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:8048>
From: "thekephart" <sip:[email protected]:16402>;tag=532265527
The @mac name is on IP xxx.xx.x.180 and the AIM name on 227
This is at odds with the @Mac Name in the start up info being on .227 even before the Video chat started.
133421.573477 Start listening on 172.16.3.227:16402(en1) sock 100
Then we have this
133429.700057 SIP IPPort: local=172.16.3.227:16402 src=63.161.132.29:36985 remote=63.161.132.27:8048 dst=63.161.132.27:8048
133429.700073 ER_AddFilter (3): Adding http://172.16.3.227->lip
133429.700080 ER_AddFilter (4): Adding 172-16-3-227->lip
133429.700086 ER_AddFilter (5): Adding http://63.161.132.27->rip
133429.700092 ER_AddFilter (6): Adding 63-161-132-27->rip
133429.700098 ER_AddFilter (7): Adding http://63.161.132.29->sip
133429.700103 ER_AddFilter (8): Adding 63-161-132-29->sip
133429.700206 TAInviteClientProc Thread start...
133429.700312 ( )( )( )( )( ) TP IS BINARY? (0)
133429.700326 RTP using 172.16.3.227:16402 and 63.161.132.29:36985 as hints
In here are two different Public IPs that are close together.
Are you using a multichannel set up ?
Is the Mac Wifi and Ethernet ?
Is the PC a Virtual one on the Mac ?
8:22 PM Friday; March 19, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

IChat login

I see iChat 3 now supports encrypted communication between users (if those users have .Mac). Is the iChat login also secure?
PB Al 15" Mac OS X (10.4.3)

IChat using the AIM service, which is not encrypted, so technically, it could be read by anyone.

IChat with MobileMe + AIM, SSL

I posted this some days ago in the MobileMe forum. I got no answer there, but I think this one should be the more appropriate place to ask about an iChat issue...
One of the potential benefit of setting up a MobileMe account in iChat is the fact that one can have an encrypted audio/video chat. Which is great.
However, there's a quirk, in my view. If I understand correctly, Apple creates and maintains an AIM account (on AOL servers) which has the same ID and the same password of the MobileMe account: which is not so great, but let's go on.
When setting up a new account (of the "MobileMe" kind), iChat, by default, connects with the AIM server without using ssl. This has nothing to do with the audio/video chat which could follow: this is just the initial authentication on the AIM server, and if I'm not mistaken the MobileMe password is sent in the clear. So it's all good and well to have ssl by default on www.me.com, but if you configure a MobileMe account in iChat you send out your password to potential eavesdroppers.
Is this the case?
Please note that I know that I can force ssl in the iChat options. What I'm pointing out is only that this is not the default behaviour.
Moreover, the first connection is made by iChat immediately after having entered the MobileMe username, without waiting for an explicit user command. Even if you do not enter your MobileMe password, iChat gets it from your keychain.
In other words, it seems to me that configuring a MobileMe iChat account implies sending out your MobileMe password at least once unencrypted, unless some convoluted tactics are adopted to stop iChat from connecting.
Is this the case?
I hope someone could confirm or (better) tell me I'm wrong here.

Hi,
On the issue that Apple Creates the AIM Accounts for you.
I have only found this in one Apple Document which suggested the same by the way it was worded.
Due to the fact if the Mobileme (Or @mac.com servers) go down iChat or any AIM app cannot check your password and sign you in the process if obviously different.
It seems that in all cases where AIM have agreements with Service like Apple or ISPs that their servers can check the names and passwords at the various servers involved
The other thing about this is that Apple allow passwords longer than 16 characters.
Using the first 16 characters only does not work which would be the simplest way the method you suggest would be used. (you have to change your password)
I have done a partial test of your other issues.
I Opened my iChat Preferences and created a New account and chose MobileMe
I did not enter a password and clicked Done.
At this point iChat displayed a Buddy List and immediately a Dialogue box asking for a Password.
Like the name I chose something fairly random. The Save to Keychain was not checked.
On Pressing OK the Dailogue box reappeared with the Save to Keychain ticked. I dismissed it. (I checked the Keychain later and it was not Saved there)
In Accounts I went to the Server Setting tab.
It was set up wihout SSL being On.
That needs to be reported here http://www.apple.com/feedback/ichat.html (And have further testing with a registered name)
In all my other accounts I have set up in iChat no Buddy List Window has appeared, saying it is Connecting, until I have pressed the Done Button.
I also know that if you delete the com.apple.ichat.AIM.plist and then restart iChat then your Accounts info is pulled back from the Keychain.
Deleting com.apple.ichat.plist and com.apple.ichat.AIM.plist will cause the Start Up Screens to reappear
This in the AIM options the "first" AIM valid Login details will be Prefilled.
From this I can see that if you have a MobileMe Name and it is use on your Mac somewhere then entering it in iChat may cause the password to be "collected" from the Keychain.
You can still decided to remove it before pressing Done.
The Account will not even try to log on until you have pressed the Done Button.
I tried also to set up an AIM name (I happened to have one not used on this computer)
This did not have the password in the Keychain for any other purposes so it was not pulled up.
The Buddy List did not appear until I pressed Done.
In fact the Add Account pane had closed and the Buddy list said Connecting before Little Snitch told me iChat was connecting to AIM (Again).
This means at no point did my fictitious @Me.com name Buddy List actually make contact with the AIM servers
I checked the Server Settings for this Account and this was a NON SSL login as well.
This surprised me as I seem to remember that the default was for SSL to be Enabled on it's introduction via Upgrade from iChat 3 (I am using iChat 4 on this computer).
You do seem to raise some valid concerns.
I have yet to test in iChat 5.
You should use the feedback site to raise these further.
10:33 PM Saturday; June 4, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.7)
 Mac OS X (10.6.7),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Can watching videos too often on Macbook Pro "wear down" the screen?

I watch most of my TV shows on my new macbook pro, and my mother just informed me that if you watch videos too often on a mac, that the screen can apparently wear down and die. Is this true? I'm not sure exactly what she meant by that or what could happen to my computer, but it doesn's sound exactly correct. Thanks!

Back in "the old days" when we all had green letters on black screens like in "War Games" (Matthew Broderick and Ally Sheedy) there were problems with "burn in" which was caused by the fact that only certain parts of the screen got used because the displays were text only. This is kind of like a prehistoric version of the problem with early plasma displays. Efforts to save CRT screens led to the creation of the ever-popular "Screen saver."
Most moms don't track display technology, so the notion remains that all video monitors are just shinier versions of last century's 15"/50 lb. wonders. Not so. Today's monitors will wear out, but most will be killed by their users long before that. Modern monitors CAN go off in color, loose brilliance, etc. over time but not specifically from movies. Notice I said movies, not video. The way we use computers these days, pretty much everything is video.
Keep calm and surf on.

Photoshop CS2 crashes too often!!!

I run Photoshop CS2 on my Mac Pro 2x2.66Ghz Intel Xeon, 5GB RAM, with Leopard OS X 10.5.2. I keep having problem with Photoshop quitting unexpectedly too often. It's not when doing certain types of task or anything, but just crashes randomly at any point. Sometimes I work fine for hours, and sometimes I can't even last 30min.
I do have CS3 installed, but don't really open it. I use CS2 for now.
I don't understand what might possibly be the problem.
Any ideas?
Thanks.

"I don't understand what might possibly be the problem."
The problem is you have a version of Photoshop supported under Leopard (CS3) and you are choosing to use one that isn't instead (CS2).
Try working with CS3. Besides the better stability, you should also notice a rather dramatic improvement in speed if you are working with files of any good size.

HT3964 Hello, my isight camer is not working properly, i was using photo booth and suddenly the image was black or too dark and also ichat and facetime are too dark as well, please helpme out i can not find any solution.

Hello, my isight camer is not working properly, i was using photo booth and suddenly the image was black or too dark and also ichat and facetime are too dark as well, please helpme out i can not find any solution.

read this and see if it helps: http://support.apple.com/kb/ht2090

Ichat/login to AIM too often

Similar Messages

Maybe you are looking for