NetworkManager: (cdc-wdm1) failed to connect modem: NoDeviceSupport

Starting this afternoon, whenever I try to connect to mobile broadband, the connection fails and I get the following information in the log...but it worked this morning!
Jun 16 20:53:45 tpx1c NetworkManager[273]: <info> Activation (cdc-wdm1) starting connection 'T-Mobile'
Jun 16 20:53:45 tpx1c NetworkManager[273]: <info> (cdc-wdm1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun 16 20:53:45 tpx1c NetworkManager[273]: <info> Activation (cdc-wdm1) Stage 1 of 5 (Device Prepare) scheduled...
Jun 16 20:53:45 tpx1c NetworkManager[273]: <info> Activation (cdc-wdm1) Stage 1 of 5 (Device Prepare) started...
Jun 16 20:53:45 tpx1c NetworkManager[273]: <info> Activation (cdc-wdm1) Stage 1 of 5 (Device Prepare) complete.
Jun 16 20:53:45 tpx1c ModemManager[236]: <info> Simple connect started...
Jun 16 20:53:45 tpx1c ModemManager[236]: <info> Simple connect state (4/8): Wait to get fully enabled
Jun 16 20:53:45 tpx1c ModemManager[236]: <info> Simple connect state (5/8): Register
Jun 16 20:53:45 tpx1c ModemManager[236]: <info> Simple connect state (6/8): Bearer
Jun 16 20:53:45 tpx1c ModemManager[236]: <info> Simple connect state (7/8): Connect
Jun 16 20:53:45 tpx1c ModemManager[236]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: state changed (registered -> connecting)
Jun 16 20:53:45 tpx1c ModemManager[236]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: state changed (connecting -> registered)
Jun 16 20:53:45 tpx1c NetworkManager[273]: <info> (cdc-wdm1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
Jun 16 20:53:45 tpx1c NetworkManager[273]: <info> (cdc-wdm1) modem state changed, 'connecting' --> 'registered' (reason: user-requested)
Jun 16 20:53:45 tpx1c NetworkManager[273]: <warn> (cdc-wdm1) failed to connect modem: NoDeviceSupport
Jun 16 20:53:45 tpx1c NetworkManager[273]: <info> (cdc-wdm1): device state change: prepare -> failed (reason 'unknown') [40 120 1]
Jun 16 20:53:45 tpx1c NetworkManager[273]: <warn> Activation (cdc-wdm1) failed for connection 'T-Mobile'
Jun 16 20:53:45 tpx1c NetworkManager[273]: <info> (cdc-wdm1): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jun 16 20:53:45 tpx1c NetworkManager[273]: <info> (cdc-wdm1): deactivating device (reason 'none') [0]
Jun 16 20:53:45 tpx1c NetworkManager[273]: <warn> (cdc-wdm1) firewall zone remove failed: (32) UNKNOWN_INTERFACE: cdc-wdm1
Jun 16 20:53:50 tpx1c ModemManager[236]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: signal quality updated (45)

I also have a HUAWEI k3765 and it's not working.
I'm a little confused about the way some of you solved it, and need some advice.
I tried to recompile modemmanager-0.3.2 against ppp-2.4.5-1 but doesn't work, in my system with kernel26 2.6.32.1-1 and networkmanager 0.7.2-1.
My dmesg shows this, when I connect the modem:
usb 3-3: new high speed USB device using ehci_hcd and address 6
usb 3-3: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
scsi 3:0:0:0: CD-ROM            Vodafone CD ROM (Huawei)  2.31 PQ: 0 ANSI: 2
sr1: scsi-1 drive
sr 3:0:0:0: Attached scsi CD-ROM sr1
sr 3:0:0:0: Attached scsi generic sg2 type 5
usb-storage: device scan complete
It seems not to being recognizing the modem and not creating ttyUSB0 and ttyUSB1.
So, it would be nice to know which versions you are using from programs listed below, with a working k3765:
-networkmanager
-modemmanager
-ppp
-kernel26
By the way... A HUAWEI E220 it's working normally in my system.
Thank's.

Similar Messages

  • Network Manager fails to connect with Huawei E3276 modem after upgrade

    Hi,
    I have Huawei E3276 (lsusb: Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard).
    I wasn't updating the system for a long time (since KDE 4.14.3), but after upgrade Network Manager can't connect anymore.
    I also tried on the fresh install on different machine (KDE + Plasma 5.3), but I get the same error...
    Error: failed to connect modem: Only IPv4 is supported by this modem.
    I realize that this problem has nothing to do with KDE, but with new version of NM + MM, systemd, dhcpcd or dhclient?
    Why now Network Manager don't use ppp like before upgrade (different connection type "cdc-wdm0")?
    I would be grateful for any advice.
    After upgrade (KDE 4.14.3 -> 15.04 apps/5.2 plasma):
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now CONNECTING
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> need-auth (reason 'none') [40 60 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect started...
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (5/8): Register
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (6/8): Bearer
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (7/8): Connect
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0) failed to connect modem: Only IPv4 is supported by this modem
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> failed (reason '(null)') [40 120 1]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now DISCONNECTED
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> Disabling autoconnect for connection 'Orange'.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0): Activation: failed for connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): deactivating device (reason 'none') [0]
    Before upgrade (KDE 4.14)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) starting connection 'Orange'
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> NetworkManager state is now CONNECTING
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect started...
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (4/8): Wait to get fully enabled
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (5/8): Register
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (6/8): Bearer
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (7/8): Connect
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <warn> (ttyUSB0): port attributes not fully set
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (8/8): All done
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> (ttyUSB0): failed to look up interface index
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> using modem-specified IP timeout: 20 seconds
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> starting PPP connection
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> pppd started with pid 780
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    mar 23 19:31:33 AsusN56VZ pppd[780]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ kernel: PPP generic driver version 2.4.2
    mar 23 19:31:33 AsusN56VZ pppd[780]: pppd 2.4.6 started by root, uid 0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ kernel: PPP BSD Compression module registered
    mar 23 19:31:33 AsusN56VZ kernel: PPP Deflate Compression module registered
    mar 23 19:31:35 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (umts -> hspa-plus)
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> PPP manager(IP Config Get) reply received.
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    Linux Mint 17.1 KDE (works the same like Arch before update)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) starting connection 'Orange Standard access - with image compression'
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTING
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect started...
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect state (3/8): Enable
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
    May 7 20:06:33 mint17-vm ModemManager[781]: <warn> (ttyUSB1): port attributes not fully set
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    May 7 20:06:34 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (80)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (4/8): Wait to get fully enabled
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (5/8): Register
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (6/8): Bearer
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> WWAN now enabled by management service
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (7/8): Connect
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (77)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown -> lte)
    May 7 20:06:35 mint17-vm ModemManager[781]: <warn> (ttyUSB0): port attributes not fully set
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (8/8): All done
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> (ttyUSB0): failed to look up interface index
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> using modem-specified IP timeout: 20 seconds
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> starting PPP connection
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> pppd started with pid 2468
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    May 7 20:06:35 mint17-vm pppd[2468]: Plugin /usr/lib/i386-linux-gnu/pppd/2.4.5/nm-pppd-plugin.so loaded.
    May 7 20:06:35 mint17-vm pppd[2468]: pppd 2.4.5 started by root, uid 0
    May 7 20:06:35 mint17-vm pppd[2468]: Using interface ppp0
    May 7 20:06:35 mint17-vm pppd[2468]: Connect: ppp0 <--> /dev/ttyUSB0
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded: Welcome!!
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded
    May 7 20:06:35 mint17-vm kernel: [ 82.363825] PPP BSD Compression module registered
    May 7 20:06:35 mint17-vm kernel: [ 82.368188] PPP Deflate Compression module registered
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> PPP manager(IP Config Get) reply received.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) complete.
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: secondaries -> activated (reason 'none') [90 100 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTED_GLOBAL
    Last edited by Shocker (2015-05-07 19:18:43)

    This week, after update, modem works again.
    However, there's a new bug in the kernel, which was not there before:
    kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    but the modem works and connects to the network.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> Auto-activating connection 'Orange'.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTING
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect state (1/8): Unlock check
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (2/8): Wait to get fully initialized
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (locked -> initializing)
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ ModemManager[338]: Invalid mobile equipment error code: 50
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (initializing -> disabled)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (3/8): Enable
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <warn> (ttyUSB1): port attributes not fully set
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'locked' --> 'disabled' (reason: unknown)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <warn> (cdc-wdm0) failed to enable modem: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.InProgress: Cannot enable modem: already being enabled
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    may 24 09:32:48 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (8/8): All done
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) starting...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: prepare -> config (reason 'none') [40 50 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) successful.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) started...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: config -> ip-config (reason 'none') [50 70 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Activation (wwp0s20u2i2) Beginning DHCPv4 transaction (timeout in 15 seconds)
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> dhclient started with pid 3624
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): IPv6 configuration disabled
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) complete.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPDISCOVER on wwp0s20u2i2 to 255.255.255.255 port 67 interval 7
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPREQUEST on wwp0s20u2i2 to 255.255.255.255 port 67
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPOFFER from 10.X.X.X
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPACK from 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> address 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> plen 30 (255.255.255.252)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> gateway 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> server identifier 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> lease time 518400
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (wwp0s20u2i2): DHCPv4 state changed unknown -> bound
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) started...
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Joining mDNS multicast group on interface wwp0s20u2i2.IPv4 with address 10.X.X.X.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: New relevant interface wwp0s20u2i2.IPv4 for mDNS.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Registering new address record for 10.X.X.X on wwp0s20u2i2.IPv4.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: bound to 10.X.X.X -- renewal in 252436 seconds.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_LOCAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_GLOBAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Policy set 'Orange' (wwp0s20u2i2) as default for IPv4 routing and DNS.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Writing DNS information to /usr/bin/resolvconf
    may 24 09:33:09 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: successful, device activated.

  • Network Manager fails to connect with Sierra Wireless 3G/4G modem

    Hi,
    I have three Asus Laptops running with Arch (Asus N56VZ, Asus F3JC, Asus UL80VS). All laptops work with Cinnamon Desktop. Everything works fine except 3G Modem in Network Manager. I have two USB modems: Sierra Wireless AirCard 310U and Sierra Wireless AirCard 320U.
    Modems had worked fine in end of year 2012, when NetworkManager version was 0.9.6.4 and ModemManager 0.6.0.0. After update (NM >0.8.X.X, MM >0.7.X. - when the ModemManager.service appeared) until now, I can't connect to the internet on all Asus laptops. Since 2013 I have to use wvdial, because in wvdial modems works fine. It is Arch problem, because in Linux Mint 15 I can connect with NetworkManager.
    Sierra AirCard 310U - When I'm connecting to the internet, modem reboots itself.
    Sierra AirCard 320U - When I'm connecting to the internet, Network Manager can't obtain DHCP address.
    I would be grateful for any help.
    Sierra Wireless AirCard 310U (USB 3G Modem) log:
    aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) starting connection 'Orange PL'
    aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled...
    aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started...
    aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete.
    aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Simple connect started...
    aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Simple connect state (3/8): Enable
    aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
    aug 22 13:41:35 AsusN56VZ ModemManager[308]: <warn> (ttyUSB2): port attributes not fully set
    aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '4FB9', Cell ID: '9C65539')
    aug 22 13:41:39 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '260', MNC: '3', Location area code: '4FB9', Cell ID: '9C65539')
    aug 22 13:41:40 AsusN56VZ kernel: usb 3-2: USB disconnect, device number 3
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ ModemManager[308]: mm_serial_port_close: assertion `priv->open_count > 0' failed
    aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (4/8): Wait to get fully enabled
    aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (5/8): Register
    aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> (tty/ttyUSB2): released by modem /sys/devices/pci0000:00/0000:00:14.0/usb3/3-2
    aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (6/8): Bearer
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB0: Sierra USB modem converter now disconnected from ttyUSB0
    aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.0: device disconnected
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: Sierra USB modem converter now disconnected from ttyUSB1
    aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.1: device disconnected
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: Sierra USB modem converter now disconnected from ttyUSB2
    aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.3: device disconnected
    aug 22 13:41:40 AsusN56VZ kernel: sierra_net 3-2:1.7 wwp0s20u2i7: unregister 'sierra_net' usb-0000:00:14.0-2, Sierra Wireless USB-to-WWAN Modem
    aug 22 13:41:40 AsusN56VZ kernel: ModemManager[308]: segfault at 28 ip 0000000000433350 sp 00007ffff409e088 error 4 in ModemManager[400000+e0000]
    aug 22 13:41:40 AsusN56VZ systemd[1]: ModemManager.service: main process exited, code=dumped, status=11/SEGV
    aug 22 13:41:40 AsusN56VZ systemd[1]: Unit ModemManager.service entered failed state.
    aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> ModemManager disappeared from bus
    aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): device state change: prepare -> unmanaged (reason 'removed') [40 10 36]
    aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): deactivating device (reason 'removed') [36]
    aug 22 13:41:40 AsusN56VZ laptop-mode[2414]: Laptop mode
    aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): cleaning up...
    aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): taking down device.
    aug 22 13:41:40 AsusN56VZ laptop-mode[2415]: enabled, not active
    aug 22 13:41:40 AsusN56VZ systemd-coredump[2336]: Process 308 (ModemManager) dumped core.
    aug 22 13:41:40 AsusN56VZ systemd[1]: Starting Modem Manager...
    aug 22 13:41:40 AsusN56VZ systemd[1]: ModemManager.service holdoff time over, scheduling restart.
    aug 22 13:41:40 AsusN56VZ systemd[1]: Stopping Modem Manager...
    aug 22 13:41:40 AsusN56VZ systemd[1]: Starting Modem Manager...
    aug 22 13:41:43 AsusN56VZ kernel: sierra_net 3-2:1.7 (unregistered net_device): usb_control_msg failed, status -19
    Sierra Wireless AirCard 320U (3G/4G Modem) log:
    aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) starting connection 'Orange PL'
    aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) scheduled...
    aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) started...
    aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) complete.
    aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Simple connect started...
    aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Simple connect state (3/8): Enable
    aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (disabled -> enabling)
    aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
    aug 22 13:48:02 AsusN56VZ ModemManager[314]: <warn> (ttyUSB3): port attributes not fully set
    aug 22 13:48:02 AsusN56VZ ModemManager[314]: <warn> (ttyUSB4): port attributes not fully set
    aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (unknown -> registering)
    aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (registering -> home)
    aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '4FB9', Cell ID: '9C65539')
    aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: '260', MNC: '3', Location area code: '4FB9', Cell ID: '9C65539')
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (enabling -> registered)
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (4/8): Wait to get fully enabled
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (5/8): Register
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (6/8): Bearer
    aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> WWAN now enabled by management service
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (7/8): Connect
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (registered -> connecting)
    aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (40)
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: access technology changed (unknown -> hsdpa, hsupa)
    aug 22 13:48:09 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connecting -> connected)
    aug 22 13:48:09 AsusN56VZ ModemManager[314]: <info> Simple connect state (8/8): All done
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) scheduled...
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) starting...
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: prepare -> config (reason 'none') [40 50 0]
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): bringing up device.
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) successful.
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) scheduled.
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) complete.
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) started...
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: config -> ip-config (reason 'none') [50 70 0]
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (wwp0s20u2i7) Beginning DHCPv4 transaction (timeout in 45 seconds)
    aug 22 13:48:09 AsusN56VZ kernel: IPv6: ADDRCONF(NETDEV_UP): wwp0s20u2i7: link is not ready
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> dhclient started with pid 2351
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) complete.
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) started...
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: Internet Systems Consortium DHCP Client 4.2.5-P1
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: Copyright 2004-2013 Internet Systems Consortium.
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: All rights reserved.
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: For info, please visit https://www.isc.org/software/dhcp/
    aug 22 13:48:09 AsusN56VZ dhclient[2351]:
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (wwp0s20u2i7): DHCPv4 state changed nbi -> preinit
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: Listening on LPF/wwp0s20u2i7/8e:1d:fe:e0:02:07
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: Sending on LPF/wwp0s20u2i7/8e:1d:fe:e0:02:07
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: Sending on Socket/fallback
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 5
    aug 22 13:48:14 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 5
    aug 22 13:48:19 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
    aug 22 13:48:26 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
    aug 22 13:48:33 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
    aug 22 13:48:36 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (40)
    aug 22 13:48:40 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 10
    aug 22 13:48:50 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 17
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <warn> (wwp0s20u2i7): DHCPv4 request timed out.
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (wwp0s20u2i7): canceled DHCP transaction, DHCP client pid 2351
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) started...
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <warn> Activation (ttyUSB3) failed for connection 'Orange PL'
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) complete.
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: failed -> disconnected (reason 'none') [120 30 0]
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): deactivating device (reason 'none') [0]
    aug 22 13:48:54 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connected -> disconnecting)
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'connected' --> 'disconnecting' (reason: user-requested)
    Last edited by Shocker (2013-09-14 20:08:08)

    Shocker wrote:I don't think it's kernel problem, because Linux Mint 15 have kernel 3.8 and there is everything fine. Maybe systemd (Fedora & Arch have systemd, but Mint sysvinit..), maybe version of dhcpcd, I have no idea...
    To test, I downgraded my kernel
    ~ ᐅ uname -r
    3.9.5-301.fc19.x86_64.debug
    And now I see in messages
    Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) starting connection 'Telstra'
    Sep 15 09:46:17 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) scheduled...
    Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) started...
    Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) complete.
    Sep 15 09:46:17 localhost modem-manager[757]: <info> (ttyUSB2) opening serial port...
    Sep 15 09:46:17 localhost modem-manager[757]: <warn> (ttyUSB2): port attributes not fully set
    Sep 15 09:46:17 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling)
    Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <info> (ttyUSB2) opening serial port...
    Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <warn> (ttyUSB2): port attributes not fully set
    Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling)
    Sep 15 09:46:18 localhost dbus-daemon[618]: modem-manager[757]: <info> (ttyUSB2): using PDU mode for SMS
    Sep 15 09:46:18 localhost modem-manager[757]: <info> (ttyUSB2): using PDU mode for SMS
    Sep 15 09:46:18 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling -> enabled)
    Sep 15 09:46:18 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling -> enabled)
    Sep 15 09:46:18 localhost NetworkManager[724]: <info> WWAN now enabled by management service
    Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabled -> registered)
    Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabled -> registered)
    Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
    Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
    Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> connected)
    Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> connected)
    Sep 15 09:46:19 localhost kernel: [ 5056.773068] IPv6: ADDRCONF(NETDEV_UP): wwp0s29u1u1i7: link is not ready
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) scheduled...
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) starting...
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: prepare -> config (reason 'none') [40 50 0]
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): bringing up device.
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) successful.
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) complete.
    Sep 15 09:46:19 localhost avahi-daemon[607]: Registering new address record for fe80::c0c3:a2ff:fe4a:207 on wwp0s29u1u1i7.*.
    Sep 15 09:46:19 localhost kernel: [ 5056.876750] IPv6: ADDRCONF(NETDEV_CHANGE): wwp0s29u1u1i7: link becomes ready
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) scheduled.
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) started...
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: config -> ip-config (reason 'none') [50 70 0]
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Beginning DHCPv4 transaction (timeout in 45 seconds)
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> dhclient started with pid 10376
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) complete.
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Sep 15 09:46:19 localhost dhclient[10376]: Internet Systems Consortium DHCP Client 4.2.5
    Sep 15 09:46:19 localhost dhclient[10376]: Copyright 2004-2013 Internet Systems Consortium.
    Sep 15 09:46:19 localhost dhclient[10376]: All rights reserved.
    Sep 15 09:46:19 localhost dhclient[10376]: For info, please visit https://www.isc.org/software/dhcp/
    Sep 15 09:46:19 localhost dhclient[10376]:
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed nbi -> preinit
    Sep 15 09:46:19 localhost dhclient[10376]: Listening on LPF/wwp0s29u1u1i7/c2:c3:a2:4a:02:07
    Sep 15 09:46:19 localhost dhclient[10376]: Sending on LPF/wwp0s29u1u1i7/c2:c3:a2:4a:02:07
    Sep 15 09:46:19 localhost dhclient[10376]: Sending on Socket/fallback
    Sep 15 09:46:19 localhost dhclient[10376]: DHCPREQUEST on wwp0s29u1u1i7 to 255.255.255.255 port 67 (xid=0x6e8c90b2)
    Sep 15 09:46:19 localhost dhclient[10376]: DHCPNAK from 10.102.67.253 (xid=0x6e8c90b2)
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed preinit -> expire
    Sep 15 09:46:19 localhost dhclient[10376]: DHCPDISCOVER on wwp0s29u1u1i7 to 255.255.255.255 port 67 interval 6 (xid=0xae2cec8)
    Sep 15 09:46:19 localhost dhclient[10376]: DHCPREQUEST on wwp0s29u1u1i7 to 255.255.255.255 port 67 (xid=0xae2cec8)
    Sep 15 09:46:19 localhost dhclient[10376]: DHCPOFFER from 10.102.67.253
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed expire -> preinit
    Sep 15 09:46:19 localhost dhclient[10376]: DHCPACK from 10.102.67.253 (xid=0xae2cec8)
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed preinit -> bound
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> address 10.102.67.12
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> prefix 24 (255.255.255.0)
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> gateway 10.102.67.12
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> nameserver '10.4.81.103'
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> nameserver '10.4.182.20'
    Sep 15 09:46:19 localhost NetworkManager[724]: nm_ip4_config_add_wins: assertion `wins > 0' failed
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> wins '0.0.0.0'
    Sep 15 09:46:19 localhost NetworkManager[724]: nm_ip4_config_add_wins: assertion `wins > 0' failed
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> wins '0.0.0.0'
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Commit) started...
    Sep 15 09:46:19 localhost avahi-daemon[607]: Joining mDNS multicast group on interface wwp0s29u1u1i7.IPv4 with address 10.102.67.12.
    Sep 15 09:46:19 localhost avahi-daemon[607]: New relevant interface wwp0s29u1u1i7.IPv4 for mDNS.
    Sep 15 09:46:19 localhost avahi-daemon[607]: Registering new address record for 10.102.67.12 on wwp0s29u1u1i7.IPv4.
    Sep 15 09:46:19 localhost dhclient[10376]: bound to 10.102.67.12 -- renewal in 97473 seconds.
    Sep 15 09:46:20 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    Sep 15 09:46:20 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Commit) complete.
    Sep 15 09:46:20 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: secondaries -> activated (reason 'none') [90 100 0]
    Sep 15 09:46:20 localhost NetworkManager[724]: <info> Policy set 'Telstra' (wwp0s29u1u1i7) as default for IPv4 routing and DNS.
    Sep 15 09:46:20 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) successful, device activated.
    I'm going to ask on #fedora and see how i can best diagnose what's going on. At least I now have it working, albeit on an older kernel.
    Last edited by qnm (2013-09-14 23:48:05)

  • Facetime fails to connect

    I am trying to FaceTime with my daughter in Sweden. I am using OS 10.9.4 on a MacBook Pro with Facetime 3.0. She is using an iPad mini with the current software. The query initally goes through and says "connecting" then fails to connect. I have checked the firewall settings in my Airport Extreme and the modem and they are correct, and have tried with the MacBook's firewall on or off without success. What am I missing?
    Randy Black

    Failure to connect is most commonly due to not being fully updated per http://support.apple.com/kb/TS5419 but that does not sound like your case.  Have you tried connecting by using the email address of the recipient instead of a telephone number?

  • Wifi scans but fails to connect on Thinkpad W520

    Running Network Manager on a Lenovo Thinkpad W520 and able to scan but unable to connect to wifi.  Wifi works fine in dualboot on Windows, and ethernet works fine in both.
    $ lspci -vv
    03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)
    Subsystem: Intel Corporation Centrino Ultimate-N 6300 3x3 AGN
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 64 bytes
    Interrupt: pin A routed to IRQ 35
    Region 0: Memory at d5300000 (64-bit, non-prefetchable) [size=8K]
    Capabilities: <access denied>
    Kernel driver in use: iwlwifi
    $ sudo systemctl status NetworkManager-wait-online.service
    ● NetworkManager-wait-online.service - Network Manager Wait Online
    Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Sun 2014-12-21 22:58:55 EST; 12min ago
    Main PID: 500 (code=exited, status=1/FAILURE)
    Dec 21 22:58:55 Defiant systemd[1]: NetworkManager-wait-online.service: main process exited, code=exited, status=1/FAILURE
    Dec 21 22:58:55 Defiant systemd[1]: Failed to start Network Manager Wait Online.
    Dec 21 22:58:55 Defiant systemd[1]: Unit NetworkManager-wait-online.service entered failed state.
    Dec 21 22:58:55 Defiant systemd[1]: NetworkManager-wait-online.service failed.
    $ sudo systemctl status NetworkManager-dispatcher.service
    ● NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
    Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled; vendor preset: disabled)
    Active: inactive (dead)
    $ sudo systemctl status NetworkManager.service
    ● NetworkManager.service - Network Manager
    Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Active: active (running) since Sun 2014-12-21 22:58:23 EST; 13min ago
    Main PID: 341 (NetworkManager)
    CGroup: /system.slice/NetworkManager.service
    └─341 /usr/bin/NetworkManager --no-daemon
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> (wlp3s0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> Disabling autoconnect for connection 'Bifröst'.
    Dec 21 23:10:12 Defiant NetworkManager[341]: <warn> Activation (wlp3s0) failed for connection 'Bifröst'
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> (wlp3s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> (wlp3s0): deactivating device (reason 'none') [0]
    Dec 21 23:10:12 Defiant NetworkManager[341]: <warn> Connection disconnected (reason -3)
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> (wlp3s0): supplicant interface state: completed -> disconnected
    Dec 21 23:10:15 Defiant NetworkManager[341]: <warn> Could not get scan request result: Scan request rejected
    Additionally, after stopping NetworkManager and trying wifi-menu, it scans correctly but fails to connect, never even prompting for a passphrase.
    So I tried wpa_supplicant on its own:
    $ sudo wpa_supplicant -B -i wlp3s0 -c <(wpa_passphrase "Bifr\xc3\xb6st" "mypassword")
    Successfully initialized wpa_supplicant
    wlp3s0: failed to initialize driver interface
    For good measure:
    $ rfkill list
    0: tpacpi_bluetooth_sw: Bluetooth
    Soft blocked: no
    Hard blocked: no
    1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
    2: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
    $ ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether f0:de:f1:62:13:b8 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.11/24 brd 10.0.0.255 scope global enp0s25
    valid_lft forever preferred_lft forever
    3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:24:d7:c6:ab:48 brd ff:ff:ff:ff:ff:ff
    I'm at a loss. and I've googled my little heart out.  Any help would be appreciated.

    Welcome to the forums - and thanks for a great initial post, all the needed information seems to be here.
    Specifically, the following error from wpa_supplicant will most likely be best to dig into:
    wlp3s0: failed to initialize driver interface
    I see several results of this error in a google search, but none of them quickly translated into solutions yet.  To get some more information on it, could you run the same wpa_supplicant command, but with the verbose debugging flag "-dd" and post the ouput here?
    I don't have a intel wireless card, so I don't know what the diagnostic signs are for the problem addressed in the wiki, but you may want to try the modprobe options shown in this section of the wiki.
    EDIT: there is a similar but unresolved thread on these forums here which points to using the -D flag for wpa_supplicant to specify other drivers.  I was thinking this too upon my first reading, but I don't fully understand what these are so I was reluctant to suggest it.  It certainly can't hurt anything to use the command in the wiki to see which drivers are available, then try each one.
    EDIT 2: and this thread seems to indicate that the -D flag driver specification is the right solution.  So start here with the -D flag and only if that fails follow up with my initial debugging suggestions.
    Last edited by Trilby (2014-12-22 12:52:13)

  • NetworkManager can't finish establishing connection

    Every time I boot Arch, the tray icon for Network Manager in GNOME 3 is shown to be still trying to connect to my wired connection to my router, and journalctl shows that it appears to be stalling when trying to establish an IPv6 connection. Currently my ISP doesn't have automatic support for IPv6, and I have to use an 6rd tunnel for IPv6 connections. Additionally, if I try to add another connection to the system after boot (like an LTE radio tether to my phone), modify any connection, or disconnect from my wired connection and then reconnect, the system will be unable to access anything over the network (Except, curiously, websites previously visited during my Firefox session before changing the connections. Not just caches of those sites, either.) When the system is unable to access anything, trying to ping any address or domain gives a "network is unreachable" error.
    journalctl -b --no-pager | grep NetworkManager
    Jul 20 00:44:05 desktop NetworkManager[390]: <info> NetworkManager (version 0.9.8.10) is starting...
    Jul 20 00:44:05 desktop NetworkManager[390]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
    Jul 20 00:44:05 desktop NetworkManager[390]: <info> WEXT support is enabled
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
    Jul 20 00:44:06 desktop NetworkManager[390]: keyfile: parsing Profile 1 ...
    Jul 20 00:44:06 desktop NetworkManager[390]: keyfile: read connection 'Profile 1'
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> monitoring kernel firmware directory '/lib/firmware'.
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> WiFi enabled by radio killswitch; enabled by state file
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> WWAN enabled by radio killswitch; enabled by state file
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> WiMAX enabled by radio killswitch; enabled by state file
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> Networking is enabled by state file
    Jul 20 00:44:06 desktop NetworkManager[390]: <warn> failed to allocate link cache: (-26) Protocol mismatch
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> (enp4s0): carrier is OFF
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> (enp4s0): new Ethernet device (driver: 'tg3' ifindex: 2)
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> (enp4s0): exported as /org/freedesktop/NetworkManager/Devices/0
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> (enp4s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> (enp4s0): preparing device.
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> (enp4s0): deactivating device (reason 'managed') [2]
    Jul 20 00:44:06 desktop NetworkManager[390]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    Jul 20 00:44:06 desktop NetworkManager[390]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    Jul 20 00:44:06 desktop NetworkManager[390]: <warn> Couldn't acquire object manager proxy: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> (enp4s0): carrier now ON (device state 20)
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> (enp4s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Auto-activating connection 'Profile 1'.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) starting connection 'Profile 1'
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> (enp4s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> NetworkManager state is now CONNECTING
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 1 of 5 (Device Prepare) scheduled...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 1 of 5 (Device Prepare) started...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 2 of 5 (Device Configure) scheduled...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 1 of 5 (Device Prepare) complete.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 2 of 5 (Device Configure) starting...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> (enp4s0): device state change: prepare -> config (reason 'none') [40 50 0]
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 2 of 5 (Device Configure) successful.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 3 of 5 (IP Configure Start) scheduled.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 2 of 5 (Device Configure) complete.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 3 of 5 (IP Configure Start) started...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> (enp4s0): device state change: config -> ip-config (reason 'none') [50 70 0]
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> dhcpcd started with pid 1559
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Beginning IP6 addrconf.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 3 of 5 (IP Configure Start) complete.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> (enp4s0): DHCPv4 client pid 1559 exited with status 0
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 4 of 5 (IPv4 Configure Timeout) started...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
    Jul 20 00:44:11 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router...
    Jul 20 00:44:11 desktop NetworkManager[390]: <info> Activation (enp4s0) Beginning DHCPv6 transaction (timeout in 45 seconds)
    Jul 20 00:44:11 desktop NetworkManager[390]: <warn> the dhcpcd backend does not support IPv6.
    Jul 20 00:48:35 desktop NetworkManager[390]: <warn> error monitoring device for netlink events: No buffer space available
    desktop :: ~ % journalctl -b --no-pager | grep NetworkManager
    Jul 20 00:44:05 desktop NetworkManager[390]: <info> NetworkManager (version 0.9.8.10) is starting...
    Jul 20 00:44:05 desktop NetworkManager[390]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
    Jul 20 00:44:05 desktop NetworkManager[390]: <info> WEXT support is enabled
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
    Jul 20 00:44:06 desktop NetworkManager[390]: keyfile: parsing Profile 1 ...
    Jul 20 00:44:06 desktop NetworkManager[390]: keyfile: read connection 'Profile 1'
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> monitoring kernel firmware directory '/lib/firmware'.
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> WiFi enabled by radio killswitch; enabled by state file
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> WWAN enabled by radio killswitch; enabled by state file
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> WiMAX enabled by radio killswitch; enabled by state file
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> Networking is enabled by state file
    Jul 20 00:44:06 desktop NetworkManager[390]: <warn> failed to allocate link cache: (-26) Protocol mismatch
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> (enp4s0): carrier is OFF
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> (enp4s0): new Ethernet device (driver: 'tg3' ifindex: 2)
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> (enp4s0): exported as /org/freedesktop/NetworkManager/Devices/0
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> (enp4s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> (enp4s0): preparing device.
    Jul 20 00:44:06 desktop NetworkManager[390]: <info> (enp4s0): deactivating device (reason 'managed') [2]
    Jul 20 00:44:06 desktop NetworkManager[390]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    Jul 20 00:44:06 desktop NetworkManager[390]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    Jul 20 00:44:06 desktop NetworkManager[390]: <warn> Couldn't acquire object manager proxy: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> (enp4s0): carrier now ON (device state 20)
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> (enp4s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Auto-activating connection 'Profile 1'.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) starting connection 'Profile 1'
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> (enp4s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> NetworkManager state is now CONNECTING
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 1 of 5 (Device Prepare) scheduled...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 1 of 5 (Device Prepare) started...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 2 of 5 (Device Configure) scheduled...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 1 of 5 (Device Prepare) complete.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 2 of 5 (Device Configure) starting...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> (enp4s0): device state change: prepare -> config (reason 'none') [40 50 0]
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 2 of 5 (Device Configure) successful.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 3 of 5 (IP Configure Start) scheduled.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 2 of 5 (Device Configure) complete.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 3 of 5 (IP Configure Start) started...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> (enp4s0): device state change: config -> ip-config (reason 'none') [50 70 0]
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> dhcpcd started with pid 1559
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Beginning IP6 addrconf.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 3 of 5 (IP Configure Start) complete.
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> (enp4s0): DHCPv4 client pid 1559 exited with status 0
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 4 of 5 (IPv4 Configure Timeout) started...
    Jul 20 00:44:09 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
    Jul 20 00:44:11 desktop NetworkManager[390]: <info> Activation (enp4s0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router...
    Jul 20 00:44:11 desktop NetworkManager[390]: <info> Activation (enp4s0) Beginning DHCPv6 transaction (timeout in 45 seconds)
    Jul 20 00:44:11 desktop NetworkManager[390]: <warn> the dhcpcd backend does not support IPv6.
    Jul 20 00:48:35 desktop NetworkManager[390]: <warn> error monitoring device for netlink events: No buffer space available
    Last edited by ButchDeLoria (2014-07-20 05:03:19)

    fungle wrote:Try disabling the IPv6 settings. Go to Edit Connections, select the connection you want to edit, select the IPv6 Settings tab, select Ignore from the Method drop-down menu.
    Whoops, I forgot I still had this open. I wasn't able to actually fix the issue, so I just disabled the IPv6 tunnel on my router.

  • Linksys E1200 fails to connect to Frontier FIOS internet at setup

    I am trying to set up my E1200 router to Frontier FIOS internet. I went thru the setup and it failed to connect to the internet. What settings do I need? Frontier says that it should find the connection automatically.

    First of all connect the modem directly to the computer and then let me know the IP address that you are getting from the router? To check the IP address that you are getting from the Router...
    You can check the IP address in the following manner:
    # Click on Start -> All Programs -> Accessories -> Command Prompt.
    # A black pop up box should come up, type: "ipconfig /all" …
    There check the IP address and Default Gateway under LAN….
    Here is the link for setting up the router with the DSL connection: http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&docid=20ee1457387f40178cd5f41d4b585db4_3687.xml&pid=80&r...

  • IPhone 5 has failed to connect to my home Wi-Fi

    my iPhone 5 has failed to connect to my home Wi-Fi and its seems am the only one experiencing this problem at home because my housemates iPhone 4 and Blackberrys get the wifi nice and clear. yet i have connected to this wifi with iphone5 before.

    Try resetting your wireless router and modem.
    Disconnect the wireless router from the power source followed by disconnecting the modem from the power source. Wait 5 minutes followed by reconnecting the modem to the power source and allowing the modem to completely reset before re-connecting the wireless router to the power source and allowing the router to completely reset with the modem.

  • Failed to connect Error - Need Help, Please

    I installed , created the simple "Hello" program and it ran fine on the simulator.
    Then, I click the run OTA and now I'm in deep yogurt!
    I get the message:
    *** Error ***
    Failed to connect to device 0!
    Reason:
    Emulator 0 terminated while waiting for it to register!
    BUILD SUCCESSFUL (total time: 4 seconds)
    I just want to restore things to what they were before I selected Run OTA. I've been reading for the past 3 hours and haven't found out to restore. I even deleted and re-installed but, still get the same meassge (probably some saved java pref file...). Anyway, HOW TO RESTORE to a virgin setup????
    Thanks

    ... I read somewhere I need to reboot - I did and it took care of it.

  • Remote app on ipod fails to connect to itunes 10

    After upgrading to iTunes 10, my remote app on the ipod touch 4G fails to connect. I've reauthorized, which times out most times, but eventually when it works, it only continues to connect to iTunes until I close and restart the program. I've disabled all firewalls and still have the issue. iTunes 10/iPod Touch 4G/iOS 4.1/ancient remote.app do not play well together.
    Anyone else unable to get the remote app working reliably with this combination?

    Hello all,
    I would like to get more details from people who are still having trouble getting Remote 2.0.1 to connect. If you are unable to connect, please email me <[email protected]> with the following information:
    - A detailed description of the specific issue you are seeing.
    - What OS is on the host computer? (the one with iTunes on it)
    - What OS is on the affected iOS device(s)?
    - A description of your network topology. Please be as detailed as you can, including hardware and firmware versions, if possible. Also please explain how everything is connected.
    - Is the base station running default settings, or do you have any non-standard settings enabled? If so, please elaborate.
    - Do you have the built-in firewall enabled on the host computer?
    - Do you have any other firewall or Internet protection (anti-virus, etc) installed on the host computer?
    - Were you able to connect with versions of Remote prior to 2.0?
    - If you have multiple computers, can you get Remote to connect to any of them?
    - Does Home Sharing work between computers on your network?
    - Do you see any messages in Console (in Applications/Utilities) on the host computer that seem to coincide with the connection failures?
    Thanks,
    Roy
    <[email protected]>

  • My iphone 5 won't make a call when i fail to connect to the internet via 3g

    My iphone 5 won't call when i fail to connect to the internet via 3g.
    At work i dont have wifi i have 3g, if i launch say the sky go app,or the iplayer, sometimes they work and everything is fine...sometimes they wont load as 3g for whatever reason cant get a connection at that particular time........ if i then try and make a call the call will fail. I've experimented 25 + times and this is definately the cause.
    (note: when the 3g connection does work, the phone has absolutely no problem calling people)
    Anyone had this problem?
    Even better has anyone got a solution?
    Thanks,
    Nick.

    Are you sure that the carrier's signal is strong where you are having this problem? Certain building structures and locations have poor cellular signal strength and this often results in the "No Service" indication. Are other users able to get service in the same locations where you have problems?

  • On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

    I have a new install of Windows 2012.  I have two physical servers.  One is a W2012 std Domain Controller ("DC").  The Second is configured as W2012 HyperV  ("HV").  Under HV I have
    two VMs.  One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS").  All systems are behind a firewall appliance.  Exchange is working via Outlook and OWA internally and externally.  The self
    created SSL must be installed manually on external machines since it comes up as an untrusted certificate.  Once installed remote outlook works and OWA works.  I have configured the terminal server and I am able
    to login remotely as various users under my "TS group".  The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
    on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
    for alias@ domain, then fails the logging on to the mail server)  The error reads:  "Outlook cannot log on.  Verify you are connected to the network and are using the proper server and mailbox name.  The
    connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC.  I have
    tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command.  I have also tried to use the guid via "Get-Mailbox
    ALIAS | fl name, exchangeguid.  Keep in mind all desktop users on the network are connecting to Outlook without issue.
    I would appreciate any thoughts on solving this issue.

    Hi,
    According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
    Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
    open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
    Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
    autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
    Regards,
    Winnie Liang
    TechNet Community Support

  • My new i phone 5 wont sync with my laptop, keeps saying failed to connect to sync services. any help?

    I just purchased a new i phone 5. when i go to connect with my laptop it says 'failed to connect to sync services, try again later' it shows my phone, and i can see my app screens, however it wont let me sync, back up or make changes. this is my first apple product, any help would be greatly appreciated.

    Hello there, load dogg.
    The following Knowledge Base article provides some in-depth steps to help troubleshoot the issue you are descibing:
    iTunes for Windows: "Unable to load data class" or "Unable to load provider data" sync services alert
    http://support.apple.com/kb/ts2690
    Thanks for reaching out to Apple Support Communities for answers to your question.
    Cheers,
    Pedro D.

  • OBIEE 11g agents are failed to connect to Essbase

    OBIEE 11g agents are failed to connect to Essbase. We are using :USER & :PASSWORD (SSO) in connection pool setting to connect to Essbase.
    User account exists in both OBIEE and Essbase. OBIEE dashboards which are based on Essbase are working fine. Essbase variables in RPD are upto date.
    Only agents are failing and error says invalid credentials, but dashboard pages are running without any issue.
    OBIEE: 11.1.1.5 (BP4)
    Essbase: 11.1.2.1
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 96002] Essbase Error: Login fails due to invalid login credentials (HY000)
    Essbase and OBIEE services are up and running.
    Any help will be appreciated.

    We finally implemented CSS Token option and ended up with this error. We are unable to connect to essbase with CSS Token option.
    We followed the Oracle document to implement this.
    [nQSError: 43119] Query Failed: EPMCSS-00301: Failed to authenticate user. Invalid credentials. Enter valid credentials. (HY000)
    We did update this property:
    JAVA_PROPERTIES="-Dplatform.home=${WL_HOME} -Dwls.home=${WLS_HOME} -Dweblogic.home=${WLS_HOME} -Didstore.identityAttribute=objectguid"
    Any help will be appreciated!

  • Fingerprint reader not working in IE and saying failed to connect to sensor

    Hi all,
    I bought a Qosmio x500 10t a couple of months back. For the first couple of weeks i had no probs using the fingerprint reader to log in to windows and to log in to websites in Internet exploer.
    All of a sudden it would not work on any website stored. The green banner showed accross the top of site and asked to swipe finger but nothing happened when I swiped. I rebooted and it worked again but not for long before failing. This time a reboot didnt work so i deleted my finger prints and websites and started from scratch. That worked for a couple of attempts before probs started again. And on trying to get into Fingerprint utility it says failure to connect to sensor. So, I did a system restore. It worked for a couple of times again and then same probs. So I found the updated utility software, uninstalled the old and put on the new. Same again, worked for a couple of times then failed.
    I could not find anything stuck in the registry but to be on the safe side i did a full system clean back to factory setup using backup discs. Hey presto i thought it had worked. Everything going ok for first 24hrs and then same problems start to occur. Only this time it is also prompting me to enroll fingerprints even though i already have. And when i try to get into the utilioty it says failed to read sensor again.
    The fingerprint log on to windows always works as long as i dont close the fingerprint utility down before shutting down. If i do exit the utilty i cant reopen it as it just says failed to connect to sensor. And then i have to unistall and reinstall the utility software. Aty the moment it occasionally works on websites stored but most of the time it doesnt do anything.
    Please help. Do I need to send laptop back to Toshiba??

    Hi,
    *I got a solution* for the problem that the fingerprint sensor "suddenly" does not work any more.
    When starting the Toshiba Fingerprint Utility, it says "failed to connect to fingerprint sensor".
    Is it possible that just before it stopped working there was a new firewall installed, or firewall settings had been changed?
    *In my case, the problem was solved by changing my firewall settings* (Windows 7 Firewall Control) to ALLOW all traffic for
    the Authentec Fingerprint Sensor Service (AFSS). It is the file "AtService.exe" in C:\Program files
    The reason is simple:
    The Toshiba Fingerprint utility communicates with the fingerprint sensor service via TCP/IP.
    Therefore, any firewall that blocks traffic on the local computer will block the communication.
    *After changing my firewall settings, fingerprint sensor works* on my R700 flawlessly now.

Maybe you are looking for

  • How to capture the data from JOBLOG

    Hi Experts, When we execute 'F110' transaction code it creates a joblog. I need to capture the joblog data through 'Z' program and it should display the joblog data in SO01 transaction code. The above process goes through when we execute 'F110' Trans

  • How do I configure a VPN Site and Subnets in Lync when clients have /32 Addresses?

    Hello, I've found a few people asking this question out in the "interwebs" but no one seems to quite answer their question (Those poor souls). In most occasions that I've seen, my customers have configured their VPN networks with a /24 (255.255.255.0

  • A-z order of songs help!

    when i put my ipod on the pc the songs on it are in alphabetical order, but when i play them on the cd player they play randomly. i want them to play in a-z order on the cd player! whats the solution please? thanx

  • How to display previous settlement rules (CJ70)

    Hi, Is there any transaction code to view the list of settlement rule from CJ70. We settle from 1 WBS - 1 AUC - many Fixed Assets After I made final settlement rules in CJ70 and run CJ88, the lines of settled items are gone. How to display the list o

  • Date on Desktop

    I find it a real pain that after buying Tiger I still can't have the date displayed on the desktop like I had on my first MAC Classic. I have searched all the helps and spent hours trying to find a way to trade the "time" in the upper right hand corn