Entering Network path name to connect with HP all in one scanner

I am unable to find the correct way to enter a network path for a shared folder on my laptop to scan to from my network scanner to my computer.

Hi Bob - I have the exact same issue - any luck with a solution for this yet?

Similar Messages

  • HT4623 since i updated my iphone 4 to ios 6, i ve noticed that the wifi connection turns off each time when the screen is locked. I need to be connected with wifi all the time so as to stay updated with all my emails.

    since i updated my iphone 4 to ios 6, i ve noticed that the wifi connection turns off each time when the screen is locked. I need to be connected with wifi all the time so as to stay updated with all my emails. is there anyway for this problem.
    (PS: i know we could use 3G but i want to use wifi instead)

    I am having a really wierd issue as well that is probally related. I dont see 95% of the album artwork associated with my music. Also, it seems as if this has gotten worse since I started using that match feature

  • Trying to connect HP officejet all-in-one! assitant does not support router??

    I am trying to connect HPOfficejet 7410 All-in-One which is wirless enabled to my wireless netowork. Getting message," HP NETWORK ASSISTANT does not currently support the router that is connected to your system."  Does this mean that I cannot setup this printer with the router I have?  Or is there another way I can connect it without using the Network assistant?  The router I have is a Linksys Router Model # WRT110 . I have tried to find another router that was in the list of "supported routers" with no luck.  I have looked everywhere.  Please if someone could help! Let me know if you need more info to answer my question. Thanks!

    Actually, its not that the youre router is not ocompatible with the HP Network Assistant. Maybe yuore router has a very secure network security thats why the wireless assistant could not connect the printer to youre router
    - The other way to connect the printer to your wireless network is to run the wireless setup wizard on the printer.
    - Step 1. Press the set up button on the printer and press the right arrow then navigate & look for netwok menu then press ok.
    - Step 2. press the right arrow and look for wireless setup wizard
    - it will look for youre wireless router and try to select your router the enter the security key(WEP or WPA) if you have one.
    - after that it will prompt you that the printer is connected to your network
    REGARDs --- 1234 --

  • Which version of MaxDB will be there with SAP All in One program

    Hi All,
    Does any one know what version of MaxDB will be bundled with SAP All in One program.
    Regards
    Raja

    Hello Raja,
    as far as I know, the SAP Business All-in-One Faststart program is bundled with SAP MaxDB version 7.6.03. Of course an update to the latest 7.6 version can be done.
    Best regards,
    Melanie

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

  • Strange Exchange name when connecting with Outlook 2013 to Exchange server 2013 SP1

    I've setup a test environment with Windows Server standard 2012 R2 and Exchange Server 2013 SP1...
    In- and outbound SMTP works fine, as well as connecting with OWA and Mac Outlook client...
    Oddly though when setting up an Outlook 2013 connection....it recognizes the email address correctly, but later on can't connect and shows a dialog to enter the server and email account manually....though the profiled fields show something like:
    Exchange Server: [email protected]
    Mailbox: =SMTP:[email protected]
    When I fill in the right fields....it won't connect and falls back to the values above...
    Something wrong in the Exchange setup?

    Hmm...found aguide here:
    http://enterpriseit.co/microsoft-exchange/2013/ssl-certificate-request/
    Though it doesn't mention anything that with the self-signed certs it won't allow Outlook 2013 to connect...
    So from my point of view Outlook 2013 should be able to connect anyway...as during the connect process you can install the self-signed cert.....so must be something else then...

  • Iphone4s does not give me enough time to enter password when trying to connect with bluetooth

    Bluetooth connection with iPhone 4s and 2006 BMW disconnects.  When attempting to resynch, the iPhone times out before I can enter my password.  Anyone else having a similar problem ?

    Settings>General> Auto-Lock
    Try changing the amount of minutes your screen stays on.

  • Anyone had any luck scanning with hp all in one connected on airport express usb bonjour

    Can someone tell me if apple will provide any support for scanning device included in hp all in one printers when connected on airport with USB bonjour network?
    From what I have read so far, it would seem that the only way to get a network printer to work decently is to use it with an airport extreme base station with an ethernet cable.  The usb "way" of the airport express doesn't seem to handle any fancy utility like ink level, test page or scanning. 
    Anyone have a solution other than that of buying an airport extreme base station ?
    Sorry for my english, i'm from québec Canada (french canadien)
    Thanks for any help

    Can someone tell me if apple will provide any support for scanning device included in hp all in one printers when connected on airport with USB bonjour network?
    Apple receives the printer driver software from various manufacturers. So far, none of the printer manufacturers have chosen to include extra features in the "USB network" versions of the software. Since this is a user forum, none of us here have any knowledge about what future plans may be.
    Your question really should be directed to the manufacturer of your all-in-one device. While we can't speak for Apple, it would be logical to assume that they would include this software shortly after it is made available by the printer manufacturer.
    From what I have read so far, it would seem that the only way to get a network printer to work decently is to use it with an airport extreme base station with an ethernet cable.
    That's correct. Another way of saying the same thing is that if you want your all-in-one device to function correctly on a network, then look for a network all-in-one device, not a USB device.  A properly configured wireless all-in-one would also work as a network device, since it connects to the network, not to USB.

  • Printing with HP all-in-one connected to Airport Extreme with USB

    We have an HP Photosmart 2610 all-in-one, an AirPort Extreme base station, and a G-5 MacIntosh running OS 10.4.8. We can print when the all-in-one unit is connected directly to the Mac with USB cable, however, we are unable to print when the USB cable is connected to the base station. What can you suggest?

    Which driver are you using?
    According to HP must use drivers 6.3.4 or 7.0
    http://h10025.www1.hp.com/ewfrf/wc/genericDocument?lc=en&cc=us&docname=c00035369

  • Connecting my wireless all in one printer to a NEW network

    We recently switched internet providers and I have tried to swap the programmed network on my all in one photo printer. However it doesn't seem to allow me to run setup again. I don't have the disk that came with the printer. What can I do? Thank you for your help.

    In the Network setup, you should have the option to select 'Let me specify the wireless settings again'.
    Troubleshooting steps HERE
    If all else fails, Uninstall the printer software and reinstall it from the download section HERE
    ******Clicking the Thumbs-Up button is a way to say -Thanks!.******
    **Click Accept as Solution on a Reply that solves your issue to help others**

  • Can't connect Photosmart 7510e all-in-one C311a to network for updates-new install-Windows 7 32 bit

    During installation of new printer and wireless e-print set up (Photosmart 7510e all-in-one C311a) I was asked to use printer to check for updates but I am getting error "printer is not connected to a network". I have printer connected to laptop via USB. Laptop have active wireless connection, Windows 7 Pro 32 bit. Please advice.

    Hi mjf11,
    Sorry you are having trouble. Here is a link to the HP Network Diagnostic Utility, which should help you resolve your network connectivity issue:
    http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02114394&cc=us&dlc=en&lang=en&lc=en&product=507...
    If I have helped in any way, just click the Kudos star on the left. Also, if your issue has been resolved, don't forget to select Accept as Solution

  • HP C3180 - Can I SCAN with this All-In-One connected to base station?

    I bought a HP C3180 all in one Printer/Scanner/Copier and I have it connected to my Airport Extreme base station.
    My question is, is there any way to Scan with this via the USB connection to the Airport Base Station ? Or do I have to connect it directly to the Mac?
    Thanks for any input
    Happy 4th,
    -Rob

    Robbie:
    You will have to connect the device directly to the computer to scan. Scanning is not supported when connected to the Airport.
    I've heard several explanations as to why this is the case. Some say it is a poorly written driver by the printer manufacturers and others say it is a limitaion of the Airport. I'm not sure which is correct but bottom line is, it doesn't work.
    Hope this helps.
    David

  • Mac OS 10.7 printer problem with 6500 all-in-one wireless

    HP 6500 all-in-one wirelss: After configuring (and reconfiguring) the printer and exhausting all the troubleshooting steps suggested by HP, I still have the problem of prints stalling in the queue or, alternately, printing very very slowly. Wireless connectivity is "excellent" according to the Wireless Network Test Report. When printing, printer is found, display says "Connected to Printer" then the barber-pole spins and spins and eventually the word "Idle" appears. Any suggestions on how to get printer to work?

    This article should help to maintain wireless connection:
    http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02817031&cc=us&dlc=en&lc=en#N101
    Give the steps outlined a try and let us know if it helps.
    Best of Luck!
    You can say thanks by clicking the Kudos Star in my post. If my post resolves your problem, please mark it as Accepted Solution so others can benefit too.

  • Can I connect My HP All in One to Iball Nirantar UPS-621V

    I have a HP Deskjet Ink Advantage 3545e recently brought it. It is an All In One Printer, Scanner, Copier.
    My Question is whether if it is safe to connect the printer to an UPS.
    The UPS which i bought declares that I should not connect any Laser printer or scanner to the UPS as it may damage the unit.
    The UPS name is IBall Nirantar UPS-621V
    Please reply quickly
    Thanks in advance

    Hi,
    The UPS which i bought declares that I should not connect any printer or scanner to the UPS as it may damage the unit.
    Hope this makes sense.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

Maybe you are looking for

  • HBR Error

    Hi, When I try to run BR attached to a form, getting error" "An error occurred while running the specified calc script. Check the log for details." But I am able to run rules with out errors from Planning web tools->business rules and aslo from EAS.

  • Lion has messed up my Macbook Pro. Help me PLEASE!

    I recently updated to Lion and have already had to fix my calendar and my iphoto, but now there are more problems Ok so heres what is wrong: Mail: I am completely unable to delete messages no matter what I try. Skype: I am fully updated and now canno

  • Sell MacBook Pro with fresh Mavericks install

    Hello everyone About 5 years ago I got my first Mac, a MBP late 2008. A few weeks ago I got a new one and have decided to give the old one to some family in England (I live in Denmark myself). So I deleted the data on the harddrive (7 pases cause why

  • Ocx in forms6i

    We are planning to undertake the development of a large Enterprise Application System in Developer 2000 Forms 6i. We also want to keep an option open to be able to migrate our application at a later date to Forms 9i. We understand that in Forms 9i, s

  • CC license overseas (South America - Europe)

    Silly (but honest) question: I'm about to buy a CC license in Brazil but I'm moving to Germany next month. Does anyone know if I can still use the softwares overseas?