Joining a private network by default?

I've set up my network at home on an Airport Extreme as a private network, which my wife and I both use. The privacy is the security, there's no password (it's easier for the wireless printer that way).
My problem is, I have to manually join the network each time I wake the machine from sleep or boot up - how can I get it to "remember" the private network name?

Hello lexrudolf,
And welcome to Apple Discussions!
Have you make sure you have enabled the "Remember any network this computer has joined" option is ticked from under the Network category of System Preferences.
To check, head to *System Preferences* -> Network and then you will need to first provide your credentials to unlock the pane to make changes, then hit the Advanced button. From there, you will be under the Airport tab which is where you will find this option.
Hope it helps.
B-rock

Similar Messages

  • By default: join a specific network

    I was using 128 bit WEP until just tonight when I got a new wireless router which does WPA. While using the WEP encryption, my computer was set to join my wireless network by default. This worked perfectly, upon restarting my computer it would automatically reconnect to the internet and all.
    Ever since the change to use the new key and WPA, when the computer restarts it does not automatically join the network any longer. In the network tab of system preferences everything is set to automatically join the network, but it doesn't. I know the settings to join the network are correct because when I choose the network from the airport menu item at the top of the Finder, it connects no problem without asking for any keys or passwords of any kind.
    Any ideas?
    I would like to have this work properly as I run a server off of my machine and need it to be running in the even I should lose power and the machine restarts while I'm not home.

    I've got a similar problem. Everything was fine and then I accepted a software update for iTunes and Quicktime. Now, my Mac won't connect to my network automatically. It's a 128 bit WEP key, and I've gone into network connections to verify the "specific network" settings. Seems like it doesn't want the 26 character key.

  • How to set up TimeCapsule (4th) to create own private (wired) network behind Airport Express (5th) that is set up to join existing wifi-network of fritz adsl modem/router?

    I work in an office building with free Wifi to connect to the Internet. I want to be able to use this internetconnection, but at the same time I want to shield of my own wired network.
    I've made the following configuration:
    - fritz adsl modem / router
    - Airport Extreme (5th gen) set up to join existing wireless network (green light, works)
    - Lan-cable from lan-port AE to wan-port TC (4th gen)
    - Lan-cable from TC to Mac
    - Lan-cable from TC to Printer
    When I set my TC (network-settings) in bridge-mode everything works fine, but my Mac and Printer get an IP-address from the fritz modem / router and are visible to others.
    I tried to set TC in NAT/DHCP-mode, but then I get the error message that I should set a static IP-adress for TC. When I set TC in DHCP-mode, it looses connection to the AE. I'm not sure what to do now. Does anyone know how to set up my TC and create my own private network and still be able to get on the internet?

    Hajenius wrote:
    Is there a better alternative? I'd rather not want to reset my TC every day.
    You are using free internet.. so there is a price to pay.. that is convenience and non-ideal network setup.
    The better alternative is to pay for your own connection. Then you are completely free of the possibility of others in the bullding seeing your connection. (as long as you secure the wireless).
    But I think you are probably over worrying about public wifi.. if it is setup right.. ask the building admins.. it should be setup so each user cannot see another users connection. This is typical for most wifi setup and simply means you can see internet connection but nobody else on the connection. ie other wireless users.
    Having a router with NAT makes it then more secure again and allows clients on your own network to interact with each other. But you can setup wireless to the free wifi for every client.. (depending on how many IP you are allowed).. and run a secondary network without internet access. This is easy for desktop etc where you have a wireless and a wired connection but less convenient for mobile devices.. unless you use a cloud connection and each client can link and share via that.
    Have I made the explanation worse??
    Think of it this way.. if you had 3 laptops.. all 3 could connect to the internet from the building wifi.. but they cannot talk to each other or share resources in local office. You can put resources out in the cloud, that can be shared.. but that adds traffic and most free services are not fast.
    Now you can also plug all three into Time Capsule by ethernet.. and share local resources. Files, printers backup etc. This network is not connected to the internet at all. Each laptop has internet via free wifi and local connection.
    For devices like iphones that have no ethernet or other method.. you could use local wireless and public wireless.. but in turns.. still the only advantage is less issues with double NAT.. if that causes problems.. then this is an alternative.

  • Yammer: How to make an External Network the default network to where to join?

    Can I make an external Network the default Network which users join when the join Yammer. By default it's the Home Network (home domain) which they join when they register in Yammer.

    Hi Freedomic,
    Seems you've posted the same question in Office 365 Communit Yammer forum. Our Yammer support engineer
    Jonathan Lee has provided a reply to your question there, could you please take a look and see if it's helpful for you?
    Thread link:
    http://community.office365.com/en-us/f/176/t/294326.aspx
    If you have any further questions about this, I would suggest you stick with that thread in
    Office 365 Community Yammer forum as here in this forum, we only discuss questions and feedback for Microsoft Office client.
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
    Regards,
    Ethan Hua
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • I am using a verizion jetpack to wireless connect to an airport express next i want to connect a Airport extreme wired from toe express to create a second private network that has internet access via the jetpack

    Thanks for the help after looking over your sugesstion I did some additional troubleshooting which i should have done in the beginning and heres what i found
    Airport express is joined to and existing wireless network and i have internet access....all good
    I set up my Airport Extreme as follows:
                        Connect using :ethernet
                  Ethernet Wan Port : automatic
                  Connetion Sharing : Share a public IP address
    Tcpip      Configue IPv4: Using DHCP
    DHCP                   Begin address: 172.16.22.200
                               Ending address:  172.16.22.254
    Wireless    Create a wireless network
                             Wireless network name Test1
                              wpa2 security
    This is needed due to set ip address of device on this private network did not address NAT
    Conneted Express ethernet port to Extreme wan port
    All wired devices have internet access and i get a double nat status which ignore
    however my wireless device will not connect.... sometimes they will they want
    any suggestions

    Here are sceeen shots of the Express

  • How do I get a 1st generation time capsule to join a wifi network?

    OK, I've searched the groups but no luck.  Here's my situation;
    I'd like to configure a 1st generation time capsule to join a wifi network ideally with a printer attached to the USB.  My set up is an iMac running 10.9.3, Airport Utility 6.3.2 and a 1st Generation TC with the latest firmware (7.6.4).  I'm trying to connect it to an ADSL Wifi Modem/Router.  I know a cabled connection would give better performance but want a wifi only connection as the printer is in a different room.
    I've disabled the network functions (bridge mode) but I can only see wireless options to Create a Wireless Network, Extend a Wireless Network or Off, not to Join.  If I try to extend I get the option to add an SSID, security & passwords but it doesn't seem like parameters to join  -the drop-down doesn't list available networks to join & manually entering the main wifi network and password doesn't work.
    Is my desired config even possible?
    Dave

    Something.....a Mac or PC will need to have a 5.x version of AirPort Utility installed on the computer.
    Perform a factory default reset on the Time Capsule by powering it off for a few minutes. Then, hold in the reset button first and keep holding for an additional 10-12 seconds while you simultaneously plug the power back into the Time Capsule. Release the reset button after the hold period and allow a full minute for  the Time Capsule to restart to a slow, blinking amber light.
    Open up AirPort Utility on the computer, select the Time Capsule and click Manual Setup
    Click the Base Station tab below the row of icons to type in a device name and password that you want to use for the Time Capsule, set Time Zone, etc.
    Click the Wireless tab next to the Base Station tab
    Hold down the option or Alt key while you click on the Wireless Mode setting box
    Select the Join a wireless network setting
    Select the name of the wireless network
    Enter the password for the wireless network
    Verify the password
    Click Update to save the settings
    Note....everything here assumes that the router that provides the wireless network is using WPA2 Personal security, which is the default setting for the Time Capsule.

  • IP routing utilizing Verizon private network (GRE tunnel) with remote cellular gateways

    Okay, I give up, and think I have done my due diligence (I have been engrossed and fascinated spending many more hours than allotted to try and learn some of the finer details).  Time for some advice.  My usual trade is controls engineering which generally require only basic knowledge of networking principals.  However I recently took a job to integrate 100 or so lift stations scattered around a county into a central SCADA system.  I decided to use cellular technology to connect these remote sites back to the main SCADA system.  Well the infrastructure is now in and it’s time to get these things talking.  Basic topology description is as follows:  Each remote site has an Airlink LS300 gateway.  Attached to the gateway via Ethernet is a system controller that I will be polling via Modbus TCP from the main SCADA system.  The Airlinks are provisioned by Verizon utilizing a private network with static IP's.  This private networks address is 192.168.1.0/24.  Back at the central office the SCADA computer is sitting behind a Cisco 2911.  The LAN address of the central office is 192.168.11.0/24.  The 2911 is utilizing GRE tunnels that terminate with Verizon.  The original turn up was done with another contractor that did a basic config of the router which you will find below.  As it stands now I am pretty confident the tunnels are up and working (if I change a local computers subnet to 255.255.0.0 I can surprisingly reach the airlinks in the field), but this is obviously not the right way to solve the problem, not to mention I was unable to successfully poll the end devices on the other side of the Airlinks.  I think I understand just about every part of the config below and think it is just missing a few items to be complete.  I would greatly appreciate anyone’s help in getting this set up correctly.  I also have a few questions about the set up that still don’t make sense to me, you will find them below the config.  Thanks in advance.
    no aaa new-model
    ip cef
    ip dhcp excluded-address 10.10.10.1
    ip dhcp pool ccp-pool
     import all
     network 10.10.10.0 255.255.255.248
     default-router 10.10.10.1 
     lease 0 2
    ip domain name yourdomain.com
    no ipv6 cef
    multilink bundle-name authenticated
    username cisco privilege 15 one-time secret 
    redundancy
    crypto isakmp policy 1
    encr 3des
    hash md5
     authentication pre-share
     group 2
    crypto isakmp key AbCdEf01294 address 99.101.15.99  
    crypto isakmp key AbCdEf01294 address 99.100.14.88 
    crypto ipsec transform-set VZW_TSET esp-3des esp-md5-hmac 
    mode transport
    crypto map VZW_VPNTUNNEL 1 ipsec-isakmp 
     description Verizon Wireless Tunnel
     set peer 99.101.15.99
     set peer 99.100.14.88
     set transform-set VZW_TSET 
     match address VZW_VPN
    interface Tunnel1
     description GRE Tunnel to Verizon Wireless
     ip address 172.16.200.2 255.255.255.252
     tunnel source 22.20.19.18
     tunnel destination 99.101.15.99
    interface Tunnel2
    description GRE Tunnel 2 to Verizon Wireless
     ip address 172.16.200.6 255.255.255.252
     tunnel source 22.20.19.18
     tunnel destination 99.100.14.88
    interface Embedded-Service-Engine0/0
     no ip address
     shutdown
    interface GigabitEthernet0/0
     description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$
     ip address 10.10.10.1 255.255.255.248
     shutdown
     duplex auto
     speed auto
    interface GigabitEthernet0/1
     ip address 192.168.11.1 255.255.255.0
     duplex auto
     speed auto
    interface GigabitEthernet0/2
     ip address 22.20.19.18 255.255.255.0
    duplex full
     speed 100
     crypto map VZW_VPNTUNNEL
    router bgp 65505
     bgp log-neighbor-changes
     network 0.0.0.0
     network 192.168.11.0
     neighbor 172.16.200.1 remote-as 6167
     neighbor 172.16.200.5 remote-as 6167
    ip forward-protocol nd
    ip http server
    ip http access-class 23
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    ip route 0.0.0.0 0.0.0.0 22.20.19.19
    ip access-list extended VZW_VPN
     permit gre host 99.101.15.99 host 22.20.19.18
     permit icmp host 99.101.15.99 host 22.20.19.18
     permit esp host 99.101.15.99 host 22.20.19.18
     permit udp host 99.101.15.99 host 22.20.19.18 eq isakmp
     permit gre host 22.20.19.18 host 99.101.15.99
     permit gre host 22.20.19.18 host 99.100.14.88
    access-list 23 permit 10.10.10.0 0.0.0.7
    control-plane
    end
    So after spending countless hours analyzing every portion of this,  I think that adding one line to this will get it going (or at least closer).
    ip route 192.168.1.0 255.255.0.0 22.20.19.19
    That should allow my internal LAN to reach the Airlink gateways on the other side of the tunnel (I think)
    Now for a couple of questions for those that are still actually hanging around.
    #1 what is the purpose of the Ethernet address assigned to each tunnel?  I only see them being used in the BGP section where they are receiving routing tables from the Verizon side (is that correct?).  Why wouldn't or couldn't you just use the physical Ethernet address interface in its place (in the BGP section)?
    #2 is the config above correct in pointing the default route to the physical Ethernet address?  Does that force the packets into the tunnel, or shouldn’t you be pointing it towards the tunnel IP's (172.16.200.2)?  If the config above is correct then I should not need to add the route I described above as if I ping out to 192.168.1.X that should catch it and force it into the tunnel where Verizon would pick it up and know how to get it to its destination??
    #3 Will I need to add another permit to the VZW_VPN for TCP as in the end I need to be able to poll via Modbus which uses port 502 TCP.  Or is TCP implicit in some way with the GRE permit?
     I actually have alot more questions, but I will keep reading for now.
    I really appreciate the time you all took to trudge through this.  Also please feel free to point anything else out that I may have missed or that can be improved.  Have a great day!

    This post is a duplicate of this thread
    https://supportforums.cisco.com/discussion/12275476/proper-routing-lan-through-verizon-private-network-gre-airlink-gateways
    which has a response. I suggest that all discussion of this question be done through the other thread.
    HTH
    Rick

  • Certificate error when connecting to RemoteApp outside of private network

    I have a server running Windows Server 2012 R2. It is configured as an all-in-one RDS server - all roles are installed on it. We've configured it primarily to use an application as a RemoteApp - the application is hosted at a different site, and this RDS
    server is at that site. We have a site to site VPN set up, so that it is all a part of our domain. The issue I'm having seems related to the fact that our internal network is .local, but the certificate only has a single .com name, so that we can access it
    from the Internet.
    Everything works, though what I'm trying to clear up is a certificate error. When connecting to the RemoteApp from outside of our private network, we get the error "The server name on the certificate is incorrect." This occurs after entering
    credentials.  The public name of the server (rds.contoso.com) is different from the private name (server.contoso.local).  We can proceed through the error and connect (though we'd like to fix it).
    I implemented a fix that I found elsewhere to try to fix this.  This was to add a custom RDP setting like so:
    Set-RDSessionCollectionConfiguration –CollectionName QuickSessionCollection -CustomRdpProperty "use redirection server name:i:1`nalternate full address:s:rds.contoso.com"
    That seemed to make some progress, then we got another error.  I made a change to the RD RAP in RD Gateway Manager - by default, it allowed access to Domain Computers (which rds.contoso.com did not exist as a domain computer). I modified it to allow
    access to the rds.contoso.com name.
    I now receive a different error message and that's where I'm stuck.  The heading on the message is RemoteApp Disconnected.  The text of the error is 'Remote Desktop can't find the computer "rds.contoso.com".  This might mean that
    "rds.contoso.com" does not belong to the specified network.  Verify the computer name and domain that you are trying to connect to.'
    Any thoughts on what I can do next?  When I roll back the changes I've made, I'm again able to connect fine, I just have the certificate error again.

    Hi,
    1. For changing the published FQDN I recommend you use Set-RDPublishedName cmdlet instead setting a custom rdp property on the collection:
    Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
    https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
    2. As you mentioned before you need to edit the RD RAP so that the FQDN that you are using is permitted, or set it to Allow users to connect to any network resource.
    3. On your internal network (internal to the RDG), you need to create a DNS A record for the published FQDN (rds.contoso.com) that points to your server's private ip address. 
    I'm not sure how you have things configured right now in terms of network and DNS so it is tough to give you instructions on how to fix.  Let me explain a bit.  Normally with a VPN you would not need RD Gateway, although it is okay
    if you want to use it.  If you have things configured properly an external client will normally connect to the RDG using the FQDN specified for RDG, then the RDG will connect to the published FQDN for the RDS deployment.
    In your case these two FQDNs would be the same, only when the client does a DNS lookup it should get the ip address that you want users to connect to for the RDG whereas when the RDG does a DNS lookup it should get the private ip address of the server. 
    Exactly how you need to configure your DNS entries will depend on your VPN and networking configuration.
    Please give it a try using the information provided above and reply back here with your results and any further questions you may have.
    Thanks.
    -TP

  • Joining an existing network as a client

    I've had an Airport Express for about 3 years...recently needed to reconfigure because of upgrade to my Belkin wireless router security.
    I need the steps to join an existing network as a client, including providing the WPA password. I've been throught the setup guides...have gotten as far as a) connecting to the network using the Windows utility
    b) seeing the AEBS in the Airport Admin utility
    ....but from this point, I'm lost.
    Windows XP Home, SP2.
    Thank you.

    Hello showbizkid41. Welcome to the Apple Discussions!
    To set up the AirPort Express Base Station (AX) as a "Wireless Client," using the AirPort Admin Utility, either connect to the AX's wireless network or temporarily connect your computer directly (using an Ethernet cable) to the Ethernet port of the AX, and then, try these settings:
    AirPort tab
    o Base Station Name: <whatever you wish or use the default>
    o Wireless Mode: Join an Existing Wireless Network (Wireless Client)
    o Wireless Network: <type in your wireless network name or select it from the pop-up menu>
    o Wireless Security: WPA Personal
    o Password: <enter your wireless network security password or key>

  • How to set a network as "default"

    I have an Airport Express.. I created my network, but each time I turn on my computer, it chooses someone elses..
    Is there some way to set my own network as the "Default" ?
    Thanks,
    Awfers

    First, create a new Location with your WiFi as the "Preferred Network."
    Create a new network Location w/Preferred Network
    o System Preferences > Network > Show > AirPort
    o Location: New Location...
    o Name your new location: <enter a location name>
    o Click "OK"
    o Click on the "AirPort" tab to select it.
    o By default, join: Preferred networks
    o Select a "preferred" network from the list, or click "+" to add a new one.
    o Click "Options..."
    o If no preferred networks are found: Ask before joining an open network.
    o Click "OK"
    o Click "Apply Now"
    Second, setup AirPort to default to the "Preferred Network."
    System Preferences > Network > Show > Network Port Configurations
    o Verify that AirPort is "On" (checked)
    Systems Preferences > Network > Show > AirPort
    AirPort tab
    o By default, join: Preferred networks

  • 2012R2 DC private network

    Disaster recovery scenario. 
    The domain controller has been backed up with proper VSS aware backup. 
    Restore the virtual machine to a target off-site datacenter. 
    Boot the VM and it is identified on a "Public/Private" network, hence it's not working at all. 
    Doesn't seem to matter what I do, it simply refuses to come online as "Domain Network". 
    My question is this: 
    How exactly does the NLS identify the domain network? 
    Things I tried already. 
    Disable/Enable NIC
    Set the awareness service to delayed start. 
    Manually removed all the network profiles from the registry, forcing a new identification. 
    Start up a 2003 DC before booting the 2012R2 DC. 
    Manually enable Network discovery on all network types. 
    Tried resetting the ipv4 stack with netsh. 
    The default gateway on the server does NOT reply to PING. 
    Is that necessary? 
    Any tips are greatly appreciated.

    In some instances, VMM cannot determine the network location by using NLA. This happens when a loopback adapter is used because it is not part a network, and on ESX Servers because the operating system on ESX Server hosts does not have an NLA feature. In
    these cases, you can manually enter the network location by selecting the
    Override discovered network location check box and then typing a name for the network location in the
    Network location box.
    https://technet.microsoft.com/en-us/library/ee236499.aspx
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • IBook - error joining the Airport Network

    Sorry for the repost but I wasn't sure if me accidently hitting the Correct Answer button would have effected getting a reply
    Excuse my ignorance but I've never had a Mac. I recently got this from a friend and I'm having trouble getting it to connect to my WiFi. I've tried everything I could find on google, but nothing has worked. I've made sure my router isn't filtering Mac addresses, I've tried the $ fix, I've removed and changed my security preferences mutiple times, and I'm out of things to try. It works fine when it's connected to the modem directly, but wireless just won't connect. Every time I try I get the error joining the Airport network "xxxxx" but the computer I'm using to type this is connected just fine. Any help would be much appreciated!!
    I belive it's a
    iBook G3/800 (32 VRAM - Tr)
    if not that one then it's a
    iBook G3/800 (Early 2003 - Op)
    I really know nothing about Macs so I don't know how to tell which one of those it is
    Clicking the About This Mac option says...
    Processor 800 MHz Power PC G3
    Memory 384 MB SDRAM
    Machine Model PowerBook4,3
    CPU Type PowerPC 750 (2.3)

    Right now I have my old ibokk g4 runing OS10.4.11 I'm going to go through the setup on airport using it.I am in system preferences- network. Airport is on and shows in the top menu bar of the desktop.Under show in nework preferences click on network status and then airport. Go to options open and check automaticly join open networks. Click ok. Go to proxies and click. Make sure use passive ftp mode is checked. Go back up and click on the airport bar.  Under by default join-click prefered network. You should now have a window showing all networks available.Click on the one that represents your router and apply. If you network is password protected you will need to inter the password. If this does not work use the assit me option . You can run diagnostics to see if it picks up your network or you can run the assistant. It will ask you to name the network. then continue and check on airport then you will get abox that should show your router and you'll need the password for it. And thenclick apply. You can also get help in network  by clicking the little ?

  • Error joining the AirPort Network - revisited

    I just got my iBook back from the shop and am trying to reestablish the link with my Airport Express. I've reset the unit, gone through numerous hoops.
    The AirPort Express currently has a green light, and my router shows it's connected. Yet, when I try to connect, or try to reconfigure, I get the message "There was an error joining the AirPort network "Apple Network xxxxxx""
    I have no idea what firmware is on the unit, nor do I have the means to update the firmware if needed (as I cannot get a connection to it).
    Yes, I have a good internet connection. I'm posting this on an older iBook ... which is not AirPort ready.
    Thanks in advance!
    Note ... This topic came up in June (2006) ... and is archived, yet unanswered.

    Ciao all.
    I'll tack onto this thread rather than starting a new one. It sounds like similar-ish territory.
    We've had Airport Express for about three weeks after our Airport Extreme gave up the ghost after 14 months. We have a DSL modem connected to Airport Express, and three computers - eMac, iBook G4 and Powerbook G4 - connected wirelessly. Or we did, until tonight.
    On the eMac, I lost my wireless connection. The Airport symbol was still black, and full strength, but my time connected stats disappeared. At the same time, my wife had the same thing happen on her Powerbook. Then the Airport symbol grayed out. As did the Powerbook. I fired up the iBook and the same thing was happening.
    Briefly, for a couple of seconds, the Airport symbol would return to black, with, on a couple of occasions, the time connected stats reappearing. We would be connected again. Then the symbol would gray out again.
    And the network name would have disappeared from the Airport menu.
    If I turned off Airport and turned it on again, the symbol would be greyed out, but the network name would be there. Only, when I tried to connect, I would get the dreaded An Error Occurred Joining The Selected Wireless Network.
    And I couldn't access the Airport Express via either Set Up or Admin.
    I rest the Airport Express back to factory settings. The Airport symbol remained greyed out, but the Apple default wireless network was visible in the Airport menu. But I would still get the dreaded An Error Occurred, etc message.
    Through Airport Set up, I was able to detect the Airport Express' default name and even the network name, but still wasn't able to connect to it.
    Trying again, I was told that no new Airport networks could be found.
    I've had basically the same results trying all three computers.
    In terms of lights, the Express will sit there with a solid green light through all these shenanigans.
    The internet connection is solid. Plugging the modem straight into the computer puts me online.
    Do we have - as I fear - a lemon of an Airport Express after three weeks?
    Hopefully someone can ... help us ...
    TIA
    Mac OS X (10.3.9)
      Mac OS X (10.3.9)  

  • There was an error in joining the airport network networkname

    I am trying to get my daughters iBook (high school provded) connected to my wireless WRT54G. I have cloned my MAC address. My setting at 192.168.1.1 are;
    Mixed
    Channel 11-2.4
    SSID is Enabled
    Security setings are;
    WEP
    Default key is 1
    128 bit
    Passphase - letters
    Key 1 is: 26 Alphanumeric
    When I click on the ibook;
    airport
    network name
    key #
    I receive a message that says: "There was an error in joining the airpor network networkname"
    I am trying to figure out if it the schools settings or an operator error?

    hi... first off make sure that you are entering valid network key... if you are entering valid key in...try setting up $ sign before the network key and try connecting to the network...

  • Proper routing for lan through verizon private network (GRE) to airlink gateways

    Okay, I give up, and think I have done my due diligence (I have been engrossed and fascinated spending many more hours than allotted to try and learn some of the finer details).  Time for some advice.  My usual trade is controls engineering which generally require only basic knowledge of networking principals.  However I recently took a job to integrate 100 or so lift stations scattered around a county into a central SCADA system.  I decided to use cellular technology to connect these remote sites back to the main SCADA system.  Well the infrastructure is now in and it’s time to get these things talking.  Basic topology description is as follows:  Each remote site has an Airlink LS300 gateway.  Attached to the gateway via Ethernet is a system controller that I will be polling via Modbus TCP from the main SCADA system.  The Airlinks are provisioned by Verizon utilizing a private network with static IP's.  This private networks address is 192.168.1.0/24.  Back at the central office the SCADA computer is sitting behind a Cisco 2911.  The LAN address of the central office is 192.168.11.0/24.  The 2911 is utilizing GRE tunnels that terminate with Verizon.  The original turn up was done with another contractor that did a basic config of the router which you will find below.  As it stands now I am pretty confident the tunnels are up and working (if I change a local computers subnet to 255.255.0.0 I can surprisingly reach the airlinks in the field), but this is obviously not the right way to solve the problem, not to mention I was unable to successfully poll the end devices on the other side of the Airlinks.  I think I understand just about every part of the config below and think it is just missing a few items to be complete.  I would greatly appreciate anyone’s help in getting this set up correctly.  I also have a few questions about the set up that still don’t make sense to me, you will find them below the config.  Thanks in advance.
    no aaa new-model
    ip cef
    ip dhcp excluded-address 10.10.10.1
    ip dhcp pool ccp-pool
     import all
     network 10.10.10.0 255.255.255.248
     default-router 10.10.10.1 
     lease 0 2
    ip domain name yourdomain.com
    no ipv6 cef
    multilink bundle-name authenticated
    username cisco privilege 15 one-time secret 
    redundancy
    crypto isakmp policy 1
    encr 3des
    hash md5
     authentication pre-share
     group 2
    crypto isakmp key AbCdEf01294 address 99.101.15.99  
    crypto isakmp key AbCdEf01294 address 99.100.14.88 
    crypto ipsec transform-set VZW_TSET esp-3des esp-md5-hmac 
    mode transport
    crypto map VZW_VPNTUNNEL 1 ipsec-isakmp 
     description Verizon Wireless Tunnel
     set peer 99.101.15.99
     set peer 99.100.14.88
     set transform-set VZW_TSET 
     match address VZW_VPN
    interface Tunnel1
     description GRE Tunnel to Verizon Wireless
     ip address 172.16.200.2 255.255.255.252
     tunnel source 22.20.19.18
     tunnel destination 99.101.15.99
    interface Tunnel2
    description GRE Tunnel 2 to Verizon Wireless
     ip address 172.16.200.6 255.255.255.252
     tunnel source 22.20.19.18
     tunnel destination 99.100.14.88
    interface Embedded-Service-Engine0/0
     no ip address
     shutdown
    interface GigabitEthernet0/0
     description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$
     ip address 10.10.10.1 255.255.255.248
     shutdown
     duplex auto
     speed auto
    interface GigabitEthernet0/1
     ip address 192.168.11.1 255.255.255.0
     duplex auto
     speed auto
    interface GigabitEthernet0/2
     ip address 22.20.19.18 255.255.255.0
    duplex full
     speed 100
     crypto map VZW_VPNTUNNEL
    router bgp 65505
     bgp log-neighbor-changes
     network 0.0.0.0
     network 192.168.11.0
     neighbor 172.16.200.1 remote-as 6167
     neighbor 172.16.200.5 remote-as 6167
    ip forward-protocol nd
    ip http server
    ip http access-class 23
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    ip route 0.0.0.0 0.0.0.0 22.20.19.19
    ip access-list extended VZW_VPN
     permit gre host 99.101.15.99 host 22.20.19.18
     permit icmp host 99.101.15.99 host 22.20.19.18
     permit esp host 99.101.15.99 host 22.20.19.18
     permit udp host 99.101.15.99 host 22.20.19.18 eq isakmp
     permit gre host 22.20.19.18 host 99.101.15.99
     permit gre host 22.20.19.18 host 99.100.14.88
    access-list 23 permit 10.10.10.0 0.0.0.7
    control-plane
    end
    So after spending countless hours analyzing every portion of this,  I think that adding one line to this will get it going (or at least closer).
    ip route 192.168.1.0 255.255.0.0 22.20.19.19
    That should allow my internal LAN to reach the Airlink gateways on the other side of the tunnel (I think)
    Now for a couple of questions for those that are still actually hanging around.
    #1 what is the purpose of the Ethernet address assigned to each tunnel?  I only see them being used in the BGP section where they are receiving routing tables from the Verizon side (is that correct?).  Why wouldn't or couldn't you just use the physical Ethernet address interface in its place (in the BGP section)?
    #2 is the config above correct in pointing the default route to the physical Ethernet address?  Does that force the packets into the tunnel, or shouldn’t you be pointing it towards the tunnel IP's (172.16.200.2)?  If the config above is correct then I should not need to add the route I described above as if I ping out to 192.168.1.X that should catch it and force it into the tunnel where Verizon would pick it up and know how to get it to its destination??
    #3 Will I need to add another permit to the VZW_VPN for TCP as in the end I need to be able to poll via Modbus which uses port 502 TCP.  Or is TCP implicit in some way with the GRE permit?
     I actually have alot more questions, but I will keep reading for now.
    I really appreciate the time you all took to trudge through this.  Also please feel free to point anything else out that I may have missed or that can be improved.  Have a great day!

    My first comment is that you have two posts in this forum and as far as I can tell they are exact duplicates, other than changing the title of the posts. It is better to figure what you want to ask and then to ask once.
    My second comment is that you have given us information about your central site. At some point we may also need some information about what is at the remote and how that is set up. But for now we will deal with what we know about your site.
    Before I deal with your specific questions I will comment that if you are able to access the remote airlinks that it is a pretty good indicator that the tunnels are probably working. But to understand the significance of this it would help if you clarify for us what address is on the local computer when you change the subnet to 255.255.0.0.
    Also what you have shown us allows us to see that BGP is configured but provides no insight into whether BGP is working or now. It would provide helpful information if you would post the output of show ip bgp sum.
    So to address your specific questions:
    You suggest that adding a static route for 192.168.1.0 might be part of the solution. But we have no information about what that network is or its significance. So we have no way to know whether the static route would help or not. But my guess (based on very scant information and therefore based mostly on assumptions) is that if BGP is working correctly that the static route is not needed.
    1) asks about an Ethernet address on the tunnel. I assume that you really meant to ask about the IP address assigned to the tunnel. The reason that the tunnel needs it own IP address is that we want a unique subnet assigned to the tunnel. If we used the address from the physical interface as you suggest then both tunnels would have the same address and that implies that they both connect to the same place, and that assumption is not correct.
    2) Yes it is correct to point the default route to the IP address that is the next hop from the Ethernet interface. You might want to have a route pointing at the tunnel address for remote subnets reached via the tunnel. But in looking at the config and trying to understand what was intended it is pretty obvious that running BGP over the tunnel is intended to learn the remote addresses over the tunnel and therefore there is no need for static routes for the remote resources.
    3) You should not need an additional permit for TCP 402. The TCP packet will be carried through the tunnel and the access list you are referring to will see the packet will modbus polling as GRE traffic and not as TCP traffic.
    HTH
    Rick

Maybe you are looking for