Closed Network is still visible

I have an Airport Express setup to create a network. On the same "wireless" tab in the AirPort Utility, when you click on the "Wireless Network Options" there is a check mark in the box for "Create Closed Network". However, the network is still visible. Why? Thanks for the help!
Message was edited by: rminot

+Bob, the option specifically says: "The name of a "closed" network is hidden. To join the network, a user must know the name of the network."+
It says this on your "main" AirPort Express setup in AirPort Utility. But there is no option for this if you are using an AirPort Express to extend using wireless only.
You posted that you were using a second AirPort Express to extend your wireless network.
Click on your "remote" AirPort Express in AirPort Utility
Click Manual Setup
Click the Wireless tab
Do you see any option that would tell the "extending" AirPort Express to hide your network? I can't find it.
My guess was that the extending device is broadcasting the name of the network since there is no option that would allow it to be "hidden".
Suggest that your follow up with Apple as I cannot speak for their product design decisions. AirPort Express Feedback.

Similar Messages

  • Closed Network Reduces Signal Strength ?

    On my AEBS I am using WPA2 Personal and had closed my network. I noticed that closing the network reduced my signal strength by 20 per cent. Why is there such a significant reduction ?
    Since a closed network is still broadcasting and therefore is detectable, is there any point at all in closing your network ?
    PowerBook 15.2, 1.33GHz, 1.5G RAM, 60GB   Mac OS X (10.4.6)   AEBS,AE

    ...is there any point at all in closing your network ?
    No, absolutely no benefit at all.

  • IFrame(child container) still visible after closing the title window(parent container)

    Hi All ,
    I have created a sample project using a link button which when clicked opens up an TitleWindow which has an iframe and a text area in a hbox
    When you execute the application ,
              Click the link button
              The Popup window opens up showing the title window with the close button
              Click the close button of the title window
              The Title window is removed and the iframe and the text area are not visible
    Do this a couple of times
    You can notice that the iframe is still visible even when the title window is closed
    Can someone explain me how this issue can be resolved and also explain me why the iframe(child container) is still visible when the title window(parent container) is not visible. 
    Main Application file
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application
        width="100%" height="100%" creationPolicy="all"
        xmlns:mx="http://www.adobe.com/2006/mxml"
        layout="vertical" creationComplete="init()"
        xmlns:containers="containers.*">
       <mx:Script>
       <![CDATA[
           import mx.managers.PopUpManager;
           import containers.PopUpBrowser;
           public function doRequest():void
                    var requestPopup:PopUpBrowser = PopUpManager.createPopUp(this, PopUpBrowser) as PopUpBrowser;
                    PopUpManager.addPopUp(requestPopup,this);
                    requestPopup.x = 220;
                    requestPopup.y = 50;
       ]]>
       </mx:Script>
       <mx:Text fontSize="14" fontWeight="bold" text="Click the link button below to open the Title Window" />
       <mx:Spacer height="100"/>
       <mx:LinkButton label="Click me" fontSize="16" fontWeight="bold" click="doRequest()"/>
    </mx:Application>
    PopUpBrowser.mxml Component
    <?xml version="1.0" encoding="utf-8"?>
    <mx:TitleWindow
        xmlns:mx="http://www.adobe.com/2006/mxml"
        close="removeMe()"
        showCloseButton="true"
        styleName="myTitleWindowStyle"
        width="850" height="500"
        title="Klout User Profile"
        paddingTop="1" paddingBottom="1"
        paddingLeft="1" paddingRight="1"
        xmlns:generic="com.serendio.voom.components.generic.*"
        xmlns:flexiframe="http://code.google.com/p/flex-iframe/"
        horizontalScrollPolicy="off"
        verticalScrollPolicy="off" >
        <mx:Script>
            <![CDATA[
                import mx.managers.PopUpManager;
                public function removeMe():void
                    PopUpManager.removePopUp(this);
            ]]>
        </mx:Script>
        <mx:HBox width="100%" height="100%">
        <flexiframe:IFrame source="http://www.google.com" id="iFrame" width="50%" height="100%"/>
        <mx:TextArea text="Open and close the title window few times and watch the iframe remain visible even when the title window is closed"
             fontSize="14" width="50%" height="80%"/>
        </mx:HBox>
    </mx:TitleWindow>
    Thanks,
    Ajantha

    Hey,
    This is working fine for me with the current 4.5 Flex, Firefox 3.6.12, IE8. On what browser you are getting this error.
    Thanks,
    Jayagopal.

  • Connecting to Closed Networks

    I have an airport express that I use for wireless access in my dorm. So, it's acting as a traditional router rather than a range extender. I have it set up as a closed network so that it's only visible to those who know the network name. I also have WPA2 enabled for security.
    My problem is that, rather sporadically, I will wake my MBP from sleep and a dialog appears stating that "No known networks are available" and gives a list of available open networks. So, I choose "other" and input the network name and the password, making certain that "remember this network" is checked before connecting. Even after doing this multiple times, I still get the dialog periodically (about every other day or so) and I haven't been able to figure out why.
    I left the network open for about a week and didn't encounter this issue, so it seems to be associated with the fact that it is a closed network. It wouldn't be a huge deal to have the network visible to anyone who browses for a network since it is encrypted, but I would rather have it closed in a building with a lot of people.
    Does anyone have any ideas for a solution?

    Yeah, the debate goes on and on, but if you were running aircrack-ng or kisMac and you saw my non-broadcast SSID pop up because I was actively affiliated to my network, wouldn't that pique your interest more in my network than in Alex's whose WPA2-AES-secured SSID you saw every day?
    Meanwhile, I don't really know of any fix to Alex's complaint, in order to avoid the hoops that he has to jump through in order to reaffiliate after waking from sleep -- I can't say that I can recall ever seeing anything posted in these forums that adequately addressed the issue. Nobody's piped in on this thread yet with a suggestion to fix this behavior. I'd love to hear of one that is a dependable long-term fix. I'd go non-broadcast then myself.
    I used to not broadcast a long time ago when I first went wireless, but I got tired of dealing with this very issue all the time myself, so when I weighed the annoyance of the reaffiliation process after waking from sleep versus the increased likelihood of my WPA2-AES-PSK with truly random passcode getting cracked because I broadcast my SSID, I chose convenience over annoyance. I don't believe that my security has been compromised in any way by my choice.
    Alex is apparently annoyed as well, so that's why I recommended he go ahead and broadcast SSID so as to not be annoyed by this behavior anymore. WPA2-AES with a random passcode is as secure as he's gonna get wirelessly, broadcast SSID or not. He needs to weigh the choice of putting up with the annoyance factor or not...until somebody posts a sure-fire cure.

  • Open and Closed network access?

    Is it possible to have both an open network portion (no password), as well as a closed (password protected) network setup with a single Time Capsule/Airport Extreme device?
    I want to keep my data protected with a password access to the network, but would like to also have an open network for guests that does not always require a password just to access the internet.
    Thanks!

    Can you clarify what you mean by "closed network"?  Normally a "closed" network is one in which the name of the wireless network is not visible.
    If you have a dual band AirPort Extreme or Time Capsule it is possible to set up a "main" network that is visible and password protected....and a "guest" network that is "open", not requiring a password to connect.
    Important.......The guest network feature cannot be enabled if you are connecting the Extreme or Time Capsule to another gateway device.....a combination modem/router that is provided by a number of service providers.

  • Can you open a closed network?

    I can no longer access the secure wi fi network set up on my Mac Pro, and must use  the (insecure) network that came with my router. The regular network name doesn't show as an available network, but I know it is still there because both the name and security type appear  when I click "advanced" on System Preferences/Network. I have apparently changed my regular network to "closed" by accident.
    I have tried unsuccessfully to sign in as "other network", providing security type and passwork, but it doesn't work.
    I need a way to open this closed network. Is this possible?  How?
    If it is impossible, what must I do to start over?

    I have apparently changed my regular network to "closed" by accident.
    Or the network is no longer available, temporarly shut down, or you were purposely locked out.  Contact the network admin.

  • Airport Extreme multicast rate and closed network

    New to Airport Extreme.
    Is the multicast rate the same as the TX rate on other routers? I chose 11Mbps during the setup and my Macbook was very slow. I moved it back to 2 Mbps and it sped up. Distance from macbook to airport approx. 24 inches.
    Other question/ statement. I assume that the closed network portion of the setup is the same as turning off the SSID of other routers. Do I assume correctly?

    goldengti, Welcome to the discussion area!
    Is the multicast rate the same as the TX rate on other routers?
    Sorry I don't know about other routers. The multicast rate defines the minimum data rate the base station will use and maintain the wireless connection. If you set it to 11 Mbps, the wireless connection will be broken if that data rate can't be maintained.
    Other question/ statement. I assume that the closed network portion of the setup is the same as turning off the SSID of other routers. Do I assume correctly?
    Yes the same useless option. Regardless of how you set this option on any router, the SSID is still broadcast between any connected clients and the base station. Therefore it only takes a few seconds to discover the SSID.

  • Using WDS and Closed Network

    I need to close an office network that I converted to wireless using apple airport's extreme base station and One relay express and a remote express. I already have it setup sucessfully broadcasting the SSID, but the owner doesnt want anybody seeing it, as we are in an office bldg. Any Suggestions? I dont want to start over unless I have to.
    Imac G4 flat panel 20   Mac OS X (10.4.1)   3 PC's as well as the Mac's.

    There is little advantage, and many disadvantages, of setting up a "closed" network. The two biggest disadvantages are setup administration and "false" security. The AirPort, like most wireless routers, still broadcast their SSIDs to include data used for network data synchronization. Therefore, even "closed" networks can be easily found by "sniffers." Closing a network only keeps the casual users away.
    A far better policy is to use wireless encryption, specifically WPA, to ensure no unauthorized access can occur (regardless if they can "see" the network.)

  • WDS and Closed Network

    In an already existing WDS network (functioning in G model) is it possible to select the "Closed Network" in all my WDS routers and still have WDS functioning?
    The reason I ask is because it is possible one of my neighbours is sabotaging my network and making it "invisible" there might a less likely chance for him to find my network (as long as he's not that savvy). What's been happening is I discovered today that the reason Time Capsule backups were happening so slowly is because my network conflicts with his--but only recently. I was on radio signal 1 and so was he/she. So I switched it to radio signal 11. Less than 2 hours later, his/her network radio signal is also on 11. So I have my suspicions...

    Yes, my network is closed now. Security has always been enabled at WPA2 but enabling security does nothing to remedy malicious radio interference (if that is what my neighbour is doing). The reason I want to set it to "close" (invisible) is so that if the neighbour is not savvy enough, s/he will think my network is gone and no longer try to use the same channel I am.
    Yesterday, I realised the reason my Time Capsule backups were going so slowly is because my neighbour was using the same radio frequency as I was (Channel 1). His/her network has existed for a while now and we never clashed before. So I thought it must have been just conincidence. So then I switched over to Channel 11. Well, two hours later, his/her network was also on Channel 11 making my network go from speeds of 54 to 11. So, I thought this is possibly him/her playing around and interfering with my network so I decided to go "invisible."
    You are right that someone who is a bit more knowledgeable can figure out what the invisible networks are. It's not that hard. Even I can use iStumbler to see them. But, may s/he is not that savvy--I'm hoping.
    Enabling security does nothing for radio interference. I've always had WPA2 security on.

  • Should iPhone remember connection to a "closed network?"

    I chose to keep my network closed by configuring my Airport Extreme to not broadcast it's network name. Laptops have no trouble remember the settings for my closed network after just one configuration. I just got my new iPhone connected to my Airport Extreme, but it seems to lose or forget the settings after it automatically locks. I then have to reconfigure the Wi-Fi settings of the iPhone to reconnect to my wireless network.
    Is this normal behavior? Shouldn't the iPhone remember the network settings for networks it successfully connects to, even if the network is not broadcasting its SSID?

    Perhaps this is a modem security thing. In France, I use a LiveBox modem. The iphone French help line told me to disconnect then reconnect the modem, wait for 4 buttons to begin flashing and then stay on, until the final 5th button - the one that indicates wifi - starts to flash. During that time, new devices can be added.
    I did this, it worked, the iphone's stayed on wifi for two days. I've gone shopping, taken it for walks, and still it connects, no problems, on return.
    Pat

  • SSID showing on closed network

    I have an original 500GB TC connected to a dual-band AEBS to extend my wireless network.
    I have configured the TC to create a closed wireless network (SSID not broadcast). But the AEBS is broadcasting the SSID of my network.
    Everything in the network (iPhone, multiple Mac's, other wireless devices) is working fine - just this little annoyance.
    I cannot find anything in the AirPort utility to alter this behavior. Anyone out there have any ideas about why this is happening? and how to get the AEBS to stop broadcasting my SSID?

    Welcome to the discussions!
    In a "closed network", many users are surprised to learn that the SSID is still always being broadcast in the open between any connected clients, so this "feature" is quite limited in it's functionality. Any number of simple utilities readily available on the internet will display a closed network in seconds.
    There is not a setting or option in AirPort Utility to tell the "extending" device to "hide" the network that it's extending, so if this is important to you, you might want to provide your thoughts directly to Apple using AirPort Extreme Feedback.

  • Cannot find my closed network, but OK if I open it up

    For at least two years now, I have been connected to my AirPort via a closed network. Then a week ago the Mini stopped connecting to this network.
    If I make it public from the Base station, the Mini can connect with no problem, even though iStumbler reports only 47% signal and 19% noise.
    However, if I close the network again, the Mini can no longer see it. If I open Networks in the system utilities and go to Advanced, then the network is still configured. But even if I try to create a new connection and enter the name and access code again, the Mini still won't connect.
    I have reset the PRAM and repaired permissions, but I am still not able to connect to my network.
    Where does OSX keep the config file for the network and can I delete it. It seems that, even though I enter the network name as a new connection, it is still using the old file, because the name is the same.

    Well. After many hours on the phone with AppleCare, deleting AirPort configuration files, keychain entries, and preferred networks, upgrading to 10.5.7 and the latest AirPort utility, we finally downgraded the TimeCapsule from firmware 7.4.1 to 7.3.2.
    That did the trick. My Mini can now connect to the closed wireless network.
    However, now it cannot see the Time Capsule disk and the AirPort utility cannot find any wireless AirPort devices, even though it is connected to the very same Time Capsule via the closed network.
    I seem to remember seeing information about this problem in connection with 10.5.7 or AirPort 5.4.2, but I haven't been able to dig them up yet.

  • "closed network" setting in a WDS network

    I've just shifted to the APExtreme after many years in LinksysLand. I've recycled an old old APExpress (circa '04) and combined the two in a WDS network, in order to boost signal on the other side of that metal elevator. (Yes, I know WDS is less efficient...but the price was right, etc).
    I prefer to suppress SSID broadcast, so I set both base and remote stations to "closed network." But then the MacBook and iPhone couldn't see the network - either station. Turn that option off on the Express (remote station) only, and the devices see the network and set up on the Express G channels. Meanwhile, down the hall, everybody can see the Extreme, and those that can use the 5gHz channels do so, with that set as a "closed network."
    What am I missing? Or not understanding about WDS? thx

    Unfortunately that option is simply a deception to the user and offers a false sense of security. The network name is still broadcast between any connected client and the base station. Therefore the network name is easily discovered.
    The only thing enabling that option does successfully is cause connection and configuration problems. The option is best avoided.

  • Closed network issue

    I called Apple support yesterday to configure my Time Capsule with my Uverse system. My Apple Tv's and my wireless iMac in my bedroom where the time capsule is located have no problem connecting to my network.
    The problem is with my iMac in my living room when after I shut it down at night. When I start it up in the morning, this imac doesn't find my network and I have to constantly re-enter my network name and password to access the internet. Is this because of my closed network setting?
    Is there a solution for this?
    thanks in advance to all you gurus out there!

    Harisn wrote:
    I recently created a closed network
    is there a particular reason for that ? closed (or hidden) networks do not add any security because they still broadcast their SSID openly. many freely available tools can detect them.
    if you are behind a router firewall, use WPA2 security and a long, non-dictionary password made up of letters and numbers, your network is as safe as it gets.
    Is this standard behavior, or is there perhaps some sort of fix?
    it may not be standard but it's not unusual. again, a closed network doesn't provide extra security but leads to problems such as what you experience.
    secure your network as per the above and do away with the closed part.
    JGG

  • Airport Closed Network

    I am having a problem automatically joining my closed network on startup.
    It will join the network if it is not closed upon startup. It works fine on my G5 iMac running Panther.
    I have tried fiddling with the Network setting to "By default, join..." Automatic & Preferred networks. Also tried the Airport setup assistant... the password is in my keychain...
    A side note, the signal level received from the airport base station is very low compared to the signal received on the iMac. The base station is about 4ft away from both computers.
    Help!!
    Mac Pro 2.66GHz - 20" iMac G5 - 12" iBook G4   Mac OS X (10.4.7)  

    No such luck. I tried the keychain first aid repair and it didn't report any problems.
    I have also tried re-ordering the networks it'll try to join by putting the Airport at the top of the list. Still nothing.
    I have noticed that on the Network Status window, the Firewire always seems to be on top of the Airport... So I deleted the Firewire network, restarted, and still it can't join the Airport network.
    Any idea if the low signal from the Airport Base Station has anything to do with it? I'll try and move the two on top of each other and see if that makes any difference.

Maybe you are looking for