Network Manager Can't Connect Wirelessly

Hi everyone,
I'm trying to migrate from Connman to Network Manager for my network needs (as well as from e17 to xmonad) and I'm seeing some strange behavior. I can get the network manager applet running, but it won't connect to any wireless networks. I see a bunch of networks floating around in the connections list, but if I click on one, nothing happens. Furthermore, if I try to connect by command line, I get the following weirdness
Input:
nmcli con up uuid f767eb89-ccbc-4dbe-bf12-af216ab8f9ff ap A0:21:B7:72:A3:CE
(the uuid is for my wlan0 interface and the ap is the BSSID of my network).
Output:
Active connection state: activating
Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/0
** (process:2012): WARNING **: _nm_object_get_property: Error getting 'State' for /org/freedesktop/NetworkManager/ActiveConnection/0: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
state: unknown
Error: Connection activation failed.
I'm fairly sure that I have my policy kit working correctly. I have dbus and network manager as daemons and I logged in to an xmonad session using GDM, which should do my policy management for me, right?
I think its the wrong error message for a policy kit error anyways.
Any ideas?
Thanks in advance!
Last edited by Yurlungur (2012-04-16 04:29:32)

I switched to wicd, so this isn't an issue anymore, I guess... still not sure what was going wrong, though.

Similar Messages

  • Adding Network Manager tray for connecting Wireless Network (solved)

    I just installed GDM, gnome, gnome-extra packages but I do not see the network applet in the top right corner.
    I also installed 'network-manager-applet' but I still do not see it.
    Currently I have been using wifi-menu everytime and it works fine that way.
    Last edited by jesse930 (2013-07-02 02:05:58)

    Hello! On arch everything is done manually:
    Start the programs:
    # systemctl start NetworkManager
    $ nm-applet
    If you want it to persist use systemctl and other options.
    See https://wiki.archlinux.org/index.php/Ne … orkManager
    Last edited by teateawhy (2013-06-30 18:19:20)

  • 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)

  • I set up time capsule and now can't connect wirelessly

    I got home with my new Apple and Time Capsule last Friday and was unable to connect to the net. I called Cox cable and they came out and got me up and running. The yellow light on the Tine Capsule kept blinking but I was able to connect and thought it was just a glitch.
    Today I added a printer and, after a few headaches, got it up and running. Then I tried to set up the automatic backup process and thought I was OK. Now, however I can't connect wirelessly at all. I keep getting the message "None of your preferred networks are available." I have a neighbor with a wireless network and it sees that, so something is going on. I also am able to connect directly to my modem and get connected. The yellow light is still blinking!
    I have tried re-starting the computer, turning off both the modem and Time Capsule, but nothing works. I am beginning to think I have a defective Time Capsule but the store I got it from is two hours away, so if anyone can offer a suggestion, I would be most grateful.

    I just went through the same deal. I'm not exactly sure how I did it, but I eventually got it to work, and even have Back to My Mac in play. For the next ten minutes, anyway.
    So here's the deal. These are some of the things I did that you might try.
    First, there is a big issue regarding how you presently connect to the internet - DSL modem? Cable modem? A dixie cup and a piece of thread? Time Capsule is both a router and a wireless base station, so whatver you're using now might be performing router duty as well, and screwing things up. I replaced my AT&T 2Wire device (modem, router, and wireless base station in one box) with a DSL modem. Oh, and when I was prompted, I assigned the public IP address for my broadband connection (the one that begins with 70.xxx.xxx.xxx) to the TIme Capsule, instead of having Time Capsule get one of those 192.xxx.x.xxx or 10.x.x.x IP addresses from DHCP.
    The modem has to operate in "bridge mode." Whatever the heck that means.
    Also, in configuring time capsule, I initially used an ethernet cable attached to a computer (in this case, my MacBook Pro). It seemed easier to get it going that way, and once it had managed to connect, it made it easier to get on just using the wireless connection.
    When you're prompted, you want to create a new network, although it might be helpful to take it one step at a time and keep your present network up and running and let Time Capsule join that deploying - initially - just the wireless backup capability.
    Oh, and regarding restarting all the hardware, I did that too. But with Time Capsule, if you're not already doing it, you should not just restart the device, but do a reset. On the back of the device if you look carefully toward the right you will see a little pinhole. Get a paper clip and depress the little button inside that little pinhole until the front light begins to blink rapidly. That resets Time Capsule and was the only way I could get the thing to bite at the beginning.
    So much for Mac's just working. Although once they do . . . .

  • Can't connect wirelessly HP Photosmart C4780 to MacBook Pro OSX 10.8.2 Mountain Lion.

    Hi!
    Didn't know exactly where to direct this question in the Apple Community so I chose Airport.  To everyone, thanks in advance.
    I’m really desperate. I’m a big Apple fan.  I have two Apple MacBook Pro laptops with Mountain Lion software.  I also have an Apple Airport Extreme.  My HP Photosmart C4780 printer was also purchased from Apple.  Anyway, my Internet service is AT&T.  AT&T just upgraded my service with a new modem/router (AT&T U-Verse).  Prior to the conversion, my wireless printer connection was working perfectly.
    Now can’t print wirelessly. For your information, everything is connected via Wi-Fi. The AT&T technician stated that I no longer needed my Apple Airport Extreme, so it was removed.  Naturally, after the tech leaves, we find out the HP printer wirelessly no longer works.  Thinking that removing Airport Extreme may have been the problem, I reconnected it to the AT&T modem/router, however no change.
    This appears to be an HP printer problem.  I went to HP community support with the information below but I have received no solutions outside of buying a new printer.
    “Ran the HP wireless network test report and it states that HP printer can’t find wireless router and to verify that the HP printer network name (SSID) matches the wireless router network name (SSID) exactly.  The Diagnostic Summary in brief:  Wireless On & Working & Security – Pass; Network Name (SSID) Found – Fail. Nothing else under diagnostic summary ran.  Under Configuration Summary:  It shows old SSID name and Mac Hardware Address but no IP Address.
    Next ran the Network Configuration Page and everything is enabled except the 802.11 Wireless.  It shows status – disconnected.  Under general information it states the following: Network status  - Offline; Active Connection Type - None; URL(s) for Embedded Web Server – http://0.0.0.0.”
    To be straightforward, I’m no computer tech so I don’t know what this means or where to find.  The AT&T tech provided me the new SSID Name and a wireless key number but that’s it. Also I uninstalled and reinstalled via USB. The HP message states can’t find router. At this point, I’ve tried everything to reconfigure without success. If I need to make these changes via Airport Extreme Utility 6.0 not easy to find not that I know what I’m doing.
    Most importantly if I ever get wireless working again, do I still need Airport Extreme connection or is the AT&T U-Verse modem/router sufficient?
    Any direction or help is greatly appreciated.  Thank you for listening.

    Thank you for your prompt response.  I'll be honest I'm a retiree and a newbie to all of this stuff. I don't even know how to do a thread. (Embarassing) This is my first ever contact with the Apple Community so I'm slowly trying to figure this out as well. 
    As to your thread request, I'm assuming you want to read my post with HP.  Not knowing how to thread, I've copied it below.
    I have an Apple MacBook Pro laptop with Mountain Lion software.  I also have an Apple Airport Extreme.  My Internet service is AT&T.  AT&T just upgraded my service with a new modem/router (AT&T U-Verse).  Prior to the conversion, my wireless printer connection was working perfectly.
    Now can’t print wirelessly.  For your information, everything is connected via Wi-Fi. The AT&T technician stated that I no longer needed my Apple Airport Extreme, so it was removed.  Naturally, after the tech leaves, we find out the HP printer wirelessly no longer works.  Thinking that removing Airport Extreme may have been the problem, I reconnected it to the AT&T modem/router, however no change.
    Ran the HP wireless network test report and it states that HP printer can’t find wireless router and to verify that the HP printer network name (SSID) matches the wireless router network name (SSID) exactly.  The Diagnostic Summary in brief:  Wireless On & Working & Security – Pass; Network Name (SSID) Found – Fail.  Nothing else under diagnostic summary ran.  Under Configuration Summary:  It shows old SSID name and Mac Hardware Address but no IP Address.
    Next ran the Network Configuration Page and everything is enabled except the 802.11 Wireless.  It shows status – disconnected.  Under general information it states the following: Network status  - Offline; Active Connection Type - None; URL(s) for Embedded Web Server – http://0.0.0.0
    To be honest, don’t know what this means or where to find.  The AT&T tech provided me the new SSID Name and a wireless key number but that’s it. Also I uninstalled and reinstalled via USB. The HP message states can’t find router. At this point, I’ve read your forum and tried everything to reconfigure without success. Any direction or help is greatly appreciated.
    Thanks in advance!
    Re: Can't connect wirelessly HP Photosmart C4780 to MacBook Pro OSX  10.8.2 Mountain Lion.              
    I finally figured it out! (Sorry that I'm replying to my own posts btw, but I want to post the solution for anybody else with the SigmaplusEOL1 problem). If you have the SigmaplusEOL1 as your SSID when you  print the "Wireless Network Test Report", you do NOT need to return it (I know that's hassle for people).  To fix the problem, follow these steps.
    1) Unplug your printer.
    2) Go to your router's IP address (like 192.168.1.1 or whatever it is for your router).
    3) Change the SSID of your wirelss network to "SigmaplusEOL1".
    4) For the Security option for your wireless network select none (so that a password is not required to access your wireless network).
    5) Power your printer back on and reprint "Wireless Network Test Repor". It should say "No problem found..."
    6) The report should also have a the IP Address of the printer (under Configuration Summary at the bottom). Type that IP Address in your browser to get to the printer's settings page.
    7) Click the "Network" Tab at the top.
    8) Under the "Connections" header in the left pane, click "Wireless (802.11).
    9) Click "Start Wizard" at the bottom right.
    10) In the wizard, change the SSID and encryption (wep or wpsk) password to whatever you want your wireless network to be. So probably whatever it started out as before you changed the SSID to SigmaplusEOL1
    11) Click "Finish" at the end. The page will probably try to keep loading but it won't because you changed the network settings of the printer. Just ignore that
    12) Go back to your router's IP address and change the SSID and encryption password to whatever you changed the printer's SSID and password to.
    13). Reprint the Wireless Network Test Report. It should say the SSID is the same as your wireless, and everything is good.
    That's it. You should be good to go now.
    Re: Can't connect wirelessly HP Photosmart C4780 to MacBook Pro OSX  10.8.2 Mountain Lion.              
    Thank you for your prompt response.  This has been a totally frustrating experience.  I’ve spent at least 8 hours trying to fix this.  My HP problems and your initial steps were identical to mine.  I am by no means a tech person and my computer tech knowledge is minimal.  However I followed your steps to the best of my ability.
    I did get the SigmaplusEOL1 message.  I was able to get to Step 6 where the wireless network test report now reads – “HP printer settings do not match your wireless router settings.”  So I guess this is a step in the right direction.  However unfortunately the Configuration summary message for the IP Address reads – “Not Applicable”.  (Note: changing SigmaplusEOL1 to network name knocked out my Internet access.  Had to switch back to regular network name to regain access.)
    I’m at a loss as to what to do next.   Without the IP Address is it possible to move forward?  As I stated earlier, I’m not a tech person.  As to your steps 7, 8 and 9, I can’t find them on my computer or maybe I’m looking in the wrong places.  In System Preferences - Network, I have none of these steps.  If you’re referring to Airport Utility, with the changes in Mountain Lion, these steps are no longer there. If you’re talking about Safari, Firefox or HP, now I’m really lost.
    Finally, I don’t know if you can answer this or not.  If I ever get wireless working, do I still need Airport Extreme or is the AT&T U-Verse modem/router sufficient?
    Again thank you for your time and patience.
    Re: Can't connect wirelessly HP Photosmart C4780 to MacBook Pro OSX  10.8.2 Mountain Lion.                  
    Unfortunately I am unable to offer any further advice as I only followed the instructions listed on the other page.
    Finally, as to having WEP enabled, I don't know.  Don't even know where to look.  The best that I could determine is that my security is WPA/WPA2 Personal.
    I'm truly sorry about all of this.  Thank you for your time and patience.  After reading all of this and you change your mind, I would understand.

  • My X61 can't connect wireless when i use battery!!!

    TYPE NO.:  7673-AN6
    i confused why it can not connect wireless when i use battery?!
    the problem drive me crazy nearly, it means i must take adapter every time
    i help every one can help me!
    cheers,

    Most of the functionality and problems are in the drivers. The hardware tends to be discrete testable functions though these days there is a fair bit of functionality in the hardware. The hardware tends to be implementing better defined protocols where as the to and fro of the higher level protocols tend to be what varies from Access Point to Access Point. The 4965AGN is a fairly recent chip set and the drivers are far from smoothly running.
    The problems can vary from AP to AP so may work at home but not at work etc. Some have reported here that the 4965AGN setup doesn't work with the Cisco 1200 Access Point and I have yet to be able to get it to work under Vista with the equipment at any New York Starbucks. T-mobile do use Cisco equipment but I don't know which models.
    Anything you can do to simplify the situation helps. Maximum power. No security. Disable IPv6 on the connection etc. Just to give a rough idea of the kind of thing that might be wrong here are some of the things listed as known issues or fixed according to the readme of the driver (Originating from Intel) that was released for the 4965AGN on 4/11/08.
    There are several authentication issues with EAP, PEAP and LEAP which will cause it not to authenticate. There are also Vista EAP issues and some things which may resolve with SP1 which was pushed out on update last week. So there are many comnbinations of situations which may not work and it is important to test with different access points. Authentication and security has more issues. Also at the higher speeds such as 54Mb some of the security mechanisms will not be able to keep up. AES is the only mechanism which Intel expects to work at 54Mb.
    http://downloadmirror.intel.com/15806/ENG/relnotes.htm
    There have also been past issues where the cards are silenced for twenty minutes after a failure to authenticate and in many cases the card will not be in a valid state after hibernation. It is noticable that when you phone T-mobile the first thing the tech has you do is completely shut the machine down - not hibernate - and begin afresh.
    Once you have uninstalled and re-installed the drivers and connection manager a few times it is also possible to be having problems with junk left in the registry.
    I don't recommend adding the 4965 drivers directly from the Intel site. I would wait for the one that has come through the Lenovo testing cycle.
    In reality for those who don't want to make maintaining their laptop a serious hobby (Hopefully all of us - Far too much time is wasted on wireless) it is really a matter of rebooting your machine at a given access point. Trying your luck and then shutting it down and going somewhere else if it doesn't work. Use wires when you can. At home if your access point doesn't work check your configuratiions, temporarily remove all security, restore factory settings on the AP, reinstall from scratch and if it still doesn't work replace it with a different brand of Access Point.
    Of course it is intended to just work and for 95+% of situations Wi-Fi does. The 4965AGN is newer so it has its fair share of early life issues to get resolved. Vista also still has issues. If the problem you are seeing is only when you are on batteries you are lucky and LANOgre's instructions may well solve it.
    Message Edited by hiker on 05-19-2008 09:23 PM

  • Can't connect wirelessly to the Internet

    Hi all,
    hope someone can help me with this.
    I'm running OSX 10.3.9, have an ADSL Nation X-Modem and AirPort Express.
    My wireless network is up and running, I have strong signal and AirTunes can connect and play fine wirelessly.
    However, when I try to open Safari and connect to the Internet, it doesn't connect ("Can't find Server.")
    When I plug the X-Modem direct into the Mac with the Ethernet cable, I can connect to the internet fine, so the modem and cable don't seem to be the problem. I've tried running throgh the AirPort Express SetUp Assistant and restarted AirPort and rebooted everything many times. In Network Preferences, it says it's happily connected, has IP address etc, but I still can't connect wirelessly to the Internet?
    Any help greatly appreciated!
    thanks
    Nat

    OK, here it is again
    First you plug the Ethernet cable from your Internet modem into the AE. Then plug it in. The light will go amber. Run the Airport Setup Assistant. Create a new wireless network. Call it what you want. Enter the information about your modem, in the fields just like you do for your Ethernet connection on your PC or Mac. This means DHCP or static IP and subnet..... most if you use DHCP will be filled in for you. Now that you have saved the info and the AE has restarted, look for the network that you named in the available networks. If you have set it up to dish out IP addresses, it will give you one. If you have started out with WEP or WPA the connection process is much more difficult at first.
    I leave it wide open until I can connect to it and then I create MAC access lists. I'll leave all the security stuff to you after you get it working basically.
    Run Airport Admin Utility. It will scan the area for AEs and AEBSs and you can select yours from the list. Click on configure. Here is where you set all the details up on how you want it to work. Here you can configure the details, place your securities etc. Notice that you are accessing it wireless and then you can go through the various Tabs to configure how you want it to operate.
    There is an Internet tab. This will show you how it is configured. It should look the same as your NIC parameters did when you hooked straight to the modem. There are also many more tabs that allow you to configure each area, like do you want it to be the gateway of your network, dish out IP addresses etc. My advice is to let it do that if more than one machine will connect and you don't require defined addresses to get to say a server.
    The two important areas are the Internet and the LAN area. These tell it how to interact with your modem, and the machines trying to connect to it. If the AE doesn't see the modem or can't interact with it, one of the parameters is wrong. Same goes for the LAN side of things.
    Michael

  • Just got a new Airport Express to replace an old ond that dropped off a lot. Works great with various Apple and Androids but Win 8 computer sees the network but can't connect.

    Just got a new Airport Express to replace an old one that dropped off all the time. The new one works with various Apple and Android devices but will not connect to Wen 8 computer. The computer sees the network but can't connect.

    Hello lucky3480;
    I don't know what else to do. I'm thinking of possibly returning the unit and purchasing a wireless internet card to install in the tower. Any help you can provide would be great. Even suggesting a good wireless card at this point
    Well it looks like you're not having any luck at all with this AX set up but please don't give on it just yet, it's a good choice for extending your Network. Your on the right path, just going backwards and in the wrong direction. You'll learn a lot about stuff this way but may lead to other issues.
    Before I continue, let me know if you have returned the AX or still need help. Here's a link to Apple's PDF about [Designing AirPort Networks|http://manuals.info.apple.com/enUS/Designing_AirPort_Networks10.5-Windows.pdf] Click on it to open in Safari but then save it to your desktop. Now open it from your desktop and start reading Chapter 3, page 42.
    Later...
    Buzz

  • Adobe cloud application manager - can not connect to internet

    To ADOBE - The Adode cloud Order no is DSSY006786009DT and is current
    The Adobe cloud application manager - can not connect to internet even though there is internet connection and says it might be time zone error but that is correct  - Sydney Australia
    Question:
         1. Is anybody else having this problem
         2. How do we fix
    I already changed the time zone east coast US - did not change anything
    Could it be a corrupt program - thus requiring to reinstall program Application manager
    I am using Windows 7.
    It has been like it for ten days - It asks to log in everytime I turn computer on
    All programs in Creative Cloud work
    Any suggestions and solution
    Online help and phone help had no solutions other than what I suggested - that is reload application manager
    Thanks for help
    Ian Cleland

    The Creative Cloud File Synching was just offline, should be online now again.
    See top off: http://forums.adobe.com/community/creative_cloud/creative_cloud_connection
    Maybe that was your problem.

  • Can connect to my house network, but can't connect to the Internet (other computers can)

    Hello,
    I'm experiencing a strange problem. Since I started my Mac Pro (cold start) some hours ago, I've lost the hability to connect to the Internet (Safari and Mail say I'm not connected). However, I can connect to 192.168.2.1 (my router) and see its webpage (it says it's connected to the Internet). If I use another computer on the same network, it can also connect to the Internet.
    Weirder, if I go back to my Mac Pro with "no internet" and launch Parallels Desktop, then I can use WinXP to browse the Internet; I'm writing this post on my WinXP virtual machine.
    This leads me to think there's a problem with how my Mac OS handles the networking. I have checked the Console, but the only related string I found is this:
    16.04.13 22:03:25
    kernel
    SIOCPROTOATTACH_IN6: en2 error=17
    As expected, Google doesn't reveal anything about that (and I'm connected with the first ethernet port). I've tried to restart my Mac, but the problem persists (exact same symptoms).
    Could it be a DNS cache issue?
    I don't see, other than a DNS problem, why I can't connect to the Internet with my Mac OS while I can on my virtual machines. If it was a driver problem, I wouldn't be able to connect to my router. If it's a DNS issue, where are the DNS caches located in order to clear them (I'd trash the folder)?
    I could also reinstall the OS (waste of time, btw), but I'd really like to understand the problem, not just clear it and forget about it.
    Or better than guesses, anyone already experienced this?
    Any help welcome.

    If it's a DNS issue, where are the DNS caches located in order to clear them (I'd trash the folder)
    No DNS caches, it looks up the alphabetic and then uses the numberic from then on.
    http://17.149.160.49
    is Apple, Inc main US web site. It that works, and the alphabetic does not, you have a DNS probelm.

  • HT5539 Can u connect wirelessly to Mac mini

    Can u connect wirelessly to Mac mini

    Yes, your Mac Mini has built-in 802.11n support and Bluetooth support.  What do you want to hook up wirelessly?

  • Can't connect wirelessly to router

    I got a new laptop and a new router wrt160n v3 everything was going fine, my connection wirelessly was laggy but that was okay. One day by mistake i set myself as an "intruder" on my router and deleted myself off the map. I tried everything, putting the cd and reset the settings but no matter how hard i can't connect wirelessly to my router anymore. Now i have to stick a wire to my router and sit beside my computer. also when i do connect to it, it says that i cant or something. I need help asap !
    question : how can i connect wirelessly back to my router

    This is certainly an unusual problem, but from your description, I would have to assume that the router memorized the MAC address of your wireless adapter, and won't let you reconnect.
    The best solution would be to download and install (or re-install) the lastest firmware for your router, then reset the router to factory defaults, then setup the router again from scratch.  If you saved a router configuration file, DO NOT use it  ---  you must setup the router from scratch.
    Alternatively, you might be able to change the MAC address of your wireless adapter.  The downside of this solution is that if you ever re-install your computer, you will need to remember to change the wireless adapter's MAC address again.
    Message Edited by toomanydonuts on 01-17-2010 12:10 AM

  • Can't connect wirelessly to our WRT54GX4 after a time without rebooting the router

    Hi,  We have 2 of these routers and can't connect wirelessly to them after a period of time (unknown length at this point) until we reboot the routers.  We have some printers cabled to one and a PC to the other.  Both loose their ability to allow wireless communications after a while.  We reboot them and they work fine.  Is it a setting that I can't fine?
    Thanks
    Mike

    hi...first off, ensure that the routers have the latest firmware installed....then try changing the wireless settings on the router
    ssid - any non-linksys name
    channel - either 1 or 11
    enable encryption
    beacon interval - 50
    Fragmentation threshold - 2306
    RTS threshold - 2307

  • Can't connect (wireless) to my Airport Express anymore with iBook, iPad or iPhone.

    Can't connect (wireless) to my Airport Express anymore with iBook, iPad or iPhone. It still recognizes the printer on the iBook (bonjour), but not on my Windows notebook (work). The only device that still connects via wireless is the PlayStation 3.

    The latest firmupdate solved the issue.

Maybe you are looking for

  • Flickering on display

    Hi there is an intermittent flickering on my 15" Macbook pro retina?What can i do about it?Thank you in advance.

  • What is the power consumption of airport extreme

    I have bought a time capsule which is fits close to my TV and HIFI but I realized it gets really hot, would I have a similar problem with Airport Extreme or is power consomption lower ?

  • Problem with viewing activities

    Hello, we have SCSM 2012 R2, we have SCSM console installed on 2 computers. Only on one computer we have problem with viewing activities. For example, we go to Work items - Service Request Fullfulment - All Open service requests - Choose one request

  • UIElement InvisibleElement - What is it for?

    Hello Everyone. I would really like to know what the UI Element InvisibleElement is intended for. I have tried to use it for a couple of things (as space filler for example) but it hasnt worked for me. So I'd like to know if anyone has found a good u

  • Photoshop cc does not associate with psd files?

    I have a simple answer to the problem of photoshop cc not being able to associate psd files and not showing in the options window when you try to associate it with the psd file? How do I get it into the forum where it belongs?