WRT610N - connected to multiple networks?

Hi all, I bought and set up one of these routers yesterday and initially my laptop reported it was connected to multiple networks, same SSID but different antennae, it meant I could switch between 2.4 and 5.0 GHz without dropping connection and obviously had great connection strength.  But after a shut down and restart it will now only connect to one antenna at a time.  Which is the correct way for the connection to work, should it be connected to only one antenna at a time?
Thanks in advance.

I've obviously not been clear, when I set up the router yesterday I set different SSIDs for the two bands, LINKSYS1 for 5GHz and LINKSYS2 for 2.4GHz.  When I connected to LINKSYS1 I got 2 connections simultaneously, one labelled "LINKSYS1" and another lablled "LINKSYS1   2" both providing a 5GHz connection.  I also had another connection at one point called "LINKSYS1   3".  Exact same thing happened when I connected to the 2.4GHz band "LINKSYS2" (i.e. I had 2 connections labelled "LINKSYS2" and "LINKSYS2   2" both providing a 2.4GHz connection).  Hovering over the network icon showed 2 connections and network and sharing center showed connected to multiple networks.  When I restarted it this morning it's only connecting to one and the converage isn't as good (could get 100% signal from outside last night and stream DVD iso's but it's buffering quite a bit today).  I've googled it and some other people have mentioned the same thing but they seemed to think it was a fault, but it gave me better coverage than I'm getting today.  What I was asking was which is the correct way for it to operate, as one connection or multiple connections.

Similar Messages

  • When I enter my password to start my atv it tells me, that "there was a problem connecting to the network."  My Ipad works fine but not my new atv.  I have reset my password multiple times with no help.  I have also rebooted my wireless server.take it bac

    When I enter my password to start my atv it tells me, that "there was a problem connecting to the network."  My Ipad works fine in my house, but not my new atv.  I have reset my password multiple times with no help.  I have also rebooted my wireless server.  Do I take it back?

    Where is everyone????  Does anyone have an answer???
    Allik1

  • Trouble connecting to wireless network with WRT610N

    Need some help please.  I have a WRT610N with 3 laptops that I am connecting to the network.  I have been able to successfully connect 2 of them, but the third is a no go.  I have the security set for WPA-TKIP, have a network code set; but when I enter the code on the one laptop and try to connect it won't do it.  The laptop will connect via wired connection and will also connect wireless if I take the security off.  Many times I have noticed the security settings on the laptop will change after I have save them; going from WPA-TKIP back to OPEN-WEP.  I have tried everything, but no luck.  The laptop is running Windows XP Home edition on a Sonay Vaio PCG K-15.  Any help would be greatly appreciated.  Thanks

    Well try upgrading the firmware of the router & keep on holding tightly
    the reset button in such a way that power light is blinking on the
    router & then do a complete network power cycle i.e., unplug the power
    cables from the modem & from the router & then plug in the power cable
    to the modem first once all the lights are solid green you could plug
    in the power cable to the router & check out it will definately work!!
    Open the setup page of router using 192.168.1.1 then put in the password as admin...
    all you need to do is do the wireless settings such as Radio Band Frequency to Standard 20 MHZ frequency,channel to 11.
    Also,the advanced wireless settings to Beacon Interval=50,Frag
    thres=2306 & Rts thres=2307 & then uncheck a Block Anonymous Internet
    Requests & it will definately work!!!

  • NetworkManager fails multiple times to connect to wirless network

    Hello Arch-Community!
    I run a Dell Vostro V131 and a Dell XPS 13 with an up to date Arch Linux with Gnome Shell as desktop enviroment. My internet connection is established by an AVM Fritzbox 7490 over wireless lan. The WLAN connection works with a windows pc and my android devices absolutely stable. As soon I get into the reach of wlan, my smartphone connects without any issues.
    With Arch I've got the following problem: After a restart or standby mode, the NetworkManager tries to connect to my wireless lan. After about 30 seconds it fails and the icon vanishes out of the notification bar. After a short moment it tries again, it fails, it tries, it fails... until it magically works and the computer is logged into my wireless network.
    To get some logs i killed the NetworkManager task and restarted it by hand. In the following log you see NetworkManager starting and failing a couple of logins with the message "association took too long, failing activation". At the end NetworkManager reports "Activation (wlp18s0) successful, device activated" and wlan works... I didn't change a thing.
    I would be very thankful if someone might be able to help me figure out what might go wrong.
    Thanks!
    Christoph
    $ sudo /usr/bin/NetworkManager --no-daemon
    NetworkManager[3251]: <info> NetworkManager (version 0.9.8.10) is starting...
    NetworkManager[3251]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
    NetworkManager[3251]: <info> WEXT support is enabled
    NetworkManager[3251]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
    NetworkManager[3251]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
    NetworkManager[3251]: keyfile: parsing KIT-OPENVPN ...
    NetworkManager[3251]: keyfile: read connection 'KIT-OPENVPN'
    NetworkManager[3251]: keyfile: parsing Littlehelper ...
    NetworkManager[3251]: keyfile: read connection 'Littlehelper'
    NetworkManager[3251]: keyfile: parsing Santa ...
    NetworkManager[3251]: keyfile: read connection 'Santa'
    NetworkManager[3251]: <info> monitoring kernel firmware directory '/lib/firmware'.
    NetworkManager[3251]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:12:00.0/ieee80211/phy0/rfkill0) (driver ath9k)
    NetworkManager[3251]: <info> WiFi hardware radio set enabled
    NetworkManager[3251]: <info> WiFi enabled by radio killswitch; enabled by state file
    NetworkManager[3251]: <info> WWAN enabled by radio killswitch; enabled by state file
    NetworkManager[3251]: <info> WiMAX enabled by radio killswitch; enabled by state file
    NetworkManager[3251]: <info> Networking is enabled by state file
    NetworkManager[3251]: <info> (wlp18s0): using nl80211 for WiFi device control
    NetworkManager[3251]: <info> (wlp18s0): driver supports Access Point (AP) mode
    NetworkManager[3251]: <info> (wlp18s0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 4)
    NetworkManager[3251]: <info> (wlp18s0): exported as /org/freedesktop/NetworkManager/Devices/0
    NetworkManager[3251]: <info> (wlp18s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    NetworkManager[3251]: <info> (wlp18s0): bringing up device.
    NetworkManager[3251]: <info> (wlp18s0): preparing device.
    NetworkManager[3251]: <info> (wlp18s0): deactivating device (reason 'managed') [2]
    NetworkManager[3251]: <warn> failed to allocate link cache: (-26) Protocol mismatch
    NetworkManager[3251]: <info> (enp19s0): carrier is OFF
    NetworkManager[3251]: <info> (enp19s0): new Ethernet device (driver: 'r8169' ifindex: 2)
    NetworkManager[3251]: <info> (enp19s0): exported as /org/freedesktop/NetworkManager/Devices/1
    NetworkManager[3251]: <info> (enp19s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    NetworkManager[3251]: <info> (enp19s0): bringing up device.
    NetworkManager[3251]: <info> (enp19s0): preparing device.
    NetworkManager[3251]: <info> (enp19s0): deactivating device (reason 'managed') [2]
    NetworkManager[3251]: <info> Added default wired connection 'Kabelgebundene Verbindung 1' for /sys/devices/pci0000:00/0000:00:1c.2/0000:13:00.0/net/enp19s0
    NetworkManager[3251]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    NetworkManager[3251]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    NetworkManager[3251]: <info> (wlp18s0) supports 4 scan SSIDs
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: starting -> ready
    NetworkManager[3251]: <info> (wlp18s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
    NetworkManager[3251]: <warn> Trying to remove a non-existant call id.
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: ready -> disconnected
    NetworkManager[3251]: <info> (wlp18s0) supports 4 scan SSIDs
    NetworkManager[3251]: <info> Auto-activating connection 'Santa'.
    NetworkManager[3251]: <info> Activation (wlp18s0) starting connection 'Santa'
    NetworkManager[3251]: <info> (wlp18s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    NetworkManager[3251]: <info> NetworkManager state is now CONNECTING
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
    NetworkManager[3251]: <info> Activation (wlp18s0/wireless): connection 'Santa' has security, and secrets exist. No new secrets needed.
    NetworkManager[3251]: <info> Config: added 'ssid' value 'Santa'
    NetworkManager[3251]: <info> Config: added 'scan_ssid' value '1'
    NetworkManager[3251]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    NetworkManager[3251]: <info> Config: added 'auth_alg' value 'OPEN'
    NetworkManager[3251]: <info> Config: added 'psk' value '<omitted>'
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> inactive
    NetworkManager[3251]: <info> Config: set interface ap_scan to 1
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: inactive -> authenticating
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> authenticating
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
    NetworkManager[3251]: <warn> Activation (wlp18s0/wireless): association took too long, failing activation.
    NetworkManager[3251]: <info> (wlp18s0): device state change: config -> failed (reason 'SSID not found') [50 120 53]
    NetworkManager[3251]: <info> NetworkManager state is now DISCONNECTED
    NetworkManager[3251]: <warn> Activation (wlp18s0) failed for connection 'Santa'
    NetworkManager[3251]: <info> (wlp18s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    NetworkManager[3251]: <info> (wlp18s0): deactivating device (reason 'none') [0]
    NetworkManager[3251]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    NetworkManager[3251]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> inactive
    NetworkManager[3251]: <info> Auto-activating connection 'Santa'.
    NetworkManager[3251]: <info> Activation (wlp18s0) starting connection 'Santa'
    NetworkManager[3251]: <info> (wlp18s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    NetworkManager[3251]: <info> NetworkManager state is now CONNECTING
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
    NetworkManager[3251]: <info> Activation (wlp18s0/wireless): access point 'Santa' has security, but secrets are required.
    NetworkManager[3251]: <info> (wlp18s0): device state change: config -> need-auth (reason 'none') [50 60 0]
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager[3251]: <info> (wlp18s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
    NetworkManager[3251]: <info> Activation (wlp18s0/wireless): connection 'Santa' has security, and secrets exist. No new secrets needed.
    NetworkManager[3251]: <info> Config: added 'ssid' value 'Santa'
    NetworkManager[3251]: <info> Config: added 'scan_ssid' value '1'
    NetworkManager[3251]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    NetworkManager[3251]: <info> Config: added 'auth_alg' value 'OPEN'
    NetworkManager[3251]: <info> Config: added 'psk' value '<omitted>'
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager[3251]: <info> Config: set interface ap_scan to 1
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: inactive -> authenticating
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> authenticating
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
    NetworkManager[3251]: <warn> Activation (wlp18s0/wireless): association took too long, failing activation.
    NetworkManager[3251]: <info> (wlp18s0): device state change: config -> failed (reason 'SSID not found') [50 120 53]
    NetworkManager[3251]: <info> NetworkManager state is now DISCONNECTED
    NetworkManager[3251]: <warn> Activation (wlp18s0) failed for connection 'Santa'
    NetworkManager[3251]: <info> (wlp18s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    NetworkManager[3251]: <info> (wlp18s0): deactivating device (reason 'none') [0]
    NetworkManager[3251]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    NetworkManager[3251]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> inactive
    NetworkManager[3251]: <info> Auto-activating connection 'Santa'.
    NetworkManager[3251]: <info> Activation (wlp18s0) starting connection 'Santa'
    NetworkManager[3251]: <info> (wlp18s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    NetworkManager[3251]: <info> NetworkManager state is now CONNECTING
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
    NetworkManager[3251]: <info> Activation (wlp18s0/wireless): access point 'Santa' has security, but secrets are required.
    NetworkManager[3251]: <info> (wlp18s0): device state change: config -> need-auth (reason 'none') [50 60 0]
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager[3251]: <info> (wlp18s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
    NetworkManager[3251]: <info> Activation (wlp18s0/wireless): connection 'Santa' has security, and secrets exist. No new secrets needed.
    NetworkManager[3251]: <info> Config: added 'ssid' value 'Santa'
    NetworkManager[3251]: <info> Config: added 'scan_ssid' value '1'
    NetworkManager[3251]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    NetworkManager[3251]: <info> Config: added 'auth_alg' value 'OPEN'
    NetworkManager[3251]: <info> Config: added 'psk' value '<omitted>'
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager[3251]: <info> Config: set interface ap_scan to 1
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: inactive -> authenticating
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> authenticating
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
    NetworkManager[3251]: <warn> Activation (wlp18s0/wireless): association took too long, failing activation.
    NetworkManager[3251]: <info> (wlp18s0): device state change: config -> failed (reason 'SSID not found') [50 120 53]
    NetworkManager[3251]: <info> NetworkManager state is now DISCONNECTED
    NetworkManager[3251]: <warn> Activation (wlp18s0) failed for connection 'Santa'
    NetworkManager[3251]: <info> (wlp18s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    NetworkManager[3251]: <info> (wlp18s0): deactivating device (reason 'none') [0]
    NetworkManager[3251]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    NetworkManager[3251]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> inactive
    NetworkManager[3251]: <info> Auto-activating connection 'Santa'.
    NetworkManager[3251]: <info> Activation (wlp18s0) starting connection 'Santa'
    NetworkManager[3251]: <info> (wlp18s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    NetworkManager[3251]: <info> NetworkManager state is now CONNECTING
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
    NetworkManager[3251]: <info> Activation (wlp18s0/wireless): access point 'Santa' has security, but secrets are required.
    NetworkManager[3251]: <info> (wlp18s0): device state change: config -> need-auth (reason 'none') [50 60 0]
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager[3251]: <info> (wlp18s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
    NetworkManager[3251]: <info> Activation (wlp18s0/wireless): connection 'Santa' has security, and secrets exist. No new secrets needed.
    NetworkManager[3251]: <info> Config: added 'ssid' value 'Santa'
    NetworkManager[3251]: <info> Config: added 'scan_ssid' value '1'
    NetworkManager[3251]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    NetworkManager[3251]: <info> Config: added 'auth_alg' value 'OPEN'
    NetworkManager[3251]: <info> Config: added 'psk' value '<omitted>'
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager[3251]: <info> Config: set interface ap_scan to 1
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: inactive -> authenticating
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> authenticating
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> associating
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: associating -> associated
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: associated -> 4-way handshake
    NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: 4-way handshake -> completed
    NetworkManager[3251]: <info> Activation (wlp18s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Santa'.
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 3 of 5 (IP Configure Start) scheduled.
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 3 of 5 (IP Configure Start) started...
    NetworkManager[3251]: <info> (wlp18s0): device state change: config -> ip-config (reason 'none') [50 70 0]
    NetworkManager[3251]: <info> Activation (wlp18s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    NetworkManager[3251]: <info> dhcpcd started with pid 3261
    NetworkManager[3251]: <info> Activation (wlp18s0) Beginning IP6 addrconf.
    dhcpcd[3261]: version 6.4.0 starting
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 3 of 5 (IP Configure Start) complete.
    dhcpcd[3261]: wlp18s0: adding address fe80::e0b1:110:f1ea:b935
    dhcpcd[3261]: DUID 00:01:00:01:1b:3e:cd:f2:78:2b:cb:cf:a1:ab
    dhcpcd[3261]: wlp18s0: IAID 4e:93:d0:c9
    NetworkManager[3251]: <info> (wlp18s0): DHCPv4 state changed nbi -> preinit
    dhcpcd[3261]: wlp18s0: rebinding lease of 192.168.178.49
    dhcpcd[3261]: wlp18s0: soliciting an IPv6 router
    dhcpcd[3261]: wlp18s0: leased 192.168.178.49 for 864000 seconds
    dhcpcd[3261]: wlp18s0: adding route to 192.168.178.0/24
    NetworkManager[3251]: <info> (wlp18s0): DHCPv4 state changed preinit -> reboot
    NetworkManager[3251]: <info> address 192.168.178.49
    NetworkManager[3251]: <info> prefix 24 (255.255.255.0)
    NetworkManager[3251]: <info> gateway 192.168.178.1
    NetworkManager[3251]: <info> nameserver '192.168.178.1'
    NetworkManager[3251]: <info> domain name 'fritz.box'
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 5 of 5 (IPv4 Commit) started...
    dhcpcd[3261]: wlp18s0: removing route to 192.168.178.0/24
    NetworkManager[3251]: <info> (wlp18s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    NetworkManager[3251]: <info> Activation (wlp18s0) Stage 5 of 5 (IPv4 Commit) complete.
    NetworkManager[3251]: <info> (wlp18s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    NetworkManager[3251]: <info> NetworkManager state is now CONNECTED_GLOBAL
    NetworkManager[3251]: <info> Policy set 'Santa' (wlp18s0) as default for IPv4 routing and DNS.
    NetworkManager[3251]: <info> Writing DNS information to /usr/bin/resolvconf
    NetworkManager[3251]: <info> Activation (wlp18s0) successful, device activated.

    Thanks for your reply.
    We use classes12 because we had no needs to upgrade, like TIMESTAMP...
    Maybe we could try change driver.
    And nothing in the code loop to try that many times. Like written in the example code we made a little sample page just to test the connection. That's all.
    I don't have any control of the pool connection. But the people that are doing it says to me that there is no settings configured to attempt connection 200 times.

  • Simultaneous multiple networks under access connections?

    I have two networks at home, one of which uses an ADSL internet connection the 2nd of which serves Network attached storage devices. Each network has a router. I want to use the wireless connection to connect to one network, and the ethernet con, for the other. I've looked through the settings carefully in the Access connections application. I've set profiles for the wired and wireless network adapters. I've unselected the tab to "disconnect from the connection when switching to a different network" but I cannot be connected wirelessly and wired simulatneously. If the wifi adapter is running, I'm working on network #1 with the internet connection I use, and if i pop the ethernet cable in from the second network, instead of having access to my Network attached storage devices, and retaining the wireless connection it seems to disconnect from the wireless connection and just retrieve an IP from the router network #2. I thought about setting up static IP's but that shouldnt be necessary. The adapters should work independently of one another. So whats the deal here? I cant move the NAS's from one network to the other, but I shouldn't need to either.

    Take a look to the option "Switching location".
    Open AC -> Configure -> Switching location.
    Try this: Disable the automatic location switching option.
    Regards.

  • EthernetIP, Unable to connect to the network path specified, Multiple NICs

    I have not been able to find an answer concerning this error, so I am hoping someone can help.
    Computer has LabVIEW 2013 with the NI-Industrial Communications for EtherNet/IP 1.2.1 addon with Win XP although I have verified the same setup with Win 7 x32 with the same results. I am using the EthernetIP CIP Get Attribute Single.vi and the corresponding "Set" vi.
    I am using a pc with five network cards, one for the corporate network (dhcp) and four that are connected to four Rockwell PowerFlex 700S AC variable drives via CAT6 crossover cables. Each 700S drive controls a motor in an engine dyno teststand. The 700S drives have the latest available firmware installed. The four NIC/700S pairs have hard coded IP addresses with the appropriate subnet masks for proper routing. I can use the Windows "ping" command without errors. The program uses a QSM-PC architecture which I have four separate qsm loops  that "talk" to the each drive, those loops constantly request three parameters from the drive, a boolean drive status array, the rpm , and the torque every 250ms using the CIP "Get" vi. That data is then sent to the main front panel via shared variables. When the operator wants to say change the rpm, a write command is inserted into the queue, and the CIP "Set" vi is used.
    My problem is when I start the program, it is hit or miss on whether these loops will begin to loop through their states. If they start, the program is rock solid. When one of the loops does not start, which is most of the time, the error returned is the "-251723767 Unable to connect to the network path specified". See the attached pictures. So if I disable three of the four loops, the error never shows up. Adding another loop or more will cause the error. Slowing down the request rate does not fix the issue and it is not always the same loop that will throw the error. Each qsm loop has its own session name and its own action engine with the only common thing amongst the action engines would be the "Get" and "Set" EthernetIP VIs.
    No more ideas.....Kevin
    Attachments:
    error.PNG ‏12 KB
    clone_error.PNG ‏30 KB

    250 ms is a pretty slow update rate for CIP so Why use a nic for each drive? Use 1 drive nic in your PC and use a network switch to connect with your drives. If You have more then 1 nic you need to specify the nic to use for each loop for each drive IP address so the drive and the loops are using the correct IP settings. You should be able to use as low as 30 ms updates with no problems.

  • Cant login multiple network accounts on the same client?

    Setup:
    I have created a simple Lion Server on a new i7 Mac Mini. I have configured Open Directory in Master mode and have setup 4 user accounts. I have enabled the File Sharing service and checked the "Make available for home directories" option on the "Users" file share. I have configured each of the 4 user accounts to use this location as the home folder. I have connected my client machines (all OSX Lion) to the Network Account Server.
    Problem:
    I can log one user into the client machine, but when using "Fast User Switching" and logging on as the second user I get the following error:
    "You are unable to log in to the user account "guestaccount" at this time. Loggin to the account failed because an error occured"
    In the console if I search for that user account the related error message is:
    11-07-31 12:30:54.993 PM authorizationhost: ERROR | -[HomeDirMounter mountNetworkHomeWithURL:attributes:dirPath:username:] | PremountHomeDirectoryWithAuthentication( url=afp://inntaserver01.local/Users, homedir=/Network/Servers/inntaserver01.local/Users/guestaccount, name=guestaccount ) returned 16
    Any thoughts as to why the Home Folder "mounter" failed in this scenario?

    Historically you have never been allowed to use Fast User Switching to log in multiple network logins on the same client machine. This certainly applied with Tiger, Leopard, and Snow Leopard. I have not yet personally tried this with Lion.
    I believe that the underlying reason for this not being allowed is down to how AFP volumes are mounted. The AFP mount becomes 'owned' by the user that triggers the login. With a network login the first user becomes the owner and this means subsequent attempted network logins are denied access to that share and hence cannot access their home directories.
    With Tiger, Leopard, and Snow Leopard servers, one could configure network home directories to be shared via NFS instead of AFP. NFS gets treated a lot different in terms of mounting, and is done more at a system level than a user level. While again I have not personally tried Fast User Switching with NFS shared home directories, this approach is specifically recommended by the authors of AquaConnect (a Macintosh Terminal Server solution) in order to allow multiple logins on the same Terminal Server. This seems to be for the same underlying reason. Using NFS does certainly work for use with AquaConnect and also works for the competing iRAPP Terminal Server product as well.
    Unfortunately, Lion Server while it can be made to run an NFS server, will not let you configure using NFS for sharing home directories. I have actually reported this as a 'bug' in Lion server.
    Neither the authors of AquaConnect or iRAPP have actually tested this scenario with Lion server yet, but AquaConnect do plan to investigate it. It could make it considerably more difficult to use their products.
    So in summary, using NFS to share network home directories in theory would avoid the problem and can be done with a Tiger/Leopard/Snow Leopard server, but cannot be done with a Lion server. It is possible however to mix Lion with older server versions. This might for some people be a possible workaround.
    PS. A bonus side-effect of using NFS shared home directories was that this allowed badly written software like Adobe's applications which are otherwise notorious for having major issues with network logins and home directories to work without errors. As an example Adobe Acrobat Pro introduced a bug in version 7.0 which prevented it being able to print-to-PDF (one of the major reasons to buy Acrobat Pro). It tooks two years for them to eventually fix this in Acrobat Pro 8.1 (I know because I spent that two years nagging them to fix it and was a beta tester). Unfortunately they then reintroduced the bug in Acrobat Pro 9.0. Fortunately I discovered this side-effect got round the issue although a clunkier workaround was also possible for Snow Leopard clients by redirecting certain folder paths.

  • How to use a connection across multiple request

    What is the idea of using a connection across multiple requests.

    Please give more details. What connections and what requests
    And are you posting on the right forum? (This sounds more like a Networking/servlet question)

  • My Apple TV is reading " There was a problem connecting to the network" error - 3906

    I have reset all network components and the Apple TV.  I first set up Apple TV and it worked beautifully.  The next time I turned it on it gave me the error message.  I have tried reconnecting to the netwrk multiple times.  I have my laptop and my ipad connected to the network, but the Apple TV will no longer connect.  I am out of solutions.  Any suggestions would be greatly appreciated.  Thank you.

    I had the same problem. I just solutioned it just by disabling MAC Address filtering in my LinkSys router. This is strange as I did enter the address of my ATV3 in the list of allowed devices in the router configuration software.
    The truth is that it now works! I just seems that ATV is not compatible with MAC Address filtering.

  • Can't scan or connect to WPA network since kernel upgrade

    Hi guys,
    I upgraded to kernel 2.6.29 earlier today and have been having trouble with scanning and connecting to WPA encrypted networks since. I'm stuck with a wired connection for the minute, but I can't have the wire going through the house for so long otherwise somebody will trip over it - probably me.
    I usually use netcfg to connect to the network, but since the update that has failed.
    My network called is a Belkin USB Wireless G, model number F5D705ed version 5000ed. It worked perfectly fine on 2.6.28 using the rtl8187 native drivers.
    dmesg output for 2.6.29
    usbcore: registered new interface driver rtl8187
    rtl8187: 8187B chip detected.
    wmaster0 (rtl8187): not using net_device_ops yet
    wlan0 (rtl8187): not using net_device_ops yet
    phy0: hwaddr 00:1c:df:47:44:c0, RTL8187BvE V0 + rtl8225z2
    I can start the card up using
    sudo ifconfig wlan0 up
    When I attempt to scan for a wireless network, I get
    sudo iwlist wlan0 scan
    wlan0 No scan results
    The network is WPA, and would scan fine on 2.6.28.
    wpa_supplicant.conf looks like this
    ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
    eapol_version=1
    ap_scan=1
    fast_reauth=1
    network={
    ssid="Arazmataz"
    psk="*****************"
    priority=5
    I should note though, that since the update - /var/run/wpa_supplicant seems to have disappeared.
    network.d/profile looks like
    CONNECTION="wireless"
    INTERFACE=wlan0
    SCAN="yes"
    SECURITY="wpa"
    ESSID="Arazmataz"
    GATEWAY="192.168.1.1"
    KEY="**************"
    IP="dhcp"
    IWCONFIG="rate 54M"
    TIMEOUT=120
    dhcpcd times out also and netcfg fails to connect. Going back to WEP seems to work ok.
    iwconfig
    wlan0 IEEE 802.11bg ESSID:""
    Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
    Tx-Power=20 dBm
    Retry min limit:7 RTS thr:off Fragment thr=2352 B
    Power Management:off
    Link Quality:0 Signal level:0 Noise level:0
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0
    Please help!
    Thanks.
    Last edited by paulingham (2009-04-09 19:04:23)

    brain0 wrote:So everyone whose issue is NOT solved by installing crda and configuring it, please raise your hand (paulingham, I guess you will be one of them).
    *raises hand*
    I've made some progress though - but still can't connect. I can now scan for a network though.
    /etc/conf.d/wireless-regdom
    WIRELESS_REGDOM="GB"
    /var/run/wpa_supplicant still didn't exist, so I created a /var/run/wpa_supplicant folder - and saw a few success messages in the log. This allowed me to bring the card up again and scan for a network.
    At this point, I was getting excited until netcfg2 still kept telling me that it couldn't associate with the network.
    I installed wicd and gave that a go and got the following. I did a 'tail -f /var/log/wicd/wicd.log' and got this;
    2009/04/10 15:17:10 :: Connecting to wireless network Arazmataz
    2009/04/10 15:17:10 :: Putting interface down
    2009/04/10 15:17:10 :: ifconfig wlan0 down
    2009/04/10 15:17:10 :: Releasing DHCP leases...
    2009/04/10 15:17:10 :: Setting false IP...
    2009/04/10 15:17:10 :: ifconfig wlan0 0.0.0.0
    2009/04/10 15:17:14 :: ifconfig eth0 0.0.0.0
    2009/04/10 15:17:14 :: Stopping wpa_supplicant and any DHCP clients
    2009/04/10 15:17:14 :: killall wpa_supplicant
    2009/04/10 15:17:14 :: iwconfig wlan0
    2009/04/10 15:17:14 :: Flushing the routing table...
    2009/04/10 15:17:14 :: route del dev wlan0iwconfig wlan0
    2009/04/10 15:17:14 ::
    2009/04/10 15:17:14 :: route del dev eth0
    2009/04/10 15:17:14 :: Generating psk...
    2009/04/10 15:17:14 :: ['/usr/sbin/wpa_passphrase', 'Arazmataz', 'key commented out here']
    2009/04/10 15:17:14 :: Attempting to authenticate...
    2009/04/10 15:17:14 :: ['wpa_supplicant', '-B', '-i', 'wlan0', '-c',
    '/var/lib/wicd/configurations/001b11ada667', '-D', 'wext']
    2009/04/10 15:17:14 :: iwconfig wlan0
    2009/04/10 15:17:14 :: Putting interface up...
    2009/04/10 15:17:14 :: ifconfig wlan0 up
    2009/04/10 15:17:18 :: iwconfig wlan0 mode managed
    2009/04/10 15:17:18 :: ['iwconfig', 'wlan0', 'essid', 'Arazmataz', 'channel', '6', 'ap',
    '00:1B:11:AD:A6:67']
    2009/04/10 15:17:18 :: WPA_CLI RESULT IS SCANNING
    2009/04/10 15:17:19 :: WPA_CLI RESULT IS SCANNING
    2009/04/10 15:17:20 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:21 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:22 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:23 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:24 :: WPA_CLI RESULT IS SCANNING
    2009/04/10 15:17:25 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:26 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:27 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:28 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:29 :: WPA_CLI RESULT IS SCANNING
    2009/04/10 15:17:30 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:31 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:32 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:33 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:34 :: WPA_CLI RESULT IS SCANNING
    2009/04/10 15:17:35 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:36 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:37 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:38 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:39 :: WPA_CLI RESULT IS SCANNING
    2009/04/10 15:17:40 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:41 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:42 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:43 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:44 :: WPA_CLI RESULT IS SCANNING
    2009/04/10 15:17:45 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:46 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:47 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:48 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:49 :: WPA_CLI RESULT IS SCANNING
    2009/04/10 15:17:50 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:51 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:52 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:53 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:54 :: WPA_CLI RESULT IS SCANNING
    2009/04/10 15:17:55 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:56 :: WPA_CLI RESULT IS ASSOCIATED
    2009/04/10 15:17:57 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2009/04/10 15:17:58 :: wpa_supplicant authentication may have failed.
    2009/04/10 15:17:58 :: exiting connection thread
    I checked the password multiple times, and it is what it is supposed to be. Still no luck connecting.

  • Officejet pro 8600 will not connect to wireless network

    I have an new Officejet Pro 8600 that I am trying to set up.  I have run the the wireless network setup wizard multiple times.  It recognizes the wireless network router asks for the WEP code and then thinks for about 5 minutes before returning a message: "Unable to connect to the network" 
    The wireless network test results suggestes that MAC address filtering may be the problem.  There is no MAC filtering function activated on our wireless router.
    The wireless router is a Verizon Actiontec MI424-WR    802.11 b & n
    We have computers running both Windows XP and MAC OS X.
    One of the reasons that we purchased this printer is for the wireless capabilities.  If it will not conect to the web then it may be going back.

    Hello,
    Based on the provided details, I believe the issue have something to do with the wireless security settings of your router.
    Please follow the steps below to access the Advanced Security Settings:
    http://www22.verizon.com/ResidentialHelp/FiOSInternet/Networking/Setup/ActiontecMI424/125511.htm
    Below you will see the Network Authentication settings.
    Select either Open System Authentication or Both.
    Shared Key Authentication is not supported by the printer, and i believe this might be the cause for the connection failure.
    Please let me know of any change,
    Shlomi
    Say thanks by clicking the Kudos thumb up in the post.
    If my post resolve your problem please mark it as an Accepted Solution

  • Windows 10 Build 9926 - Can't connect to this network in certain networks

    I have been asked to ask this question here. The original thread can be found at:
    http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_web/windows-10-build-9926-cant-connect-to-this-network/e9196f95-5570-4a92-8fae-d29d7d1416b2?msgId=b2246cb5-1038-40dc-98b6-249e8734eb7f
    Hello
     I have a Samsung 700T tablet.
     Since I got the latest update 9926 I am having issues with my corporate network access. I have to type in my user name and password on the wireless connection. When I do I get "Can't connect to this network" message.
     I have tried multiple drivers for the network card a "Intel(R) Centrino(R) Advanced-N 6235". I am currently using latest.
     I am able to connect fine with my home Wifi.
     On the "System" event log I get the following error message when I attempt to login no the WiFi.
     "A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 42"
     Any ideas?
     I have checked and my card is set to use DHCP.
    God bless,
    Bruno
    ---  got this answer ----
    Have you tried talking to your system administrator? We had a fun bug in our Cisco wireless access points and wireless controller that would
    kick Win 8+ machines from even trying to connect. A very long firmware and software update process fixed it. 
    --- answered back ----
    Hello DatAsian,
     Thank you for your response.
     This is a very large wireless network, and as far that I know I am the only one having this issue. My other devices on the same cube work fine. The only difference is of course Windows 10. The other machines are Windows 8.1 and Windows 7.
     In the past this was caused by a driver, but I have gotten about 6 different version of my wireless driver and they all have this issue.
    I read on the troubleshoot about entering the wireless configuration manually by using the "Hidden network" screen. The instructions go:
    2. Tax or click to connect to a network
    3. Tap or click Hidden network tap or click Connect and then enter the network info.
    I cannot find this "Hidden network" text on the "Connect to a network" screen. Am I missing something? Do I need to check something that allows me to connect to Hidden network? 
    One thing that I forgot to mention. I need to enter my user name and password when I enter this wireless network, since this is Employee Own device network.
    Any other ideas?
    God bless,
    Bruno
    When I use an android device I had to do the following changes to the way the device connected to wireless:
    EAP Method: TTLS
    Phase 2 Authentication: PAP
    Then I have to use my user name and password.
    Is there a way to set windows to the same type of authentication?
    Please let me know.
    God bless,
    Bruno 

    Hi Alex,
    I have the similar problem with Bruno, using the
    certificate network.
    The Event View show message of the Wired-AutoConfig as below:
    Information 1:
    Network authentication attempts have been resumed on this network adapter.
    Network Adapter: Intel(R) 82579LM Gigabit Network Connection
    Interface GUID: {************************}
    Information 2:
    Wired 802.1X Authentication was started.
    Network Adapter: Intel(R) 82579LM Gigabit Network Connection
    Interface GUID: {********************}
    Connection ID: 0x2
    Error:
    Wired 802.1X Authentication failed.
    Network Adapter: Intel(R) 82579LM Gigabit Network Connection
    Interface GUID: {******************************}
    Peer Address: ************
    Local Address: ************
    Connection ID: 0x2
    Identity: -
    User: -
    Domain: -
    Reason: 0x70006
    Reason Text: The network does not support authentication and 802.1X is enforced in the profile
    Error Code: 0x0
    Information 3:
    Network authentication attempts have been temporarily suspended on this network adapter.
    Network Adapter: Intel(R) 82579LM Gigabit Network Connection
    Interface GUID: {*************************}
    Reason Code: The network does not support authentication and 802.1X is enforced in the profile
    Length of block timer (seconds): 1200
    everything find with Windows 7 and 8.1
    days searching the internet but nothing makes sense.
    looking forward to your help
    Thanks!

  • What do i do after downloading iOS 3.1 software and "There was a problem downloading iOS 3.1.1 software update for ipod touch. an unknown error occurred (8288). Please check that the connection to the network is active and try again." comes up?

    what do i do after downloading iOS 3.1 software and "There was a problem downloading iOS 3.1.1 software update for ipod touch. an unknown error occurred (8288). Please check that the connection to the network is active and try again." comes up?

    Hello, I hope by now you have resolved the upgrade issue, but if not, here is what I ended up having to do:
    “SUCCESS!!! I took my iPod to a friend who is a computer programmer/genius. He turned off his wireless, hooked the ethernet cable directly into his computer, and the download went through without a hitch. YAY!”
    Here is my original post explaining what I had already tried:
    “Hi all,
    I got an iPod Touch 1st gen for my youngest son for Christmas as a starter. It has the 2.1.2 ios on it, but after I paid for the upgrade to 3.1.1, I keep getting an error message (8288) saying there was a problem with the network connection. I have called customer service, and they suggested I try on a different computer, and if that didn't work, try connecting to a different network, and then trying the update. None of this has worked. It seems that tech support is clueless with this issue.
    I have installed and unistalled iTunes 10.5, 10.3, 10.4, and now I am back with 10.5. I have tried looking up the issue from several search engines but no one seems to have a universal solution and I have tried several.
    I really want to have this thing updated for himw hwne he opens it, but I am starting to worry that my purchase was a bust. I know this is the oldest version, but I don't want to buy a newer, more expensive iPod and him still not be mature enough to really take care of it. As I said, this one is a starter.
    Can anyone help? Please?!
    Thank you!!!
    P.S. We have a PC, with Windows XP Home.”
    Now, there seem to be a lot of different ways to solve the 8288 error, none of which are universal. Best of luck getting yours upgraded!
    Tiffany
    P.S. The post by Sparkhi is a link to his blog going into a long story about how he wanted Apple to pay him for “solving” the issue….the one that apparently has been solved by multiple solutions. I’m not trying to bash, it just bothers me that he put up this whole story and finally, at the very end of his blog post, posts his solution.

  • There was a problem downloading iOS 3.1.1 software update for ipod touch. an unknown error occurred (8288). Please check that the connection to the network is active and try again.

    The error
    Therewas a problem downloading iOS 3.1.1 software update for ipod touch. an unknownerror occurred (8288). Please check that the connection to the network is active and tryagain.
              Keeps coming up when I try upgrading iOs 3.1.1 software to my 8gb 1st generation iPod touch! Please help! I've looked at all other posts related and none helped.

    Hello, I hope by now you have resolved the upgrade issue, but if not, here is what I ended up having to do:
    “SUCCESS!!! I took my iPod to a friend who is a computer programmer/genius. He turned off his wireless, hooked the ethernet cable directly into his computer, and the download went through without a hitch. YAY!”
    Here is my original post explaining what I had already tried:
    “Hi all,
    I got an iPod Touch 1st gen for my youngest son for Christmas as a starter. It has the 2.1.2 ios on it, but after I paid for the upgrade to 3.1.1, I keep getting an error message (8288) saying there was a problem with the network connection. I have called customer service, and they suggested I try on a different computer, and if that didn't work, try connecting to a different network, and then trying the update. None of this has worked. It seems that tech support is clueless with this issue.
    I have installed and unistalled iTunes 10.5, 10.3, 10.4, and now I am back with 10.5. I have tried looking up the issue from several search engines but no one seems to have a universal solution and I have tried several.
    I really want to have this thing updated for himw hwne he opens it, but I am starting to worry that my purchase was a bust. I know this is the oldest version, but I don't want to buy a newer, more expensive iPod and him still not be mature enough to really take care of it. As I said, this one is a starter.
    Can anyone help? Please?!
    Thank you!!!
    P.S. We have a PC, with Windows XP Home.”
    Now, there seem to be a lot of different ways to solve the 8288 error, none of which are universal. Best of luck getting yours upgraded!
    Tiffany
    P.S. The post by Sparkhi is a link to his blog going into a long story about how he wanted Apple to pay him for “solving” the issue….the one that apparently has been solved by multiple solutions. I’m not trying to bash, it just bothers me that he put up this whole story and finally, at the very end of his blog post, posts his solution.

  • Alternative Access Mapping not working "You're not connected to a network"

    Hi *,
    i want to set up alternate access mapping in my sharepoint 2013 development environment.
    My SharePoint is reachable through http://sp2013.
    I created a second web application with listens on port 8080. When i open http://sp2013:8080 everything works fine and i can see my root site collection.
    Next i added through "Add internal Urls" a new url -> http://sp2013test to the default zone.
    Next i edited the bindings in the iss application for this web application and added http://sp2013test listening to port 80:
    But i does not work! I get the message "You’re not connected to a network" from the ie.
    I dont want have to call my WebApps through ports. I want to have WebApplication which i can call through clear names like http://customerWebApp1, http://customer2WebApp. All via Port 80.
    Whats wrong here?
    Best Regards
    Bog
    Developers Field Notes | www.bog1.de

    Hi Bob,
    For you issue, try to map web application URLs to the local loopback address. For that you need to update host file at the path:(C:\Windows\System32\drivers\etc\hosts) 
    Here is a link about Setup Multiple SharePoint Web Applications on Port 80 with Https Binding on Port 443, you can use as a reference:
    http://onlinecoder.blogspot.com/2012/10/setup-multiple-sharepoint-web.html
    Best Regards
    Lisa Chen

Maybe you are looking for

  • For Cost Center Purchase Requisitions

    Hello Gurus, In ME52N transaction, For the PRs with account assignment K (Cost centres), the quantity field is display. User wants to change the quantity (which is valid). I am not able to figure out why quantity field is diaply only for cost centre

  • Authorization Rules.

    Hi, I am in the process of setting up OAM/OID to provide secure access to a website. Part of the website is public and part of the website is secure. For the secure part I want to limit access to a particular group of users who belong to i.e. secureG

  • Version of iphoto

    I just purchased an ipod touch. Has all the latest updates. I am having a problem loading photos. My thoughts are that my version od iphoto is, iphoto 5. I have it set to manual sync. Choose my folder. When I choose the folder everything says that it

  • Text selected while typing, history forgotten after hibernate

    After hibernating/screen saver/suspend I get the following two problems: 1. While typing in address field and Google Search field, the text gets selected at random events, so that what I have typed is erased. E.g. I try to type "google", but after ty

  • HT202716 How to get to Settings on Apple TV

    i just connected a new Apple TV device to my television.  When first start the TV it does not give me the option to go to settings.  It is in French. The first screen to appear is the screen with all the choice icons. I have tried restarting several