Preferred Network doesn't *stick*

Hi there. I have an ABS network set up, and have selected in all of my computers the network's name as the *preferred network*, however, whenever I restart a particular machine, it says that none of my trusted networks can be found. I then have to manually tell it which network to use. I've also set up each machine manually with its own IP addy.
Granted, this is mostly a nuisance, not a show-stopper. Any ideas what I'm doing wrong?

I've since moved and no longer experiencing this issue, so I'm closing this post.

Similar Messages

  • When returning from sleep my preferred network doesn't connect

    After returning from sleep mode my prefered network won't automatically connect. I checked the settings and its set to automatically connect to my network. I have to turn of the wireless and then turn it back on or select my network before it will connect.

    In Networking,  make sure that Wireless is at the top of the list,  if it is not then move it there above Ethernet.  I also uncheck "Ask to join new Networks"
    In Preferred Networks make the one you want the only one,  if more than one set the priority of which one first. Check "Remember Networks this computer has joined"  Most of this is in Advanced.

  • OS 10.8.5 Wi-Fi doesn't find "Preferred Network"

    We installed a new modem provided by Comcast that has built in wireless. After naming and establishing the password for the network, I successfully connected via my MacBook Pro, which detected it. Once connected I accessed the "Advanced Settings" screen in the Network control panel.
    Under the first "Wi-Fi" tab I dragged the new network to the top of the list of "Preferred Networks." I also confirmed that the "Remember networks this computer has joined" check-box was selected.
    Yet each time the computer wakes from sleep or is restarted the Wi-Fi utility scans for networks and doesn't connect to any. When I click on the control bar icon for Wi-Fi the network appears -- usually at the bottom of the list -- and when I click on it the computer connects immediately.
    Obviously this defeats the point of remembering preferred networks and is a nagging time-suck at the start of each work session. Has anyone else experienced this problem and discovered a solution?
    Thanks!!
    Joseph
    Washington, DC

    Hello Joseph_DC
    If you are having issues with it not connecting after waking from sleep, the check out the article below to troubleshoot the issue further. Check in the section Symptom: The network connection drops unexpectedly and there will be a solution just for that issue and will continue with going into Keychain Access the
    iPhone: Troubleshooting No Service
    http://support.apple.com/kb/ts4429
    Regards,
    -Norm G.

  • Airport doesn't automatically connect to my preferred network

    I had my hard drive replaced and ever since my airport doesn't automatically connect to my wifi network. I have specified my network as my preferred network in my system preferences.
    I need to re-connect to the network manually (ie: I need to select my network form the drop down list) each time I wake my computer up from sleep mode.
    How do I have my airport automatically connect??

    Go to System Preferences then select the Network icon.
    Select the airport adaptor then click advanced
    the first tab "Airport" has all your recent SSID's listed.
    Select the desired network and drag it to the top of the list and check the " Remember Networks this computers has joined."
    Apart from that the next best thing would be to removed all the networks from the list and add that network you wish to join to verify its configuration

  • "By default, join" drop-down doesn't have "Preferred Networks" option

    I use my laptop on two different networks. I would like it to automatically join whichever one is available. The Mac Help has instructions titled "Choosing preferred AirPort networks" with three steps. Step 1 works fine; I can open network preferences and get to the drop-down labelled "By default, join". It says I should then select the option "Preferred networks" from the drop-down. The problem I have is, there is no such option. The drop-down has only one option, labelled "A specific network".
    It works identically on a regular user account and an adminstrator account. I have authenticated.
    Tiger 10.4.8, fully updated.

    Can't find the TIL again... might have it bookmarked at work though, but that's the problem... Sorry can't remember the fix right now at all.

  • Macbook Pro no longer auto-connects to preferred network

    The title says it.
    While my computer connects automatically to some (maybe all but one) of my preferred networks, it now does not connect, annoyingly, to the one I use the most often (let's call it NET).
    I've triple checked that it's preferred and should connect automatically, and the computer remembers the password, so that if I manually select NET, it connects no problem. But:
    a) It won't auto-connect to NET, and
    b) If I turn my computer on, when it presents the list of networks to me, I have to wait for it to reload the list, cause if I click on NET originally, it doesn't connect, and I have to refresh the list and try again.
    c) Figured that might mean that it's just taking longer to load the networks and is showing me a list before it's actually picked up on the networks, but waiting forever doesn't make it autoconnect; it just refreshes the list.
    Any ideas? This is a huge pain.

    No idea. You could try deleting the file
    /Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist
    ... and restart your Mac.
    To find that file quickly, select the above path (triple-click the line), control-click to bring up the contextual menu, and select Services > Reveal. Drag that file to the Desktop, or directly to the Trash.
    This will completely erase your AirPort network preferences, requiring that you select your Wi-Fi network and authenticate again.
    What OS X version are you using, and are you using an Apple AirPort Base Station, or a third party product?

  • [Solved] Network doesn't work after hibernate?

    Hello!  This is my first legit Linux install so excuse me if I'm a bit slow.  I installed Arch last night and everything went smoothly.  However, after I tested out hibernate on my machine, the network doesn't seem to work.  Just prior to the hibernate, I installed Pidgin and Skype but they worked alright, so I think that the hibernate caused a problem on eth0.
    I have an Asus P8Z68-V Pro motherboard with an Intel 82579V Gigabit Ethernet Controller that's using the e1000e driver.  Running "dmesg | grep e1000e" says that it is up.
    I'm not entirely clear here, but from reading, I think that I have several ways of connecting to the network, including network, dhcpcd, networkmanager, and wicd.  I am using wicd so I did the following (or at least I think I am only using wicd):
    #rc.d stop network
    #rc.d stop dhcpcd
    #rc.d stop networkmanager
    Similarly, I put a ! in front of network in rc.conf:
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
    # startup and during the boot process. If set to 'no', the C locale is used.
    # HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # Note: Using "localtime" is discouraged, using "" makes hwclock fall back
    # to the value in /var/lib/hwclock/adjfile
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # Note: if unset, the value in /etc/localtime is used unchanged
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.UTF-8"
    DAEMON_LOCALE="no"
    HARDWARECLOCK="UTC"
    TIMEZONE="America/New_York"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
    # Replace every !module by an entry as on the following line in a file in
    # /etc/modprobe.d:
    # blacklist module
    # See "man modprobe.conf" for details.
    MODULES=()
    # Udev settle timeout (default to 30)
    UDEV_TIMEOUT=30
    # Scan for FakeRAID (dmraid) Volumes at startup
    USEDMRAID="no"
    # Scan for BTRFS volumes at startup
    USEBTRFS="no"
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="Vicious"
    # Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
    # Wired network setup
    # - interface: name of device (required)
    # - address: IP address (leave blank for DHCP)
    # - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
    # - broadcast: broadcast address (ignored for DHCP) (optional)
    # - gateway: default route (ignored for DHCP)
    # Static IP example
    # interface=eth0
    # address=192.168.0.2
    # netmask=255.255.255.0
    # broadcast=192.168.0.255
    # gateway=192.168.0.1
    # DHCP example
    # interface=eth0
    # address=
    # netmask=
    # gateway=
    interface=eth0
    address=
    netmask=
    broadcast=
    gateway=
    # Setting this to "yes" will skip network shutdown.
    # This is required if your root device is on NFS.
    NETWORK_PERSIST="no"
    # Enable these netcfg profiles at boot-up. These are useful if you happen to
    # need more advanced network features than the simple network service
    # supports, such as multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    # If something other takes care of your hardware clock (ntpd, dual-boot...)
    # you should disable 'hwclock' here.
    DAEMONS=(hwclock syslog-ng dbus !network netfs crond wicd)
    Restarting eth0 through wicd-cli still did not work.  I also tried resuscitating the network via instructions on the configure network page before trying to focus solely on wicd.
    I found a few similar problems on the forums by searching "wicd hibernate" and tried several solutions but they did not work.  Several problems seem to be that the network doesn't work after a suspend because I guess the stuff in RAM did not get saved?  But people were able to restart the network by running "/usr/lib/wicd/autoconnect.py" and I wasn't able to get this to work.  As a final effort, I added "resume" into mkinitcpio.conf and placed the machine into sleep again to see if it may magically reset something but of course this did not happen .
    mkinitcpio.conf:
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run first, so it may be used to
    # override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten if already added)
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options
    # like so:
    # FILES="/etc/modprobe.d/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect pata scsi sata filesystems"
    ## This is identical to the above, except the old ide subsystem is
    ## used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev pata mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    HOOKS="base udev autodetect pata scsi sata resume filesystems usbinput"
    # COMPRESSION
    # Use this to compress the initramfs image. With kernels earlier than
    # 2.6.30, only gzip is supported, which is also the default. Newer kernels
    # support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
    # compression.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    Not sure if my fstab.conf is useful but if this has something to do with settings getting "lost" in swap, here it is.  Linux is on an SSD and HDD (sda and sdc) and Windows 7 is on a HDD (sdb).
    fstab.conf:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /tmp tmpfs nodev,nosuid,noatime,size=2000M,mode=1777 0 0
    /dev/sda1 / ext4 defaults,noatime,discard 0 1
    /dev/sda2 /home ext4 defaults,noatime,discard 0 2
    /dev/sdc1 /boot ext4 defaults 0 1
    /dev/sdc2 /var ext4 defaults 0 0
    /dev/sdc3 swap swap defaults 0 0
    /dev/sdc4 /media/data ext4 defaults 0 0
    shm /dev/shm tmpfs nodev,nosuid,size=10G 0 0
    Is wicd causing these problems or did I configure something else improperly?  Would appreciate any help to get eth0 up again!
    Last edited by TheBigCow7 (2011-09-13 17:57:20)

    Ok, I think I've made some progress!  Hibernate definitely affects my network connection.  Could this be a kernel 3.0 problem?
    I noticed that ifconfig showed eth0 without an inet addr, just an inet6 addr for the longest time.  e1000e seemed to be loading up ok.  I'm not certain here, but I think that meant the dhcp settings didn't stick, or something along those lines.
    Trying to use dhcpcd like the instructions here did not work.  By some chance, one attempt did work and while it did, I downloaded and installed dhclient.  After that one successful attempt, renewing the DHCP lease via dhcpcd did not work again.
    Luckily though, I found that running "dhclient eth0" worked.  My DHCP settings seemed to have somehow gotten messed up after my initial, problematic hibernate to the point where none would stick, even after a reboot.  Manually typing in "dhclient eth0" would get eth0 working, so I decided to add it to the bottom of /etc/rc.local, like in the example on the networking page.
    Now, eth0 works after a boot.  However, after the daemons load up during the boot process, my computer takes a long time to get to the login prompt (this is relatively speaking, since I am on a SSD and the boot process used to be blazing fast before).  I'm pretty sure it's because I added "dhclient eth0" to /etc/rc.local.
    I should say that even with these changes, after a hibernate, my eth0 still does not work and if it weren't for the edit to /etc/rc.local, eth0's inet settings would still not stick after a reboot (that is to say, the hibernate does do something to my network settings). 
    Is this the correct/most efficient way to fix my DHCP problem?  Can I fix my "eth0 after hibernate" issue?  Also, can I make my DHCP settings boot up without changes to /etc/rc.local so that I can get a fast boot again (still not sure how it was able to work before without my edit)?

  • WiFi Sense Not Very Sensible - Preferring Public Hotspots over Preferred Networks

    When I am out and about WiFi Sense is really good as it automatically connects to public hotspots and I only need to open a browser and press ok, etc.
    However when at home I have BT and have set up my own WPA network connection but the router also has BT WiFi on it and even though I am connected to my home WPA connection and it is a "preferred network" and set to be connected to automatically
    why does the phone keep disconnecting at regular intevals reverting back to the BT WiFi connection?
    When the phone switches to BT WiFi the internet is blocked until you sign into a web portal so as a result the phone uses up all my data connection as it reverts to 3G/4G and also the push email stops working.
    So is there no way that WiFi Sense could be more "sensible" and connect to my preferred network in preference to the public hotspot then only connect to the public hotspot if no preferred networks are available?
    I have friends who have Windows Phones and BT internet and have the same issue as well.
    Thanks
    Robin
    Robin Wilson

    You are welcome. I'm glad you got it back up.
    (1) You say you did the symbolic link. I will assume this is set correctly; it's very important that it is.
    (2) I don't know what you mean by "Been feeding the [email protected] for several weeks now, 700 emails each day at least." After the initial training period, SpamAssassin doesn't learn from mail it has already processed correctly. At this point, you only need to teach SpamAssassin when it is wrong. [email protected] should only be getting spam that is being passed as clean. Likewise, [email protected] should only be getting legitimate mail that is being flagged as junk. You are redirecting mail to both [email protected] and [email protected] ... right? SpamAssassin needs both.
    (3) Next, as I said before, you need to implement those "Frontline spam defense for Mac OS X Server." Once you have that done and issue "postfix reload" you can look at your SMTP log in Server Admin and watch as Postfix blocks one piece of junk mail after another. It's kind of cool.
    (4) Add some SARE rules:
    Visit http://www.rulesemporium.com/rules.htm and download the following rules:
    70sareadult.cf
    70saregenlsubj0.cf
    70sareheader0.cf
    70sarehtml0.cf
    70sareobfu0.cf
    70sareoem.cf
    70sarespoof.cf
    70sarestocks.cf
    70sareunsub.cf
    72sare_redirectpost
    Visit http://www.rulesemporium.com/other-rules.htm and download the following rules:
    backhair.cf
    bogus-virus-warnings.cf
    chickenpox.cf
    weeds.cf
    Copy these rules to /etc/mail/spamassassin/
    Then stop and restart mail services.
    There are other things you can do, and you'll find differing opinions about such things. In general, I think implementing the "Frontline spam defense for Mac OS X Server" and adding the SARE rules will help a lot. Good luck!

  • Preferred Networks by Location in Mavericks

    Back in Snow Leopard, preferred WiFi networks were stored separately, in different lists according to the location chosen.
    That worked great because I have 2 routers at home, one for my ISP and one for my VPN.
    When connected trough the ISP router, the DNS Servers are chosen automatically.
    If I want to connect trough the VPN router, I must specify the DNS Servers, for example OpenDNS.
    So I had 2 locations, one for each router.
    When I chose either one of the locations, it automatically connected me to its respective router.
    It also worked for assigning Static IP addresses for the computer, a different one for each router.
    The problem with Mavericks is that all Preferred Networks are listed together, and not grouped by Location as it was in OSX 10.6
    Now It's a mess. I have to manually choose my desired network.
    The problem is that if the other network comes out first in the list, the computer will connect to it.
    If it doesn't match my chosen location, I will then have incompatible IP and DNS settings for that router.oes
    Does someone else have this problem?
    Is there a way to revert to the way Snow Leopard handled Preferred Networks?
    Thanx!

    I wish I would have taken a screenshot. The "kind" option is back after a reboot. Grrr.

  • How to choose the "preferred Network"

    My phone automatically defaulted to "Global mode". Is this correct or should it be in CDMA or GSM/UMTS mode? Also, does this affect my ability to send text messages b/c I haven't been able to send them with this phone and tech support doesn't seem to be able to resolve my issue.
    Thanks!

    jaxgirl3278 wrote:
    My phone automatically defaulted to "Global mode". Is this correct or should it be in CDMA or GSM/UMTS mode? Also, does this affect my ability to send text messages b/c I haven't been able to send them with this phone and tech support doesn't seem to be able to resolve my issue.
    Thanks!
    Hi jaxgirl3278,
    You can change your preferred network to CDMA by following the instructions below:
    From a home screen, select the applications tab (located in the lower left).
    Select Settings.
    Select Wireless & networks.
    Select Mobile networks.
    Select Preferred Networks.
    Select CDMA.
    Also make sure that Enable always -on mobile data box is checked. 
    Global mode does not interfere with text messaging and you should be able to send your messages. In order for our forum members to assist you please provide some more information.
    Are you able to receive text messages?
    Are you able to send any text messages at all to any of your contacts?
    Do you use the native text messaging application or a third party text messaging application?
    Have you ever added a messaging block feature to your account?
    Please keep in mind that in order to resolve text messaging issues your account may need to be accessed and feature re-provisioned and our forum members may not be able to resolve this issue for you. If you prefer to send me a private message including your name and wireless number I will be happy to review

  • Deleted preferred networks reappear

    Upon installing Mavericks, and turning on iCloud keychain, I noticed that all wifi networks I had ever connected to appeared in the preferred network list on my Macbook.
    There were quite a few I naturally wanted to delete, so I removed them. Also my devices were trying to connect to networks I thought I had removed.
    It didn't take me long to notice that my Macbook was trying to connect to some of these old networks again, and upon looking at the list - all deleted entries had reappeared.
    Another symptom seems to be that if I tell my iPhone not to auto-connect to a public hotspot (BT WIFI for example), if my Mac ever comes near that hotspot it auto connects - as will my iPhone subsequently.
    I have tried editing the com.apple.airport.preferences.plist file manually, deleting the Mac's WiFi service and recreating, and resetting network settings on all my Apple devices.
    I have even looked at the Keychain app on my Mac, but it doesn't seem to be storing my wireless networks from what I can see.
    From my Google-ing, it doesn't sound like anyone else is having this issue..
    Any ideas?
    Thanks!

    Back up all data. Open the iCloud preference pane and uncheck the Keychain box. You'll be prompted to delete the local iCloud keychain. Confirm. Also disable it on the other devices. Delete the unwanted preferred networks from all devices. Then follow one of the procedures described in this support article to set up iCloud Keychain.

  • Won't connect to preferred network automatically

    In the last week, my Macbook suddenly doesn't connect to my preferred network (top of the list) automatically. Rather I sometimes I have to turn airport on and off once or twice and it usually connects to another network first. Suggestions?

    Seems to have been fixed in an update. I currently run Mountain Lion and had forgotten I ever had this issue.

  • Airport Time Capsule: None of your preferred networks are available

    Just got the brand new MBA and an AirPort Time Capsule and set-up went fine, except that whenever my MBA goes to sleep and I open it back up, I've lost my wireless connection and get the message "None of your preferred networks are available."  My network is among those available in the list, and it remembers my password, but I must select it every single time.  Why won't it remember my preferences and automatically find my network.  I shelled out $300 for this Time Capsule because it was supposed to be "lightening fast".  My $45 Vizio router had me connected all the time - much faster, wouldn't you agree?

    Make sure the box next to Remember networks this computer has joined is checked.
    No other boxes should be checked.
    Click OK, then click Apply.
    It is easy to miss "Apply", and if you do, the settings will not "stick" on the Mac.
    Restart the Mac.
    Hopefully, your new Time Capsule network name does not use the same name of a previous network. That will really confuse things. If that is the case, use a new wireless network name and a new password for the Time Capsule.

  • All options whited out with preferred network

    Every time I restart my computer (which has been needed quite often lately) it doesn't remember the preferred network and tries to connect with
    Xfinity.  Almost as if Xfinity is somhow intercepting my network in order to get me to join.  When I go to settings and networks and WiFi, all the options such as preferred networks.

    kinofrad wrote:
    When I go to settings and networks and WiFi, all the options such as preferred networks.
    I do not know what this means.
    Go to System Preferences > Networks.  Click the "Advanced" button.  Choose the "WiFi" tab.  You can move the networks into your preferred order there.

  • Cannot add preferred networks in network preference

    Dear all,
    I have a quite strange problem after someday. Every time I switch AirPort on, I have to choose the wireless network from the list available, and the computer doesn't join the right network automatically.
    I went to Network -> AirPort -> Advanced, and I found the reason is that there is no preferred network stored there. Even I chose the option "remember networks this computer has joined", the computer couldn't remember any wireless network I joined. Then I tried to add a known network manually, but System Preferences just kept quitting unexpectedly after I clicked "OK" to save the network I just added.
    Any ideas why this happened?
    Many thanks,
    Xiaowen

    Then try a simple reset of you wireless connections. Just disconnect to any wireless connections. Then go to System Preferences (in your Dock)->Network pane and at the top of that pane use the drop-down "Location". Create a new Custom Location calling it whatever you want. Then at the bottom of the Network pane click on the 'Apply' button to save your new Location. Lastly rejoin your wireless network and see if it is add or you can manually add one.

Maybe you are looking for