SOLVED: W510 Wired Network Stops working

I had a problem with a W510 I ordered with Windows 7 32 bit. At random times, the exclamation point icon would appear over the network icon in the system tray, and the network adapter would no longer be recognized. I could use the built in Windows facilities to reset the adapter, but it would quickly fail again. The only cure was to restart the machine, which was annoying. Wireless networking was not affected - just the wired Ethernet connection.
I downloaded the latest drivers from the Lenovo site and that did not fix it. I have had numerous Thinkpads over the past 12 years and have NEVER had any sort of hardware fault before, so I doubted that it was a hardware fault. Therefore I wiped the machine clean and installed 64 Bit Windows 7 instead.
The first problem I had after installing Win7 x64 was that the internal USB controller was not recognized by Windows. Therefore, USB devices (i.e. my thumb drive with all the x64 Lenovo drivers on) were no longer recognized. Therefore, I burned the x64 drivers to a CD and used that instead.
All the devices including the USB controller then came to life, and it looks like the problem has been completely solved.
I post this, in case anybody else has such a problem. 

I just started seeing this issue with my pen silo.  The Wacom tablet component has completely stopped working, and I'm seeing "USB device not recognized" every time I insert and draw out the pen.  My guess is that all the peripheral components in the tablet are connected to the motherboard via crappy silver trace ribbon cables, and they're susceptible to the tiniest amount of flex, heat, and disruption.
Since the USB device is, at least in my case, still operating well enough to report that it is having trouble, I'm guessing that the issue is transient, but that doesn't fix my problem - and probably won't fix yours.  I'd recommend getting a refund.
Here's how to see if the device is reporting a problem:
1) Wait until you see the "USB device not recognized" message again.
2) CTRL+X -> Device Manager
3) Other Devices -> double-click "Unknown device"
4) Go to "Details" tab
5) Select "DevNode status" from the drop-down; the Value pane will have DN_HAS_PROBLEM on one of the lines.
6) Select "Problem code" from the drop-down; the Value pane will likely show "0000002B", or Microsoft USB problem code 43 in decimal.

Similar Messages

  • Wired network stopped working

    Hi all,
    Since recently, and without any changes to network related config files, wired connections do not work any longer. Wireless connections still do.
    I'm somehow suspecting this is DHCP related.
    dhcpcd is not running as as systemd.service but started by NetworkManager. Upon activating wireled connection through gnome network settings I'm seeing
    # ps aux | grep dhcpcd
    /usr/bin/dhcpcd -B -K -L -G -c /usr/lib/networkmanager/nm-dhcp-client.action eth0
    # journalctl -f
    NetworkManager[444]: <info> Activation (eth0) starting connection 'Wired'
    NetworkManager[444]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    NetworkManager[444]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager[444]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager[444]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager[444]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager[444]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager[444]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
    NetworkManager[444]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
    NetworkManager[444]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
    NetworkManager[444]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager[444]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
    NetworkManager[444]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
    NetworkManager[444]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    dhcpcd[2044]: version 6.0.5 starting
    NetworkManager[444]: <info> dhcpcd started with pid 2044
    NetworkManager[444]: <info> Activation (eth0) Beginning IP6 addrconf.
    NetworkManager[444]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
    dhcpcd[2044]: eth0: soliciting an IPv6 router
    dhcpcd[2044]: eth0: ipv6rs_sendprobe: sendmsg: Cannot assign requested address
    NetworkManager[444]: <info> (eth0): DHCPv4 state changed nbi -> preinit
    dhcpcd[2044]: eth0: soliciting a DHCP lease
    NetworkManager[444]: <info> (eth0): IP6 addrconf timed out or failed.
    NetworkManager[444]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    NetworkManager[444]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    NetworkManager[444]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    dhcpcd[2044]: timed out
    dhcpcd[2044]: exited
    NetworkManager[444]: <info> (eth0): DHCPv4 client pid 2044 exited with status 1
    NetworkManager[444]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
    NetworkManager[444]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) started...
    NetworkManager[444]: <info> (eth0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
    NetworkManager[444]: <info> Marking connection 'Wired' invalid.
    NetworkManager[444]: <warn> Activation (eth0) failed for connection 'Wired'
    NetworkManager[444]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
    NetworkManager[444]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    NetworkManager[444]: <info> (eth0): deactivating device (reason 'none') [0]
    # systemctl
    NetworkManager.service loaded active running Network Manager
    # systemctl list-unit-files
    dhcpcd.service disabled
    Is it anything obvious that I'm doing wrong here?
    Last edited by walz (2013-09-02 10:00:56)

    Thanks for the nice welcome and all the quick replies. I forgot to subscribe to the topic to answer sooner.
    I can confirm that the network device is not renamed
    # ifconfig
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    Strike0 wrote:
    Things to try:
    1. Put IPv6 to "local link only" in network manager
    2. Stop NM and try to connect manually, using
    # systemctl stop NetworkManager
    # ip link set up dev eth0
    # dhcpcd -A
    3. If that fails, install "dhclient" and try with that.
    1. Setting IPv6 to "local link only" results in the following journalctl output when activating 'Wired'
    NetworkManager[568]: <info> Activation (eth0) starting connection 'Wired'
    NetworkManager[568]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    NetworkManager[568]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager[568]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager[568]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager[568]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager[568]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager[568]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
    NetworkManager[568]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
    NetworkManager[568]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
    NetworkManager[568]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager[568]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
    NetworkManager[568]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
    NetworkManager[568]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    NetworkManager[568]: <info> dhcpcd started with pid 5027
    NetworkManager[568]: <info> Activation (eth0) Beginning IP6 addrconf.
    dhcpcd[5027]: version 6.0.5 starting
    NetworkManager[568]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
    NetworkManager[568]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) scheduled...
    NetworkManager[568]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) started...
    dhcpcd[5027]: eth0: soliciting an IPv6 router
    dhcpcd[5027]: eth0: soliciting a DHCP lease
    NetworkManager[568]: <info> (eth0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    NetworkManager[568]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) complete.
    NetworkManager[568]: <info> (eth0): DHCPv4 state changed nbi -> preinit
    NetworkManager[568]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    NetworkManager[568]: <info> Activation (eth0) successful, device activated.
    dbus[596]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
    dbus[596]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: ...e' for details.
    dbus-daemon[596]: dbus[596]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
    dbus-daemon[596]: dbus[596]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service...' for details.
    NetworkManager[568]: <warn> Dispatcher failed: (32) Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory. See system logs and 'system...' for details.
    dhcpcd[5027]: eth0: no IPv6 Routers available
    gnome-session[1833]: [3601:3653:0902/105453:ERROR:download_updates_command.cc(187)] PostClientToServerMessage() failed during GetUpdates
    dhcpcd[5027]: timed out
    dhcpcd[5027]: exited
    NetworkManager[568]: <info> (eth0): DHCPv4 client pid 5027 exited with status 1
    NetworkManager[568]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
    NetworkManager[568]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) started...
    NetworkManager[568]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
    dbus-daemon[596]: dbus[596]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
    dbus[596]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
    dbus[596]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: ...e' for details.
    dbus-daemon[596]: dbus[596]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service...' for details.
    2. NetworkManager immediately restarts, when being stopped. Thus, I disabled it and tried your steps.
    # systemctl disable NetworkManager
    # ip link set up dev eth0
    # ip link
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether e8:03:9a:a6:0a:41 brd ff:ff:ff:ff:ff:ff
    3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT qlen 1000
    link/ether c4:85:08:0a:cc:b5 brd ff:ff:ff:ff:ff:ff
    # dhcpcd -A
    dhcpcd[5319]: version 6.0.5 starting
    dhcpcd[5319]: wlan0: up_interface: Operation not possible due to RF-kill
    dhcpcd[5319]: eth0: soliciting an IPv6 router
    dhcpcd[5319]: eth0: soliciting a DHCP lease
    dhcpcd[5319]: wlan0: waiting for carrier
    dhcpcd[5319]: eth0: no IPv6 Routers available
    dhcpcd[5319]: timed out
    dhcpcd[5319]: forked to background, child pid 5366
    I also tried explicitely turning off IPv6
    # dhcpcd -4
    which also ended in a time out.
    As neither solution worked, I'm going to try dhclient this evening.

  • [Solved]Vbox 3.1.2 - Bridged networking stopped working on Arch guest

    After upgrading Virtual Box to 3.1.2 (both ose and puel versions apply here) bridged networking stopped working on an Arch guest which I use as a test server.
    While writing this post I solved the problem. What I did was to enable NAT on the first adapter and Bridging on the second. After booting into to the guest I did the following;
    # ifconfig eth1 up
    # dhcpcd eth1
    I shutdown the guest and removed the NAT adapter so only the bridged one remained, booted it and voilá for some mysterious and unfathomable reason bridging now works again.

    After upgrading Virtual Box to 3.1.2 (both ose and puel versions apply here) bridged networking stopped working on an Arch guest which I use as a test server.
    While writing this post I solved the problem. What I did was to enable NAT on the first adapter and Bridging on the second. After booting into to the guest I did the following;
    # ifconfig eth1 up
    # dhcpcd eth1
    I shutdown the guest and removed the NAT adapter so only the bridged one remained, booted it and voilá for some mysterious and unfathomable reason bridging now works again.

  • Apple wired keyboard stops working after iTunes sync

    I have an imac running snow leopard.  When I sync old ipad, iphone 3gs or iphone 4, the wired keyboard stops working.  The only solution seems to be to turn the IMac off and turn on again.  Have tried resetting permissions with no success. Any ideas?

    Try resetting the NVRAM
    About NVRAM and PRAM
    Try another BK. Maybe a KB problem.
    Try booting to Recovery and see if it works OK. Maybe a software problem with Yosemite
    OS X: About OS X Recovery - Apple Support

  • Wired keyboard stops working

    My wired keyboard stops working a lot of the time. Message saying can't find keyboard and trying to connect to wired keyboard (which I don't use). If I close down and switch off at mains for 10 minutes or so Mac finds keyboard when starts again. Any ideas how I can fix this?

    Try resetting the NVRAM
    About NVRAM and PRAM
    Try another BK. Maybe a KB problem.
    Try booting to Recovery and see if it works OK. Maybe a software problem with Yosemite
    OS X: About OS X Recovery - Apple Support

  • My phone fall down and suddenly the network stopped working can't find for any coverage, And I already reset the all settings and network settings!!! plz help me

    my phone fall down and the network stopped working can't search to any coverage

    It is not properly connected to the network.
    Make sure location is set correctly
    DNS should be on auto (settings - general - network)
    Try ethernet
    Signal strength on device won't account for issues, you would need a network report from istumbler, netstumbler or similar. This will show accurate signal strength along with noise and nearby networks

  • [solved] Network stopped working after update

    Hi,
    I have been working on this problem for some time now with no success. I searched the forums and found threads like this, which did not seem to work for me. I hope it is (as always) just a stupid mistake I made.
    After a bigger update (not using the machine for half a year) I cannot get my network back to work. I am talking about wired network, though wireless network has a similar problem. I verified the hardware via a Windows dualboot.
    I think this problem is DHCP related:
    # dhcpcd enp2s0
    dhcpcd[563]: version 6.0.5 starting
    dhcpcd[563]: enp2s0: waiting for carrier
    dhcpcd[563]: enp2s0: carrier acquired
    dhcpcd[563]: enp2s0: carrier lost
    dhcpcd[563]: enp2s0: waiting for carrier
    dhcpcd[563]: enp2s0: carrier acquired
    dhcpcd[563]: enp2s0: soliciting a DHCP lease
    dhcpcd[563]: timed out
    dhcpcd[563]: exited
    I usually run NetworkManager and dhcpcd, but also tried wicd and dhclient which did not help either.
    I have no idea which outputs can be helpful in this matter, so I will provide them on demand. Thanks in advance.
    Last edited by CommanderCool (2013-09-11 09:40:26)

    I just want to add that connecting with a static IP works flawlessly. I am trying to connect to a Fritz Box 7270, if that helps. I have the same problem on another machine. The problem occured with the update from dhcpcd 5.6.4-2 to 6.0.5-1, I guess, but I cannot be absolutely sure.
    I already tried commenting out the "require dhcp server_identifier" option of dhcpcd, which did noch change anything. I am really lost here, so any hint would help.

  • Wired network dont work, cant install

    Hi i tray to install Arch linux like this man http://www.youtube.com/watch?v=VJb6bZm5QOc, but my wired or wlan network wont work, when i ping -c 3 www.google.com it say unknown host, when i ping -c 3 8.8.8.8 say destination host unreachable. I dont know what to do now.
    Can you help me please!?

    i doing this
    # systemctl stop dhcpcd.service
    # ip link
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: enp2s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
        link/ether 00:11:25:31:69:20 brd ff:ff:ff:ff:ff:ff
    3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT qlen 1000
        link/ether 01:02:03:04:05:06 brd ff:ff:ff:ff:ff:ff
    # iwconfig
    enp2s0f0  no wireless extensions.
    wlp3s0    IEEE 802.11bgn  ESSID:"NETGEAR97"
              Mode:Managed  Frequency:2.427 GHz  Access Point: 2C:B0:5D:9C:72:BF
              Bit Rate=65 Mb/s   Tx-Power=16 dBm
              Retry  long limit:7   RTS thr:off   Fragment thr:off
              Power Management:on
              Link Quality=61/70  Signal level=-49 dBm
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:430   Missed beacon:0
    lo        no wireless extensions.
    # ip link set enp2s0f0 up
    # ip addr add 192.168.1.2/24 dev enp2s0f0
    # ip route add default via 192.168.1.1
    # nano /etc/resolv.conf
    nameserver 192.168.1.1
    search dummy.porta.siemens.net
    ONLY enp2s0f0, CHANGE WITH enp4s0 when i put line
    but wont work,
    wireless network say no wifi-menu package!?
    I dont know what to do now?
    Last edited by max300f (2013-05-21 13:31:16)

  • Wired ethernet stops working on c2d MBP

    I am a new 15 inch C2D MBP owner and I'm just starting to learn all the Mac stuff... I need your help because I have a serious problem with wired ethernet stability under macOS. I need to know if it's something specific to my machine or if anyone else has similar problem.
    I am connected to a LAN with a 10/100 Mbit switch. I'm using a good cable (checked!). And my connection seems to hang from time to time. Usually this happens under heavier load (torrent plus multi-tab browsing), but it dies sometimes during casual browsing or checking for system updates. And it's anywhere from 3 minutes to 12 hours between hangs...
    The symptoms are strange. The connection seems to be on, but there's a sudden surge in bad packet received number and the network connection stops working remaining on-line. Putting the machine to sleep or manually shutting down the line helps immediately. I'm using:
    sudo ifconfig en0 down
    sudo ifconfig en0 up
    At first I suspected hardware problem but the same line works perfectly under Windows (with even higher load, and tcpip.sys patched to 1000 connections).
    It acted like this from the very first moment I got it and I have no clue if I should contact service or wait for a patch or maybe just stick to Windows (just kidding)...
    I've browsed the forum and it seems I'm not the only one with the problem:
    http://discussions.apple.com/thread.jspa?threadID=649927
    but this topic is unsolved... There's nothing really strange in system.log:
    Dec 15 17:22:45 honsiu kernel[0]: AppleYukon: bad packet received. length: 20, packet status bits: Packet fragment
    Dec 15 17:25:01 honsiu sudo: Janek : TTY=ttyp1 ; PWD=/Users/Janek ; USER=root ; COMMAND=/sbin/ifconfig en0 down
    Dec 15 17:25:04 honsiu sudo: Janek : TTY=ttyp1 ; PWD=/Users/Janek ; USER=root ; COMMAND=/sbin/ifconfig en0 up
    Dec 15 17:25:05 honsiu configd[41]: posting notification com.apple.system.config.network_change
    Dec 15 17:25:05 honsiu lookupd[13803]: lookupd (version 369.6) starting - Fri Dec 15 17:25:05 2006
    Dec 15 17:25:05 honsiu kernel[0]: AppleYukon - en0 link active, 100-Mbit, half duplex
    Dec 15 17:25:06 honsiu kernel[0]: AppleYukon: bad packet received. length: 21, packet status bits: Packet fragment
    Any hints appreciated. It's a beautiful machine and I'm so sorry it doesn't work as it should...
    15inch C2D MacBook Pro   Mac OS X (10.4.8)  

    evans_re,
    does the trackpad not work? If it works, you could try selecting “Shut Down…” from the Apple menu.
    As a last resort, you can hold down the power button for approximately ten seconds, which should force a (non-clean) shutdown.
    If your keyboard is completely non-functional (excepting the power button), then you should take it to an Apple store or other qualified service facility.

  • Wired Remote stopped working.. PLEASE HEL

    I got the zen a few months ago, with little problems thus far. Last month, my headphones decided to stop working. No big deal, I am very acti've so I figured I was just too rough with them. I bought some new phones, Sony in ear types. Recently, my Wired Remote has stopped working. It will work some days, and then stop working just like that.
    I am just wondering if this has happened to anyone else out there.. and if so, how they solved their problem.
    Please help, and thanks.

    The wired remotes are notoriously badly made - you'll probably need to contact Creative support to get it replaced.

  • Network stops working in Tecra M9 with Vista OS?

    We have four Toshiba tecra M9 (2.2ghz T7500 processor) laptops with factory installed windows vista business version and one with fresh non toshiba installation of Vista Ultimate version. All these laptops have exactly same problem.
    Network sometimes stops working and nothing but restarting computer helps?
    Thing is that usually you cant event restart computer because it hangs to logging off or to shutting down state.
    Theres no clear reason to this hang and it happens now and then.
    Sometimes many times a day and sometimes it works for days. Doesnt matter if you are docked or undocked. We have several desktops pcs and other brand laptops with exactly same configuration/programs and no problems.
    Any help would be great because users are not very pleased to this situation and we wouldnt want to change back to windows XP (which is working in M9 without problems).

    All vista updates are installed to all these computers. BIOS is newest 1.50 that is available from web site. Toshiba Value Added Package for Windows Vista (v1.1.7; 12-14-2007; 38.89M) package is only new driver that has released from Toshiba since purchase of these machines. Four factory installed Vista M9 models have original driver versions (not sure if they are newest ones). One Vista Ultimate has drivers downloaded from Toshiba support site and it even has Vista Servicepack 1 RC-1 version installed.
    I installed that new value added package two days ago and no networks hangs yet but still have to wait because it might work for week and then start hanging again.

  • [SOLVED]Kmail imcoming notification stopped working

    Hi!
    I have up-to-date system. My notification theme is colibri. Until few hours ago incoming notification worked but after i changed my plasma-theme to caledonia it stopped working. I doubt it that this is a reason because i changed the theme back to Air and incoming notification still didn't work. Any clues?
    EDIT: I didn't do anything but now out of a sudden it has started to working. I am really confused now. I will tag the question as SOLVED.
    Last edited by Shark (2012-02-26 20:37:34)

    sajoch wrote:
     I am using Skype version 6.11 (455), and iOS X version 10.9.
    I am not receiving sound notification of any kind other than "You are logged in"
    Thank you for the version info. I'd recommend an upgrade to 6.12, although it's not likely to be the problem in this particular case.
    What is your Sound Effects device in System Preferences > Sound? Many Skype sounds are alerts and use the Sound Effects channel instead of the general output channel. If the device is set to something which won't play, or the alert volume is set too low, you will not hear Skype alerts, just as you won't hear Finder alerts such as moving a file to the trash.

  • Apple (wired) keyboard stopped working

    Hi everyone,
    I bought a 2.8 GHz Quad-Core Intel Xeon "Nehalem" processor Mac Pro (model MC560LL/A) in April, 2011.
    1 year and one month later (after the warranty expired, natch), the apple wired keyboard (MB110LL/B) that came with the computer stopped working. No stuck keys or repeating characters, just stopped working altogether.
    I didn't drop the keyboard, or spill anything on it. As a matter of fact, I kept the keyboard clean with a cover. I tried the keyboard in every USB port, no dice. I've rebuilt permissions and zapped the PRAM, still no dice. I'm stuck using the clickety-clackety black keyboard from my G4.
    Has anyone else had this problem?
    Since it's been one month (and 2 weeks) out of warranty, should I still try to get Apple to replace it?
    Thanks in advance for any help.
    p.s.- OS 10.6.8

    OK, it looks like Christmas came early.
    I called Apple (and spoke to a WONDERFUL service agent named Hannah), and she agreed to send me a replacement keyboard at no charge, even though the warranty on my non-working keyboard expired 38 days prior.
    I was wanting to replace the wired keyboard that I have with another wired keyboard, because of the numeric pad. Unfortunately, Hannah informed me that Apple no longer sells the wired ones and that I would be getting a wireless keyboard as replacement. Bummer.
    I ended up buying a new wired one, because I really need the numeric pad. I'll have to send the wireless one back. I feel awful that the good will was wasted. At least I left a glowing review for her and suggested that she get a raise!

  • IPhone 5 data network stops working when using GPS

    Hello,
    I have a strange problem for some time now. The DATA connection in GPS apps stop working when navigating. When I use Google maps or WAZE apps the first time after rebooting the device, everything is working just fine for first address search, but after beginning the navigation, DATA network disappears only for the navigation app, browsing is working just fine (a bit slowly, but fine).
    Tried to factory reset the device few times, and changed the carrier provider, didn't help
    Any ideas??? 

    Hi liokap,
    Welcome to the Apple Support Communities!
    I know that it can be frustrating when applications you downloaded from the App Store do not function as expected. In this situation, I would recommend working through the troubleshooting steps in the attached article.
    iOS: An app you installed unexpectedly quits, stops responding, or won’t open - Apple Support
    Have a great day,
    Joe 

  • PSE 13 solves "Error: Licensing has stopped working" on MAC OS X 10.10.2?

    After some years using my reliable PS8 I've got this nasty message and I am unable to work since then.
    I've been working on solving the "Error: Licensing has stopped working" on MAC OS X 10.10.2 for a while without success.
    Does PSE 13 solves the problem? I just want to be sure that if I buy the new version it is going to work or if I am going to lose another US$ 99 on a piece of software that requires more "MAC OS X" expertise than I have.
    Any help, clue or piece of advice is welcome.

    Thank you, but it is exactly the paper I've been trying to follow.... I can't go through solution 2 because I got an error when using “sudo python “.
    After trying for some days I am thinking about buying the newest version (PSE 13), I just want to be sure I am not going to have the same error.... ;-)

Maybe you are looking for