If iChat still does not work and you use DSL, try this.
Hi All-
I have been working with iChat for a few years now and went to this forum for help solving issues that were intermittent and involved error -8, -7 etc when trying to chat with various individuals. I was never able to completely resolve my issues on the basis of the common responses. I spent a LOT of time screwing with this and I believe I have established that a VERY common problem is related to a conflict between the DSL Modem acting as a DHCP router (nearly ALL OF THEM DO, even if it has ONLY 1 plug in the back!) and the wireless or wired router (also acting as a DHCP router) in your home. I have COMPLETELY solved serious and ongoing iChat issues for myself and three friends located across the country, using 3 different DSL providers, three different DSL modems and 2 different wireless routers. This appears to be a universal solution. The problem is in a conflict with NAT protocols between the DSL modem and the Router and the fact that they both are acting as DHCP servers and screwing up the traffic for iChat. If you connect to the internet using a set up like this.
Phone cable comes into a DSL modem. Internet cable leaves DSL modem and plugs into a Wireless or wired ROUTER, your computer connects to ROUTER. And if you have ongoing and serious iCHAT issues with inconsistent error messages, you need to try the following. Doing this completely solved ALL issues with the following set ups.
Linksys wireless router with 2-wire DSL modem
Net Gear wireless router with Paradyne DSL modem
NetGear wireless router with unknown brand DSL modem
In EACH instance, these set ups would have serious connectivity issues when trying to iChat. We would get the usual did not respond, cancelled invitation, error -8 etc etc errors. As SOON as we set up our DSL modems to act as a UNMANAGED bridge the errors were gone and 100% of the time we are able to chat.
If you want to FIX iCHat you need to switch your DSL modem into Bridge Mode, then you need to configure your ROUTER to log into the DSL provider via PPOe or whatever you use. This can get a little complicated depending on which modem you have and which router you have.
It is important that the DSL modem does not manage internet traffic in ANY WAY. The older modems can be a PAIN (such as the paradyne). But, once your modem is acting as a true bridge, i.e. it is not intercepting any net traffic, its simply a wire connecting your router to the outside phone system you will need to configure your router to log into your DSL account. This should be easy, just copy the settings your DSL provider had set up in the modem. Now try iChat and let me know if this fixed it . It worked for me and so far three people I spent a lot of time working with and who had the same problems so many people post about here. I would say this should be the FIRST thing you should be advised to check if you use DSL.
YOU SHOULD BE AWARE THAT THIS CAN BE COMPLICATED and that for some older DSL modems, once you tell them to act as a bridge, you now need to instruct them to stop managing traffic. When they get this last command they will DISCONNECT from your computer and will no longer be visible or log-onable (whatever). I.e they will cease to exist even if plugged directly into your computer, you will not be able to log onto the 192.168.1.1 or other typical address. The ONLY way to get them back, if you get lost or something else, is to hold down the factory reset button. If you are using a newer DSL modem its likely as simple as hitting the "act as bridge" button or similar spot. DO NOT SCREW WITH YOUR DSL MODEM UNLESS YOU ARE CONFIDENT YOU CAN RESTORE YOUR CONNECTION. Once its a bridge your will LOSE INTERNET CONNECTIVITY until you configure your router to log into your DSL provider. I dont want to scare people but things can go badly and you will be without any internet service if your not careful, and in my experience your DSL provider is not going to know much about bridge settings, they dont want to deal with this, but it MATTERS A LOT.
Its worth it, if you tried everything else try this!
I have been working with iChat for a few years now and went to this forum for help solving issues that were intermittent and involved error -8, -7 etc when trying to chat with various individuals. I was never able to completely resolve my issues on the basis of the common responses. I spent a LOT of time screwing with this and I believe I have established that a VERY common problem is related to a conflict between the DSL Modem acting as a DHCP router (nearly ALL OF THEM DO, even if it has ONLY 1 plug in the back!) and the wireless or wired router (also acting as a DHCP router) in your home. I have COMPLETELY solved serious and ongoing iChat issues for myself and three friends located across the country, using 3 different DSL providers, three different DSL modems and 2 different wireless routers. This appears to be a universal solution. The problem is in a conflict with NAT protocols between the DSL modem and the Router and the fact that they both are acting as DHCP servers and screwing up the traffic for iChat. If you connect to the internet using a set up like this.
Phone cable comes into a DSL modem. Internet cable leaves DSL modem and plugs into a Wireless or wired ROUTER, your computer connects to ROUTER. And if you have ongoing and serious iCHAT issues with inconsistent error messages, you need to try the following. Doing this completely solved ALL issues with the following set ups.
Linksys wireless router with 2-wire DSL modem
Net Gear wireless router with Paradyne DSL modem
NetGear wireless router with unknown brand DSL modem
In EACH instance, these set ups would have serious connectivity issues when trying to iChat. We would get the usual did not respond, cancelled invitation, error -8 etc etc errors. As SOON as we set up our DSL modems to act as a UNMANAGED bridge the errors were gone and 100% of the time we are able to chat.
If you want to FIX iCHat you need to switch your DSL modem into Bridge Mode, then you need to configure your ROUTER to log into the DSL provider via PPOe or whatever you use. This can get a little complicated depending on which modem you have and which router you have.
It is important that the DSL modem does not manage internet traffic in ANY WAY. The older modems can be a PAIN (such as the paradyne). But, once your modem is acting as a true bridge, i.e. it is not intercepting any net traffic, its simply a wire connecting your router to the outside phone system you will need to configure your router to log into your DSL account. This should be easy, just copy the settings your DSL provider had set up in the modem. Now try iChat and let me know if this fixed it . It worked for me and so far three people I spent a lot of time working with and who had the same problems so many people post about here. I would say this should be the FIRST thing you should be advised to check if you use DSL.
YOU SHOULD BE AWARE THAT THIS CAN BE COMPLICATED and that for some older DSL modems, once you tell them to act as a bridge, you now need to instruct them to stop managing traffic. When they get this last command they will DISCONNECT from your computer and will no longer be visible or log-onable (whatever). I.e they will cease to exist even if plugged directly into your computer, you will not be able to log onto the 192.168.1.1 or other typical address. The ONLY way to get them back, if you get lost or something else, is to hold down the factory reset button. If you are using a newer DSL modem its likely as simple as hitting the "act as bridge" button or similar spot. DO NOT SCREW WITH YOUR DSL MODEM UNLESS YOU ARE CONFIDENT YOU CAN RESTORE YOUR CONNECTION. Once its a bridge your will LOSE INTERNET CONNECTIVITY until you configure your router to log into your DSL provider. I dont want to scare people but things can go badly and you will be without any internet service if your not careful, and in my experience your DSL provider is not going to know much about bridge settings, they dont want to deal with this, but it MATTERS A LOT.
Its worth it, if you tried everything else try this!
MacBook Pro/ iMac 24, Mac OS X (10.5.1)
