3 Replies Latest reply: Apr 3, 2007 1:01 PM by Ralph Johns (UK)
Yvon Couture Level 1 Level 1 (65 points)
Hello to all who have experience some kind of "communication error" that renders videoconferences inoperative.

I have found a possible cause and a solution. At least to my problem. I had videoconferences on my Mac Pro without any problem and then all of a sudden, it seemed, it wouldn't work and I got the above mentionned message.

In fact here is what happened:

I originnaly used my mac with the ethernet port. Everything was fine. Then I went to a wireless connection with the use of an "Airport extreme" base station(the one with airtunes)plugged to my router and, still, everything was fine.

However, at one point I repluged the wire and kinda used both. That 's where the error originated.

Indeed, in that kind of setup, you have to make sure that "Network port configuration" will show "Airport" as the first choice. In my setup, if it's set to "Built-in ethernet 1" and then "Airport", even though both are plugged, I will get the error message.

I hope this is clear enough to help anyone with that problem.

Cheers!

Mac Pro   Mac OS X (10.4.9)   2.66
  • Ralph Johns (UK) Level 9 Level 9 (69,525 points)
    Hi,

    Yes. If you are coonnected to your routing device by two methods you will get two IPs from that router.
    In this case one for Ethernet and one for wireless.

    iChat and some other apps can not distinguish that there are two IPs and give conflicting info to the SNATMAP server as to what the computer's IP is and problems will arise.

    It sounds like in this case that the wireless connection attempts to take precedence even when lower in the list.

    This info in the original post should be useful.



    10:36 AM Monday; April 2, 2007
  • Yvon Couture Level 1 Level 1 (65 points)
    Thanks for the explanation and technical detail. I was baffled by this. Because the router was setup properly and my other computer, a Dual MDD G4, could videoconference without any problem. At one point I even thought bootcamp might have been the culprit.

    I had just purchased the computer and had to install so many things on it that I could hardly pinpoint the cause of this problem.

    Everything runs smoothly now.
  • Ralph Johns (UK) Level 9 Level 9 (69,525 points)
    Hi Yvon,

    I think we all dfo that at times.

    "It worked here so I'll just use it there" Often forgetting that the OS may be slightly different levels or not written for Intels yet.



    9:00 PM Tuesday; April 3, 2007