Adium

Ticket #8449 (closed defect)

Opened 1 year ago

Last modified 1 year ago

Adium does not connect to ICQ

Reported by: nwinter Assigned to: nobody
Priority: normal Milestone: Needs feedback from users
Component: ICQ Version: 1.1.4
Severity: normal Keywords:
Cc: Patch: None
Pending: 0

Description

Error message: "Could not connect to authentication server: Error resolving login.oscar.aol.com: nodename nor servname provided, or not known.

I am able to ping, dig, traceroute or whatever "login.oscar.aol.com". iChat is still able to connect to icq and Adium is still able to connect other services. It usually occurs after I wake the mac from sleep. I wonder if it only occured since Leoard.

One workaround i found is to un/plug the network cord from the switch. After that Adium usually is able to connect.

I wish i where able to serve any more details.

Attachments

2007-11-26.log (43.8 kB) - added by nwinter on 11/26/2007 03:11:37 PM.
requested debug log, replaced icq # with (myICQ#)
2007-11-26-2.log (96.7 kB) - added by nwinter on 11/26/2007 03:21:43 PM.
this time disconnected network cord while system sleep

Change History

11/25/2007 06:10:02 PM changed by jas8522

  • pending set to 1.
  • milestone set to Needs feedback from users.

See ReportingBugs for how to get debug logging from this occurrence. If it has only occurred since Leopard, this might be related to the DNS bug tickets and #8053

11/26/2007 03:11:37 PM changed by nwinter

  • attachment 2007-11-26.log added.

requested debug log, replaced icq # with (myICQ#)

11/26/2007 03:21:43 PM changed by nwinter

  • attachment 2007-11-26-2.log added.

this time disconnected network cord while system sleep

12/10/2007 12:00:02 AM changed by trac-robot

  • status changed from new to closed.
  • pending deleted.

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

01/04/2008 08:15:59 AM changed by nwinter

Ticket could be closed. Seems to be an OS X problem

$ dscacheutil -flushcache

solves this problem.