Synchronisation problem with 3500c (usb)

Hello,
I'm using Win XP Home 2002 SP3 and Nokia PC Suite 7.0.8.2 to (try to) synchronise my 3500c with Microsoft Outlook (usb) but it doesn't work. It doesn't give a reason either... just 'could not synchronise'. I used to synchronise my 6230 without any problem the last couple of years. (I did reinstall PC Suite since then so the 6230 is not in the phone list anymore).
Even if I can't synchronise, I have a connection because I CAN do SMS, MMS, and file transfer using PC Suite...
I updated my phone software to v7.0 (19-08-08) but this doesn't solve my problem.

Hello again,
See this:
KB16471 BlackBerry Desktop Software prompts that an Internet connection is required to configure synchronization
Hopefully it contains something useful.
Good luck!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4   Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA   Display/Scan Bar Code

Similar Messages

  • Problems with the USB Ports

    Hi there,
    I writing this because I'm having some really big problems with my USB ports.
    A few days ago I plugged in an USB-Hub that was quite cheap. Suddenly a window popped up saying that a USB device was deactivated because it "needed" to much power. Since this happening, two of those windows keep popping up everytime I boot the MacBook. I called Apple and got some help: I had to delete some .plist files and clear some caches. The man who helped was able to find the error and deactivate the notification, he also told me to make a PRAM- and a SMC-reset. The man said that it's just a software problem and that I have to reinstall the system if we don't find a solution. So, one day later I reinstalled the system (Lion) and not only didn't it help, the two notification windows were popping up again...everytime I booted the Mac. So I decided to formate the whole hard drive and install Snow Leopard -> still the problem with the USB ports. After that I installed Lion  -> still the problem with the USB ports. I even tried to extract the .kext files that are important for the USB functionality from an earlier Combo Update, but it didn't help either. The point is, that the Mac doesn't recognize my external hard drive or any of my iDevices. Sometimes it recognizes USB sticks, but only after 20 seconds. The data transfer on both USB ports is also very slow. If I'm lucky and Mac recognizes one of my USB sticks, it takes like an hour for 1GB to be transfered on the USB stick or from the USB sticks to the Mac.
    I really don't know what to do and need help, especially because my backup data is on my external hard drive which I can't access because of this problem.
    I really hope that someone can help me, I'm very thankful for every answer that could help me!
    PS: Sorry for my bad English, I hope that everyone understands what I mean, please tell me if you don't get what I'm trying to explain in the text above.
    Sincerely,
    iLoud
    [UPDATE] I downloaded "USB Prober" and copied the Output file, maybe it helps:
    Timestamp Lvl            Message
        0.698 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7316), outstandingIO(0), _interruptReadPending(false) - rearming read
        0.698 [3]          AppleUSBUHCI[0x4f97000]::UIMCreateInterruptTransfer - root hub interrupt transfer - clearing unneeded memDesc (0x5073080) from dmaCommand (0x506a100)
        0.735 [3]          AppleUSBUHCI[0x4f97000]::UIMAbortEndpoint - endpoint 1:1,1
        0.735 [3]          AppleUSBUHCI[0x4f97000]::RHAbortEndpoint - Interrupt pipe -  noting status change
        0.735 [3]          AppleUSBHub[0x5076c00]::InterruptReadHandler error kIOReturnAborted (expected)
        0.739 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - Host controller resume detected - calling EnsureUsability
        0.739 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - deferring further processing until we are running again
        0.761 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7320), outstandingIO(0), _interruptReadPending(false) - rearming read
        0.761 [3]          AppleUSBUHCI[0x4f97000]::UIMCreateInterruptTransfer - root hub interrupt transfer - clearing unneeded memDesc (0x5073080) from dmaCommand (0x506a100)
        0.798 [3]          AppleUSBUHCI[0x4f97000]::UIMAbortEndpoint - endpoint 1:1,1
        0.798 [3]          AppleUSBUHCI[0x4f97000]::RHAbortEndpoint - Interrupt pipe -  noting status change
        0.798 [3]          AppleUSBHub[0x5076c00]::InterruptReadHandler error kIOReturnAborted (expected)
        0.801 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - Host controller resume detected - calling EnsureUsability
        0.801 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - deferring further processing until we are running again
        0.823 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7324), outstandingIO(0), _interruptReadPending(false) - rearming read
        0.823 [3]          AppleUSBUHCI[0x4f97000]::UIMCreateInterruptTransfer - root hub interrupt transfer - clearing unneeded memDesc (0x5073080) from dmaCommand (0x506a100)
        0.860 [3]          AppleUSBUHCI[0x4f97000]::UIMAbortEndpoint - endpoint 1:1,1
        0.860 [3]          AppleUSBUHCI[0x4f97000]::RHAbortEndpoint - Interrupt pipe -  noting status change
        0.860 [3]          AppleUSBHub[0x5076c00]::InterruptReadHandler error kIOReturnAborted (expected)
        0.863 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - Host controller resume detected - calling EnsureUsability
        0.863 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - deferring further processing until we are running again
        0.885 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7328), outstandingIO(0), _interruptReadPending(false) - rearming read
        0.885 [3]          AppleUSBUHCI[0x4f97000]::UIMCreateInterruptTransfer - root hub interrupt transfer - clearing unneeded memDesc (0x5073080) from dmaCommand (0x506a100)
        0.922 [3]          AppleUSBUHCI[0x4f97000]::UIMAbortEndpoint - endpoint 1:1,1
        0.922 [3]          AppleUSBUHCI[0x4f97000]::RHAbortEndpoint - Interrupt pipe -  noting status change
        0.922 [3]          AppleUSBHub[0x5076c00]::InterruptReadHandler error kIOReturnAborted (expected)
        0.926 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - Host controller resume detected - calling EnsureUsability
        0.926 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - deferring further processing until we are running again
        0.947 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7332), outstandingIO(0), _interruptReadPending(false) - rearming read
        0.947 [3]          AppleUSBUHCI[0x4f97000]::UIMCreateInterruptTransfer - root hub interrupt transfer - clearing unneeded memDesc (0x5073080) from dmaCommand (0x506a100)
        0.984 [3]          AppleUSBUHCI[0x4f97000]::UIMAbortEndpoint - endpoint 1:1,1
        0.984 [3]          AppleUSBUHCI[0x4f97000]::RHAbortEndpoint - Interrupt pipe -  noting status change
        0.984 [3]          AppleUSBHub[0x5076c00]::InterruptReadHandler error kIOReturnAborted (expected)
        0.987 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - Host controller resume detected - calling EnsureUsability
        0.987 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - deferring further processing until we are running again
        1.009 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7336), outstandingIO(0), _interruptReadPending(false) - rearming read
        1.009 [3]          AppleUSBUHCI[0x4f97000]::UIMCreateInterruptTransfer - root hub interrupt transfer - clearing unneeded memDesc (0x5073080) from dmaCommand (0x506a100)
        1.045 [3]          AppleUSBUHCI[0x4f97000]::UIMAbortEndpoint - endpoint 1:1,1
        1.045 [3]          AppleUSBUHCI[0x4f97000]::RHAbortEndpoint - Interrupt pipe -  noting status change
        1.045 [3]          AppleUSBHub[0x5076c00]::InterruptReadHandler error kIOReturnAborted (expected)
        1.049 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - Host controller resume detected - calling EnsureUsability
        1.049 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - deferring further processing until we are running again
        1.071 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7340), outstandingIO(0), _interruptReadPending(false) - rearming read

    Oh, sorry, I meant "I'm writing this...".

  • Problem with SB1240 USB sound card

    I'm pulling hair here! I've just bought a SB240. Windows (XP Pro, SP3) detected it and I can select it fine for listening. But when I open Sound and Audio Device Properties and select Sound Recording/Volume, I see the Capture panel with the three inputs, but all the controls are greyed out and immovable. I also use the application "Total Recorder" by High Criteria, in which I can select the SB240 device but the only input line it sees is SPDIF Interface.
    I'm stumped. Can anyone help?
    John?

    &Re: Problem with SB240 USB sound card
    Thank you. I did a complete uninstall, including the device itself (from Device Manager) as well as all drivers and any SB related software. As recommended by Creative, I had previously installed the driver software from the supplied CD and that seems to have been the problem.
    I let Windows re-detect the SB, but? got a "problem ... device may not work correctly.." during the detection, so I was not hopeful (this had not happened the first time I installed the device).
    Nevertheless it now does work fully and is properly configured in "Total Recorder" too.
    So I would suggest not using the supplied drivers and software - at least not in WinXP. But it's not very confidence inspiring.
    John

  • Problems with wireless usb adapter on MSI K8NGM-V

    Hi!
    I have a 3Com (3crusb20075) wireless usb adapter, and a MSI K8NGM-V Mainboard. Very often the usb disconnects from the network and i have to reinsert it to work again. A friend of mine have the exact same adapter and that one fails too. He uses mine without problems. I therefore belive that this is a problem with the usb ports on my mainboard. Have anyone heard of anything like this? I wanted to try to update my bios but i don't have a floppy so msi live update wouldnt let me, and i could find the bios files on the msi webpage so i cant burn them on a bootable cd. Help please
    (I trying turning of power save mode on the usb adapter, without any luck. Tested it in linux. Same result)
    Alex

    The ability to access the network, but not the Internet, typically indicates that the computer is not able to either find or negotiate with the DNS servers. The proper DNS servers would be provided by your ISP using DHCP. In turn, the AirPort would use DHCP to provide these to both the wired & wireless computers connected to it.
    Please try the following:
    For each PC that is unable to access the Internet, temporarily include the following OpenDNS servers:
    o Primary: 208.67.222.222
    o Secondary: 208.67.220.220
    You would enter these in the network TCP/IP settings for the respective PC's wireless network adapters. You may need to restart the computer in order for these DNS settings to "stick." After restarting, can you access the Internet with either or both of them?

  • Problem with detecting USB devices.. something abt ehci-hcd??

    Hi All,
    I have a DELL E6410 laptop. I have a problem with connecting USB devices.
    Whenever a power event (such as connecting/disconnecting of AC adaptor) happens, my laptop stops detecting any USB devices and any changes that happen on the USB ports. That is, say an external mouse is connected to the laptop, the mouse stops functioning, and if I connect a mouse/USB_stick or any such thing to the computer, the device is not detected.
    dmesg output show that any connecting/disconnecting events are not detected by the computer. lsusb output too shows the same thing.
    To solve the problem, I need to rmmod the module ehci-hcd and modprobe it back. That is, I have to run the commands rmmod ehci-hcd followed by modprobe ehci-hcd. Then, this problem goes away until the next power event happens.
    This event does not happen all the time, but it happens very regularly.
    Here are the kernel and laptop specs..
    uname -a
    Linux myhost 3.0-ARCH #1 SMP PREEMPT Tue Aug 30 08:53:25 CEST 2011 x86_64 Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz GenuineIntel GNU/Linux
    Kindly help me on this issue.
    Thanks

    This is the output of kernel.log when I unplug my AC adaptor with the external USB mouse connected.
    Sep 12 11:18:33 localh ost kernel: [ 591.015557] EXT4-fs (sda6): re-mounted. Opts: commit=600
    Sep 12 11:18:37 localhost kernel: [ 595.478866] ehci_hcd 0000:00:1a.0: PCI INT A disabled
    Sep 12 11:18:37 localhost kernel: [ 595.478919] ehci_hcd 0000:00:1a.0: PME# enabled
    Sep 12 11:18:37 localhost kernel: [ 595.498827] ehci_hcd 0000:00:1d.0: PCI INT A disabled
    Sep 12 11:18:37 localhost kernel: [ 595.498877] ehci_hcd 0000:00:1d.0: PME# enabled
    After this the the mouse goes dead (the light on the mouse also goes off).
    If I disconnect the mouse at this stage, there is no change in kernel.log. If I the mouse back too, there is no change in kernel.log.
    Now, when I turn the AC adaptor on, this is the output on kernel.log
    Sep 12 11:22:16 localhost kernel: [ 813.917712] EXT4-fs (sda6): re-mounted. Opts: commit=0
    Sep 12 11:22:16 localhost kernel: [ 813.977405] NMI watchdog enabled, takes one hw-pmu counter.
    Sep 12 11:22:16 localhost kernel: [ 813.977453] NMI watchdog enabled, takes one hw-pmu counter.
    Sep 12 11:22:16 localhost kernel: [ 813.980838] NMI watchdog enabled, takes one hw-pmu counter.
    Sep 12 11:22:16 localhost kernel: [ 813.980874] NMI watchdog enabled, takes one hw-pmu counter.
    Sep 12 11:22:16 localhost kernel: [ 814.075104] ehci_hcd 0000:00:1a.0: BAR 0: set to [mem 0xd6970000-0xd69703ff] (PCI address [0xd6970000-0xd69703ff])
    Sep 12 11:22:16 localhost kernel: [ 814.075148] ehci_hcd 0000:00:1a.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
    Sep 12 11:22:16 localhost kernel: [ 814.075189] ehci_hcd 0000:00:1a.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900002)
    Sep 12 11:22:16 localhost kernel: [ 814.075256] ehci_hcd 0000:00:1a.0: PME# disabled
    Sep 12 11:22:16 localhost kernel: [ 814.075279] ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    Sep 12 11:22:16 localhost kernel: [ 814.075295] ehci_hcd 0000:00:1a.0: setting latency timer to 64
    Sep 12 11:22:17 localhost kernel: [ 814.228224] ehci_hcd 0000:00:1d.0: BAR 0: set to [mem 0xd6950000-0xd69503ff] (PCI address [0xd6950000-0xd69503ff])
    Sep 12 11:22:17 localhost kernel: [ 814.228246] ehci_hcd 0000:00:1d.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
    Sep 12 11:22:17 localhost kernel: [ 814.228273] ehci_hcd 0000:00:1d.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900002)
    Sep 12 11:22:17 localhost kernel: [ 814.228310] ehci_hcd 0000:00:1d.0: PME# disabled
    Sep 12 11:22:17 localhost kernel: [ 814.228324] ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    Sep 12 11:22:17 localhost kernel: [ 814.228333] ehci_hcd 0000:00:1d.0: setting latency timer to 64
    Sep 12 11:22:17 localhost kernel: [ 814.614404] usb 2-1.1: reset low speed USB device number 3 using ehci_hcd
    At this point, the mouse comes back to life (its light begins to glow) and I can move the mouse pointer on the screen.
    The output of the grep command that rwd gave is too big (16000 lines) to be pasted here..
    Thanks,

  • Synchronisation problem with LifeBlog

    Since about 2 weeks now, I cannot synchronise the stuff from my 6630 Lifeblog onto the PC Lifeblog. I keep getting the following message:
    "Lifeblog encounters problems transferring items. Please check the connection and try again. If the problem persists, restart Lifeblog and/or the PC and try again.
    Possible reasons: An item that you are trying to transfer may be opened in an application on your phone or PC, the multimedia card (MMC) on your phone or your PC hard disk may be full.
    For more information see Lifeblog Online Help, Troubleshooting, Transfer Problems."
    In the course of this problem I had done the followings:
    * Restart the computer and try again
    * Restart the 6630 and try again
    * Restart both the PC and the 6630 and try again
    * Check both the MMC (354 MB free) and my PC hard disk (16 GB free), restart both and try again
    * Uninstall Nokia PC-Suite and reinstall it and try again
    * Went to see the "Troubleshooting" which wasn't any help at all
    * Updated the firmware and try again
    * Re-installing PC-Suite (newest version), Lifeblog (newest version) on both phone and PC and try again
    All to no avail.
    Any help?
    Information:
    Phone:
    Nokia 6630
    Firmware version 6.03.08
    Operating system:
    Microsoft Windows XP
    Service Pack 2
    Nokia PC Suite:
    Version 6.81.13.0
    Language: English
    Connectivity Cable Drivers:
    Version 6.81.1.2

    23-Aug-2006
    10:01 AM
    elemmaciltur wrote:
    Since about 2 weeks now, I cannot synchronise the stuff from my 6630 Lifeblog onto the PC Lifeblog. I keep getting the following message:
    "Lifeblog encounters problems transferring items. Please check the connection and try again. If the problem persists, restart Lifeblog and/or the PC and try again.
    Possible reasons: An item that you are trying to transfer may be opened in an application on your phone or PC, the multimedia card (MMC) on your phone or your PC hard disk may be full.
    For more information see Lifeblog Online Help, Troubleshooting, Transfer Problems."
    In the course of this problem I had done the followings:
    * Restart the computer and try again
    * Restart the 6630 and try again
    * Restart both the PC and the 6630 and try again
    * Check both the MMC (354 MB free) and my PC hard disk (16 GB free), restart both and try again
    * Uninstall Nokia PC-Suite and reinstall it and try again
    * Went to see the "Troubleshooting" which wasn't any help at all
    * Updated the firmware and try again
    * Re-installing PC-Suite (newest version), Lifeblog (newest version) on both phone and PC and try again
    All to no avail.
    Any help?
    Information:
    Phone:
    Nokia 6630
    Firmware version 6.03.08
    Operating system:
    Microsoft Windows XP
    Service Pack 2
    Nokia PC Suite:
    Version 6.81.13.0
    Language: English
    Connectivity Cable Drivers:
    Version 6.81.1.2
    I've occasionally had the same error message you experienced above and have been able to solve it although I have not been able to localise whereabouts the problem is occurring.
    As an aside, I don't think you mention what version of LifeBlog you are using but FYI (For Your Information) v2.1.131 is out.
    I've composed a list of things you should look at to find out why this is happening - these questions are only meant to find out where the problem lies - not apportion blame so please don't take them the wrong way !
    Things you need to look at to solve the problem or eliminate the potential cause of the problem :
    1) Upgrade to the latest version of LifeBlog if you aren't already using it - it can be found here - http://www.nokia.com/lifeblog - it may be possible that the problem you are having is a known issue which is solved in the latest release. At the very least I would recommend doing a complete uninstall of the old version and then rebooting, and installing the new version to ensure that you start from a clean configuration.
    2) Has LifeBlog ever worked ? If so, then when did it stop working ? What did you do previous to when it stopped working ? Did you install a new PC/mobile application ?
    3) Are you able to use the full capabilities of PC Suite successfully ? Can you backup the phone, synchronise data with Outlook or whatever compatible PIM you use ? The fact that you have done a software update etc. indicates you can connect successfully to the phone, but I thought I would put it here for completeness !
    4) Have you tried installing the LifeBlog software which is designed to run on the mobile phone - not the PC ? (If not - please do this - it will act as an useful potential problem indicator further below)
    5) Are you running any minimized software on your PC or phone whilst trying to do the PC Suite/LifeBlog update ? Disable any anti virus software JUST IN CASE FOR THIS TESTING ONLY. I once had an issue where I connected a camcorder via Firewire and I then couldn't surf the internet - this turned out to be a problem with the anti virus application I was using at the time - it only recognised one valid TCP/IP interface at a time - when the FireWire connection became active, it shut the interface to my network card down ! Also make sure any firewall software is temporarily disabled just in case as well.
    You sound technically proficient, but again I thought I'd put this in for completeness.
    The thing that should happen if you have PC Suite living in your system tray (next to your clock) and you plug you phone in is as follows. You should get a little bublle pop up saying "6680 connected via USB" or something similar - the white cross in a red background should change to a green shape - can't remember what the shape is off the top of my head.
    Once that happens it pretty much means that your phone and PC are talking correctly. At this point PC Suite (e.g. backup) should work - if it doesn't then you will need to resolve this issue before LifeBlog will work.
    Presuming PC Suite works, and the problem is indeed localised to LifeBlog, the next stage of diagnostics would be to load LifeBlog for your mobile. When you load the LifeBlog software on your mobile, you should see a chronological list of pictures you have taken and text messages you have sent - check this is the case and that it is up to date - send yourself a text message and check if you can see it being sent and received in LifeBlog - if not, then click the options button and select Update Timeline (or something similar) and try again - does it appear now ? If it doesn't then it indicates LifeBlog isn't working correctly - I would recommend that you uninstall LifeBlog on your mobile and power cycle your mobile and reinstall it. This is the particular issue I was having - when I got LifeBlog on my mobile working - it worked on my PC - sometimes I find if they get out of sync they're not particularly happy (even though they should be independent of each other).
    I'm pretty sure from the log files, that LifeBlog uses a database of sometime to collate the LifeBlog information and sometimes it can get a bit confused - the "Update TimeLine" option should help solve this.
    Hope this helps - let me know how you get on !
    Regards,
    Edward

  • How do I investigate and solve Pages, Notes, Mail intermittent 'offline' and failure to synchronise problems with Mountain Lion after waking from Sleep

    When I wake up my iMac after sleep, i get a variety of intermittent - but mostly FREQUENT and FRUSTRATING problems including:
    Notes app is offline - as stated by a message in the window bar. If I close Notes and reopen, the app appears to be online. However, Notes does NOT update with items I know are on my iPad or in the web iCloud. Furthermore, if I create a new note on my iMac, the new Note does not upload to iCloud. This is IRRITATING!
    Pages and Numbers - similar situation. I can edit a Pages or Numbers document on my iMac (stored on the iCloud). But then the Pages doc doesn't ALWAYS get uploaded to the iCloud. Then I end up with conflicted versions of the file in the cloud, my iPad, and the two iMacs I use. Then I get CONFUSED and FRUSTRATED. For example, consider these steps:
    Open Pages on my iMac, edit an iCloud file, then save and close file
    Pages/File/Open/iCloud - I note in the iCloud file list the edited file has a little 'cloud' icon against its name. From experience this warns me of TROUBLE - namely that the file has NOT yet been uploaded to the iCloud. However, I just checked the new Beta iCloud on the web, and to my surprise, the file edited on my iMac is apparently in the icloud. But now, I edit the iCloud version, and the changes DO NOT appear on my iMac pages version. OK I realise its in Beta version...
    So now, I open my iPad, open Pages. I note the iCloud version of my edited document updates to my iPad, as indicated by a blue download line. 'It just works' as Steve Jobs claimed at Apple Developers Conference a couple of years back. Again, the edited version form my iPad is now 'up in the cloud' correctly....
    Oh - and now mysteriously the Pages version on my Imac has become synchronised with my iPad/iCloud version! Luck ... but that's about all I can say. It doesn't always happen. I'm LUCKY today.
    Meanwhile, the Note I created on my iMac (Item 1 above) has still not yet appeared on my iPad or iCloud... even though I HOPE it would be given that Pages on my iMac, iPad and iCloud are chatting nicely now! The Note says it's in my iCloud - but  NOT. Similarly, notes updated or added on my iPad, which appear in iCloud, are NOT on my iMac.
    Mail - last but NOT LEAST! and MOST INFURIATING!!! My Gmail, Vodafone NZ and Orcon accounts (in Mail) are all active and receiving after the night's sleep. However, my iCloud mail account has the dreaded offline.
    The message on Mail is "There may be a problem with the mail server or network. Verify the settings for account “ICloud - [email protected]” or try again. The server returned the error: The server “p03-imap.mail.me.com” cannot be contacted on port 993." Despite the message, mail was received this morning at 8:59 am ... some time before I woke-up my computer (a late start this morning).
    If I sent an email FROM my .me iCloud account TO my Vodafone account, the message whooshes away, it's in my SENT box. But it doesn't get delivered to my Vodafone account on my iMac Mail, or anywhere else, Despite the message being listed in my 'Sent' mailbox!!!
    In contrast, a message sent from my Gmail account to my Vodafone account (in Mail) gets sent and received almost instantly on  my iMac and iPad.
    All of the above mishaps are extremely frustrating, as I rush off from working on my iMac at home, get to my iMac at work and find documents I have been updating on my home iMac not available correctly on my work iMac ... or even my iPad. I expect these things from Apple to 'just work'. Furthermore, emails I THINK I have sent (as indicated by them appearing in the Sent folder on my home iMac) ... have not actually been despatched.
    Frankly, I can no longer rely or recommend the Apple iCloud stuff, so I am converting more and more to relying on DropBox and Google.
    These problems only became apparent since I updated to one of the Mountain Lion versions... I can't say when.
    Oh - if I shutdown and restart the computer my Mail works OK. Guess what, I don't want to do that each time I want to use Mail!
    Technicals:
    My iMac is connected by Ethernet cable to my Apple TimeCapsule. The TimeCapsule is connected by Ethernet cable to my Orcon Genius Modem.
    Obviously, my internet connection is A-OK, as I am able to use Firefox to make this posting!
    Mountain Lion 10.8.4
    iMac 27 inch, mid 2010, Intel Core i5 16 Gb

    I've returned to my sleeping iMac after a few days away. Tis time, ALL MAIL accoiunts are offline. I will follow you next set of instructions. In the meantime, here is the DETAIL from MAIL CONNECTION DOCTOR:
    LevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    19.10827 STATUS [Gmail]/Trash (UIDNEXT UNSEEN HIGHESTMODSEQ)
    WROTE Sep 30 08:35:11.179 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    20.10827 STATUS INBOX (UIDNEXT UNSEEN HIGHESTMODSEQ)
    WROTE Sep 30 08:35:11.202 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    21.10827 STATUS "Sent Messages" (UIDNEXT UNSEEN HIGHESTMODSEQ)
    WROTE Sep 30 08:35:11.226 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    22.10827 STATUS "Deleted Messages" (UIDNEXT UNSEEN HIGHESTMODSEQ)
    READ Sep 30 08:35:11.254 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    * STATUS "[Gmail]/All Mail" (HIGHESTMODSEQ 561701 UIDNEXT 1666 UNSEEN 105)
    13.10827 OK Success
    READ Sep 30 08:35:11.494 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    * STATUS "[Gmail]/Drafts" (HIGHESTMODSEQ 561701 UIDNEXT 1 UNSEEN 0)
    14.10827 OK Success
    READ Sep 30 08:35:11.514 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    * STATUS "[Gmail]/Important" (HIGHESTMODSEQ 561701 UIDNEXT 731 UNSEEN 8)
    15.10827 OK Success
    * STATUS "[Gmail]/Sent Mail" (HIGHESTMODSEQ 561701 UIDNEXT 532 UNSEEN 2)
    16.10827 OK Success
    * STATUS "[Gmail]/Spam" (HIGHESTMODSEQ 561701 UIDNEXT 16 UNSEEN 2)
    17.10827 OK Success
    * STATUS "[Gmail]/Starred" (HIGHESTMODSEQ 561701 UIDNEXT 19 UNSEEN 0)
    18.10827 OK Success
    * STATUS "[Gmail]/Trash" (HIGHESTMODSEQ 561701 UIDNEXT 546 UNSEEN 0)
    19.10827 OK Success
    * STATUS "INBOX" (HIGHESTMODSEQ 561701 UIDNEXT 603 UNSEEN 64)
    20.10827 OK Success
    * STATUS "Sent Messages" (HIGHESTMODSEQ 561701 UIDNEXT 138 UNSEEN 0)
    21.10827 OK Success
    * STATUS "Deleted Messages" (HIGHESTMODSEQ 561701 UIDNEXT 89 UNSEEN 0)
    22.10827 OK Success
    WROTE Sep 30 08:35:11.537 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc3186cf640
    23.10827 IDLE
    READ Sep 30 08:35:11.927 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc3186cf640
    + idling
    READ Sep 30 08:35:15.472 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.mail.me.com -- port:587 -- socket:0x7fc31855c470 -- thread:0x7fc31858ada0
    220 st11p00mm-asmtp002.mac.com -- Server ESMTP (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013))
    WROTE Sep 30 08:35:24.784 [kCFStreamSocketSecurityLevelNone]  -- host:mail.orcon.net.nz -- port:25 -- socket:0x7fc3161a1b00 -- thread:0x7fc315d05050
    EHLO [10.1.1.4]
    WROTE Sep 30 08:35:24.822 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x7fc316e72a70 -- thread:0x7fc31850bec0
    EHLO [10.1.1.4]
    WROTE Sep 30 08:35:34.080 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.mail.me.com -- port:587 -- socket:0x7fc31855c470 -- thread:0x7fc31858ada0
    EHLO [10.1.1.4]
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc316fc30e0
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc31a6fa8a0
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316197890
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc316e813d0
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0350
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3185c0410
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315ded870
    INITIATING CONNECTION Sep 30 08:35:47.193  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e729b0
    INITIATING CONNECTION Sep 30 08:35:47.198  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3167d2380
    INITIATING CONNECTION Sep 30 08:35:47.377  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3167d2380
    INITIATING CONNECTION Sep 30 08:36:40.352  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.352  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc312c8dbc0
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31617f290
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc316e729b0
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31615a390
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316e3bbc0
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316e0cfa0
    INITIATING CONNECTION Sep 30 08:36:40.368  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31829f120
    INITIATING CONNECTION Sep 30 08:36:40.403  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc312c8dbc0
    INITIATING CONNECTION Sep 30 08:36:40.412  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.565  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc312c8dbc0
    INITIATING CONNECTION Sep 30 08:36:40.595  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.633  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.687  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.708  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.729  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3183339e0
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3186f07e0
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315a9b630
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3163e7dd0
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3172f6e70
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31616b9d0
    INITIATING CONNECTION Sep 30 08:37:33.323  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.336  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e03950
    INITIATING CONNECTION Sep 30 08:37:33.462  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.463  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3163e7dd0
    INITIATING CONNECTION Sep 30 08:37:33.509  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.528  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3163e7dd0
    INITIATING CONNECTION Sep 30 08:37:33.557  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.598  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.624  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.646  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:38:26.315  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc31686fa30
    INITIATING CONNECTION Sep 30 08:38:26.316  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316fcc7d0
    INITIATING CONNECTION Sep 30 08:38:26.316  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3170d8a90
    INITIATING CONNECTION Sep 30 08:38:26.317  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc318521490
    INITIATING CONNECTION Sep 30 08:38:26.317  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316e81b30
    INITIATING CONNECTION Sep 30 08:38:26.317  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc316fdf410
    INITIATING CONNECTION Sep 30 08:38:26.318  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315d3a890
    INITIATING CONNECTION Sep 30 08:38:26.320  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316774270
    INITIATING CONNECTION Sep 30 08:38:26.350  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316728a90
    INITIATING CONNECTION Sep 30 08:38:26.350  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.495  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316774270
    INITIATING CONNECTION Sep 30 08:38:26.538  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.591  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.619  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.642  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.666  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:39:19.257  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc31662a980
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3182e6150
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31605c330
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3184b79c0
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31658f5b0
    INITIATING CONNECTION Sep 30 08:39:19.259  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc316e03950
    INITIATING CONNECTION Sep 30 08:39:19.259  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3160d8c80
    INITIATING CONNECTION Sep 30 08:39:19.265  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31662b000
    INITIATING CONNECTION Sep 30 08:39:19.287  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316073530
    INITIATING CONNECTION Sep 30 08:39:19.287  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.420  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31662b000
    INITIATING CONNECTION Sep 30 08:39:19.457  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.505  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.531  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.552  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.573  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:40:11.346  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3161c6e50
    INITIATING CONNECTION Sep 30 08:40:11.347  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc316becee0
    INITIATING CONNECTION Sep 30 08:40:11.348  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31679c620
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3144ad030
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc3158e5b50
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc316728a90
    INITIATING CONNECTION Sep 30 08:40:11.363  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315c576d0
    INITIATING CONNECTION Sep 30 08:40:11.518  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.518  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3168cf630
    INITIATING CONNECTION Sep 30 08:40:11.548  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.568  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3168cf630
    INITIATING CONNECTION Sep 30 08:40:11.597  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.638  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.660  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.683  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:41:06.173  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318297540
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc314144080
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315d435e0
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3167306a0
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31680f3e0
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3170d8a90
    INITIATING CONNECTION Sep 30 08:41:06.197  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31671e630
    INITIATING CONNECTION Sep 30 08:41:06.223  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.223  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318569a40
    INITIATING CONNECTION Sep 30 08:41:06.376  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.396  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318569a40
    INITIATING CONNECTION Sep 30 08:41:06.431  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.475  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.503  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.527  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:59.159  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.160  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316e16c90
    INITIATING CONNECTION Sep 30 08:41:59.160  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3161e71f0
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc315f45120
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3170d94c0
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3174bc990
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31820b7d0
    INITIATING CONNECTION Sep 30 08:41:59.174  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3162884e0
    INITIATING CONNECTION Sep 30 08:41:59.189  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:41:59.189  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.344  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:41:59.363  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.409  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.430  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.450  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.471  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:42:51.209  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31a613830
    INITIATING CONNECTION Sep 30 08:42:51.210  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3168ae8d0
    INITIATING CONNECTION Sep 30 08:42:51.210  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3161d6110
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315de6190
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc316482400
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31829f120
    INITIATING CONNECTION Sep 30 08:42:51.224  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3159e76e0
    INITIATING CONNECTION Sep 30 08:42:51.372  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:42:51.372  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.402  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:42:51.421  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.466  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.492  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.514  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.536  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc315d40d90
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc315ad1930
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc316c27e30
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315adf230
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315d49010
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159a1ea0
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc318691eb0
    INITIATING CONNECTION Sep 30 09:43:23.250  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315f45120
    INITIATING CONNECTION Sep 30 09:43:23.311  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e1b2d0
    INITIATING CONNECTION Sep 30 09:43:23.311  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.427  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315f45120
    INITIATING CONNECTION Sep 30 09:43:23.471  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.524  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.547  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.574  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.598  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 10:06:17.592  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159227c0
    INITIATING CONNECTION Sep 30 10:06:17.596  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3174e7bd0
    INITIATING CONNECTION Sep 30 10:06:17.598  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315e08640
    INITIATING CONNECTION Sep 30 10:06:18.674  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.483  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318462600
    INITIATING CONNECTION Sep 30 10:06:19.539  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3162d4270
    INITIATING CONNECTION Sep 30 10:06:19.564  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159227c0
    INITIATING CONNECTION Sep 30 10:06:19.582  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.653  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.674  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.725  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.747  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:07:19.496  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316491d10
    INITIATING CONNECTION Sep 30 10:07:19.523  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3144bad30
    INITIATING CONNECTION Sep 30 10:07:19.531  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.534  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3172b7640
    INITIATING CONNECTION Sep 30 10:07:19.550  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315cbb960
    INITIATING CONNECTION Sep 30 10:07:19.626  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315842910
    INITIATING CONNECTION Sep 30 10:07:19.665  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316491d10
    INITIATING CONNECTION Sep 30 10:07:19.715  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.805  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.854  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.892  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.915  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:08:19.527  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3162aa260
    INITIATING CONNECTION Sep 30 10:08:19.553  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3162e8510
    INITIATING CONNECTION Sep 30 10:08:19.555  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315ac9950
    INITIATING CONNECTION Sep 30 10:08:19.564  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.582  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3146b1020
    INITIATING CONNECTION Sep 30 10:08:19.685  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3163d82c0
    INITIATING CONNECTION Sep 30 10:08:19.705  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3162aa260
    INITIATING CONNECTION Sep 30 10:08:19.756  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.800  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.852  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.876  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.898  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0

  • N73 problem with the usb cable

    so, i have a problem with the connectivity of my usb
    when i plug the cable to my pc or any pc it said "USB device Not Recognize"
    this happen since i use my headset often than before, is that take effect?
    or when i use card reader to transfer all file from my phone to pc, the card reader can't read the memory card.
    so is there anyone know  how to solved it?
    i dont want to take my phone to Nokia Care, i dont believe Nokia Care in my town.

    It looks like your memory card is corrupted. Reformat the card. Did you try another USB port?
    ‡Thank you for hitting the Blue/Green Star button‡
    N8-00 RM 596 V:111.030.0609; E71-1(05) RM 346 V: 500.21.009

  • Router Console Connect Problem With Mini Usb (1941 Series - Os Win7 64Bit) (SOLVED)

    I can not connect console with mini usb, my router is cisco 1941 series and my os win7 x64 help me please ?
    My problem was solved thanks to this topic;
    https://supportforums.cisco.com/discussion/11492306/usb-console-driver-install-failing#comment-9697916

    Hi,
    Here is how I have managed to enable the communication with the 1941 using the usb A-B cable:
    Download the usb console driver 3.1
    Install the x64 version on your PC (as administrator)
    After the installation was completed:
    Open the Device Manager. There will be a new entry named “CiscoUsbConsoleWindowsDrive”. Expand it and select the “Cisco USB to Serial adaptor”.
    From the drop-down select “Update Driver Software…
    In the “Update Drive Software” dialog select “Browse my computer for driver software”
    In the next window, a driver location should be displayed, if not browse your PC and find the …\Windows_64 folder where you have extracted the 3.1 driver.
    After the driver software was updated, there should be a new entry in the “Ports (COM &LPT)” named “Cisco Serial (COMx)”.
    You can configure the port here:
    Right click on the “Cisco Serial (COMx)” and select “properties” and set the properties to this;
    Bits per second :9600
    Data bits              :8
    Parity                    :None
    Stop bits              :1
    Flow control       :None
    The new COM port should be ready to accept the connection with the router.
    I am using Tera Terms VT, and it is working well with the above driver and settings.
    Should you wont to use the Cisco Configuration Professional (CCP) download the 2.7 version and make shore you have the current Adobe Flush and a current Java installed on you PC.
    Hope this will help.
    AlexS

  • Problem with the USB-connection after upgrade to P...

    Hello to everybody!
    After upgrading PC-suite, I can't establish a USB-connection with the phone.
    Here are the facts:
    1) My phone is the E90. Latest software installed (300.34.84)
    2) PC-Suite version 7.0.9.2 english. I also tried the greek version, same problem with it also.
    3) Nokia Connectivity Cable Driver 7.0.2.1. I also installed manually a previous version of the driver (7.0.2.0), but this didn't solve the problem.
    4) I didn't have any problem with the older version of PC-suite.
    5) I don't have a problem with the cable because the data-transfer-mode works fine.
    6) Prior to any installation attempt, I always first uninstalled PC-suite and Cable-driver manually with the windows-xp uninstall program. This was not the fact, only in my first attempt, where I upgraded the pc-suite from inside the program itself.
    Please help, because I can't backup and this is very important for me!
    Solved!
    Go to Solution.

    Thank you all for your suggestions but nothing of the above worked for me.
    After of hours and hours of installing and uninstalling of several versions of the pc-suite I solved the problem as following:
    1) Uninstall manually (windows - control panel - add/remove programs)Nokia-PC-Suite, Nokia Connectivity Cable Driver AND PC Connectivity Solution!
    2) Restart PC
    3) Download and install the new version of Nokia-PC-Suite.
    The tricky part is that you have to uninstall the application called "PC Connectivity Solution" manually and since the title of the application dosn't include the Nokia-Name you have first to find out that this program is Nokia-related!
    Once again, thanks to everybody who took the time to make suggestions and especially to cricfancy who made me aware of the fact that PC Connectivity Solution is a nokia application!
    Finally, I would like to make a statement for Nokia:
    People, if you are not sure about an update then keep it in beta and don't make it available to the public!!! I lost hours and hours on search and made countless installs and uninstalls to find out what was wrong. Under the line, I had made no mistakes in my update from the start and the whole problem was based on your software! This is not acceptable!

  • Audio problems with an USB interface

    Hi everyone, this is my first post and glad to finally do it.
    I am so pleased with arch linux, it's just simply amazing. I have learnt a lot following the wikis, it's pretty simple and effective.
    I managed to install and configure ssh server, samba server (surprisingly easy), usb samsung laser printer, nvidia drivers, KDE desktop (so fast in arch), fonts, cpu scaling and I'm so happy with the results and perfomance.
    The only problem I ran into is about audio, I think the wiki on audio is pretty  incomplete (don't get me wrong I enjoy your work).
    The problem is with an USB interface line 6 toneport gx (http://line6.com/toneportgx/), I know the device is meant to be an usb guitar interface but since I don't longer play guitar I use it as soundcard. As complementary information it works with no problem on Ubuntu 10.04 (which is the distro I came from).
    The interface works and it's unmuted since I dmix does not work when I try to play sounds from different sources I had to install pulseaudio. Pulseaudio works partially, the sound was improved and finally I am able to play different sources. The big problem is when high cpu load ocurrs the the audio dies and does not come back even when the cpu loads decrease.
    Any help is appreciated.
    Thanks.

    You may want to debug pulseaudio (check their wiki to see how, involves running pulseaudio in verbose mode) to see what happens.

  • Still having Problems with yamaha USB UX16 midi device can anyone help??

    I have setup drivers on my computer which have installed successfully. In logic I have setup environment so Physical input sequenser and keyboard are all connected up in Click and Ports layer.
    When I am trying to play keyboard I still have no input or outport signal in transport window I am stuck on what to do??
    please can someone help???

    I take back all I said. After reading reviews of this product, take it back to wherever you bought it and buy something else, anything else, everyone hates this thing, and is having problems with it. get a midisport instead.
    http://www.midiman.com/index.php?do=products.list&ID=usbmidiinterfaces
    here are a couple of reviews:
    Dec 12, 2006 - It is hit or miss as far as compatability goes and you don't know until it is too late if the full instruction set is going to be sent/recieved intact. Tried it on various Macs, PCs and inconsistent in every situation. Yamaha needs to issue a full recall on this POC called the UX-16.
    Nov 6, 2004 - The first Yamaha UX 16 that I bought worked okay for a day, then started to cause a buzzing noise. The next day, it was not recognized at all by my laptop. I returned it to the retailer, hoping to find a competitive portable USB/MIDI interface at another store. After failing to find an alternative at the other store, I bought the Yamaha UX16 again, hoping that the first dud was a fluke.
    The second UX16 also worked for one day before giving out.
    Avoid the UX16.
    Apr 12, 2004 - This thing only works for a short period of time then quits being detectable to windows for random periods of time. Totally unreliable.

  • Aperture 2.1.1 Vault problem with external usb  disk

    I have just updated to 2.1.1 and now Aperture freezes every time I connect my usb external disk and try to create or update a vault. I have to force quit Aperture and remove the disk before I can use Aperture again. The only way I can create a vault is to create it on my internal disk then manually copy to the external usb. Another topic here suggested the problem is with network disks but I have a very similar problem with a local usb disk. I have tried two different disks with the same results. All my software and os is up to date.
    Does anyone else have this problem?

    I have a similar problem, and have a not totally satisfactory fix for my issue.
    I have my photos stored on an external FW drive.
    Originally I also stored my vault on the same drive.
    When I started Aperture with this config then Aperture would not pass the loading screen. I would have to kill the process to quit.
    If I started Aperture with the FW drive disconnected then it would launch, but I would then attach eth FW drive and have to Manage referenced files.
    What has worked for me:
    I have removed the vault from the FW drive and Aperture now boots quickly as 2.1 did.
    I have to create the vault on the internal HD and copy to the external.

  • Audio problems with a USB turntable using Linein, right channel not playin

    I have an Audio Technica usb turntable and I am using Linein software to get the audio in. I am now missing the right channel. I use the USB connection and I have tried different cables so that is not the problem. I also tried using the RCA cables, plugged into the micro phone/line-in port via an an RCA to single stereo adapter up which did not solve the problem either. In fact when I switched the red white, left right cables the sound still only came out from the left channel and subwoofer. Both channels work fine with Itunes so it is not the speaker system. I am thinking that it is a setting problem with the software either the Linein or Mac OS. Does anyone use Linein and what settings should I be looking at, Midi settings, Sound preferences? Thanks.

    Apple>About This Mac>More Info>Service
    Please read the warranty paperwork that came w/your computer.
    You have 14 days to return the computer w/no questions asked. 
    You have 90 days of FREE phone tech support on top of your standard 1 year warranty unless you also purchased AppleCare which gives you an additional 2 years of coverage plus FREE phone support.
    Strongly suggest that you take FULL advantage of the above before it runs out.  Let Apple deal w/the problems.

  • Problems with multiple USB devices. (Possible Low Power on USB Bus)

    I believe I'm having an issue with the USB bus or one of my devices that I have installed on my iMac.
    I purchased this iMac along with a printer (HP C4280 All-in-One) as part of a promotion deal. I also have wireless logitech USB mouse, and iPhone and an 80gb 5th Gen iPod.
    My problem has to do with syncing the iPod and iPhone. Normally I have the printer attached to the iMac along with the USB mouse. Both devices function as expected. However I have problems when I connect the iPhone or iPod.
    iPod Symptoms: When I connect the iPod the iPod screen shows the flashing red circle with a line but iTunes never launches and the iPod never syncs.
    iPhone Symptoms: When I connect the iPhone the iPhone screen says Sync in Progress and iTunes does show the iPhone in the list of devices but a dialog appears giving me one of two messages (that I've seen so far) - [msg 1] Your iPhone is corrupt please disconnect then reconnect to restore. [msg 2] iPhone device timed out.
    I've been dealing with this problem for a couple months and found that if I disconnect the printer (HP C4280) then connected either other device then everything works just fine.
    I downloaded XCode 2.5 and launched the USB Prober utility. Then plugged in each device in turn and found some interesting findings.
    When connecting the iPhone (1st attempt) the USB Logger reported; (iTunes displayed msg 1 from above)
    128.517 [1] USB Device iPhone is violating Section 9.3.5 of the USB Specification -- Error in GetConfigDescriptor( wLength = 4)
    128.520 [1] USB Low Power Notice: The device "iPhone" cannot be used because there is not enough power to configure it
    128.528 [1] USB Low Power Notice: The device "iPhone" cannot be used because there is not enough power to configure it
    128.629 [1] AppleIRController[0x2dc8e00]::RearmInterruptRead immediate error 0xe000404f queueing read, clearing stall and trying again(1)
    When connecting the iPod (1st attempt) the USB Logger reported; (iTunes never showed that the iPod devices was connected)
    938.797 [1] USB Device IOUSBDevice is violating Section 9.3.5 of the USB Specification -- Error in GetConfigDescriptor( wLength = 4)
    938.801 [1] IOUSBCompositeDriver[0x39b9f80](IOUSBDevice) SetConfiguration (1) returned 0xe00002ed
    938.900 [1] AppleIRController[0x2dc8e00]::RearmInterruptRead immediate error 0xe000404f queueing read, clearing stall and trying again(1)
    When connecting the iPhone (2nd attempt) the USB Logger reported; (iTunes displayed msg 2 from above)
    1789.023 [1] AppleIRController[0x2dc8e00]::RearmInterruptRead immediate error 0xe000404f queueing read, clearing stall and trying again(1)
    1802.166 [1] AppleUSBEHCI[0x28a7000]::Found a transaction which hasn't moved in 5 seconds on bus 253, timing out!
    1809.166 [1] AppleUSBEHCI[0x28a7000]::Found a transaction which hasn't moved in 5 seconds on bus 253, timing out!
    I'm suspicious of the USB Low Power Notice. If this is true then I suspect the my iMac might need some type of repair. However I am also suspicious of USB Device violating the USB Spec Error. Although this is the message that appears when I plug in the iPhone or iPod I don't think I can assume that error relates to the iPod or iPhone. The error doesn't specify which USB Device is in violation.
    My current workaround is to unplug the printer every time I sync the iPhone or iPod which is cumbersome. I'm also worried that repeated connecting/disconnecting of USB plug for the printer will over time damage the USB port.
    I'm not sure what options I have here. Can anyone provide some suggestions or information that might provide some insight.
    Best Regards,
    xgnomex

    A-Ha! Now I'm feeling like my 1.5 hours of reading this forum are not wasted, since I've found others with similar symptoms.
    I've only had my iMac for two weeks today. I've got some new accessories & have experimented with the ones I've had awhile (various USB external drives). My model has 3 USB ports, one of which is taken by the keyboard, of course.
    Over the weekend, I picked up an MS Office 2008 Upgrade and also an HP Officejet Pro L7680 all-in-one. I only mention the Office upgrade because I installed it on the same day as the printer, but it's possibly unrelated.
    I actually have a Belkin 4-port hub--not the same one suggested in this thread, but externally powered with it's own A/C adapter. (It's a Hi-Speed USB 2.0 r-Port Hub, model F5U234 Rev.3, and I used it with a previous iMac G3 CRT with no problem.)
    So with a LaCie 100 GB USB Mobile Drive in one of the iMac's ports, and the HP L7680 in the iMac's third port, or the HP via the Belkin hub in iMacs the third hub, here are some of the symptoms I've seen:
    1) while browsing in Firefox, suddenly the mouse-cursor will "freeze" (get stuck) in a pull-down selector...sometimes it unfreezes, but eventually (like on the next pull-down menu) the keyboard & mouse will shut off (and if you wait & the iMac goes to sleep, the keyboard won't let me enter my unlock password when I wake the iMac with the Apple Remote)
    2) when trying to open a document from the LaCie in MS Word, Word freezes and the keyboard & mouse go dead--terminal beachball--to restart the computer, I have to hold in the power button
    3) when trying to print a message in Mail, Finder freezes (though the print job does finish)
    These symptoms seem strange! Hey, it's just supposed to work, right? But everything has limits, so my question becomes, "how much stuff can I hook up at once?"
    I wonder if this Apple article is addressing this issue:
    http://docs.info.apple.com/article.html?artnum=25243
    especially when it says "Two high-bandwidth devices or two isochronous devices cannot be connected to a single Universal Serial Bus (USB)."
    So only two hi-speed USB devices can be connected "to the same bus" simultaneously? I'm not entirely sure I understand what "isochronous" means, but I'm thinking I need to peel my printer off the USB somehow, maybe via Airport Express--?
    Does anyone know for sure about USB limitations? Thanks.
    Also, xgnomex, how/where did you find that "USB Logger"? Is that something iPhone-specific, or is it an OS X log in a Library somewhere?

Maybe you are looking for

  • Naming.lookup() returns null???? Why??

    I read about this in a previous forum but there was no answer given to someones question about it. Sometimes Naming.lookup() returns null and a later call will succeed. Is there a recognised reason for this? Is it a recognised bug or undocumented fea

  • My HP Pro 8500 will not print in blue. All new cartridges installed.

    My HP Pro 8500 will not print the a blue color, it comes out pint where it should be blue.  Installed all new cartridges and still does the same thing.

  • Help with an EtreCheck Report

    I have an older iMac running Yosemite and I just ran the EtreCheck and this the report. I am not sure what it means by "memory pressure" or what the solution is to the issue? Thanks EtreCheck version: 2.1.8 (121) Report generated April 3, 2015 at 11:

  • Debug Problem in Indesign cs5.5

       We are having Plugin for adobe indesign cs5.5 and installed adobe indesign debugger.. While debugging our source code we are getting the values of integer data types, but we are not known the values of data types related to PMString, PMMatrix, PMR

  • Backdrops with Sony DV Camcorder in iChat and Photo Booth

    Hello I have found the Backdrops will not work with my DV camcorder, I have seen on apple's iChat page that "Backdrop effects when using a DV camcorder require fixed focus, exposure, and white balance". How do I do that with my camcorder (or can it e