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

Similar Messages

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.

My Macs can't remember visited closed networks

My friend, a new Mac user, brought this problem to my attention. He was frustrated to find that he has to enter the network name and password for the closed network at his job site each time he accesses the network. His Windows laptop "remembers" the information and automatically logs him in.
I thought I would quickly get to the bottom of this problem for him and show him how easy Macs are to configure. I set up a closed network at my home with my AP extreme. I am running Snow Leopard on my main Mac and OS X 10.4.11 on my older Powerbook. Much to my chagrin, I am duplicating my friend's experience. I can connect to the new closed network from either of my computers by entering the network name and password. But neither of my computers "remembers" the closed network between restarts of Airport or of the computer. I have to re-enter the network name and password each time I want to connect. Neither computer shows any memory of the closed network except that the name of the network does appear in the "Preferred Networks" section of the Networks preferences section of System Preferences. "Remember networks this computer has joined" is selected.
I know that in the past it was possible to have my Mac remember closed networks that had been previously visited. What has happened?
Any help would be appreciated.
John

LittleSaint wrote:
Are two threads about the same problem supposed to fix it faster?
I have initiated only one thread on this subject. A search of this forum reveals a half a dozen or more threads on this or very closely related topics. Some of these threads are quite old and dormant. None of them provides an answer. I did respond to a thread initiated by another user. But since his problem and mine are not necessarily the same issue(s) I posted my request for help in this thread. I apologize if this has offended you or any one else.
And to answer your question– I'm not convinced that the two threads you refer to necessarily relate to the "same problem". Perhaps they do. But there is the distinct possibility that by posting my own unique problem with detailed explanations might lead to a "faster fix". By posting in detail my networking problem in another's thread I run the risk of "hijacking" the discussion away from the original poster.
John

Airport 7.4.1 Update and closed networks

I updated my Airport Extreme and Express with the new firmware (7.4.1), both Purchased Dec 2008. After the Express udpated, it didn't show up in Airport Utility. I reset the Express and it showed up, but I had to redo the settings, when I did it didn't show up again. So I plugged an Ethernet cable into the Express and it I could see it in the Airport Utility. The Utility app said the express could not find a wireless network. My network is closed (hidden) and this seems to be a problem with the 7.4.1 update. When I opened the network, the Express worked fine. I'm using WPA2 Personal encryption.
--Scott

guys, I had this problem and have logged an issue on this forum for a similar (exact?) issue of a *TC in bridge mode* on a 5GHz hidden (closed) network that *would not connect after V7.4.1 update.*
HOWEVER after speculating a DEFECT in the V7.4.1 formware that after sometime (an hour???+) the TC doe sfinally hidden network @ 5G and iraculously comes online and connects. I have made a mistake in thinking this is a defect.
so I think I might propose _firing up V7.4.1 firmware back on your TC_ and go visit some mates for a while and it is likley to be back on.
I recycled the TC (just did this again) and waited 10mins and yes it was back online!. Slack latency however it is back with V7.4.1
In anycase backing off to that flaky V7.3.2 is probabaly not a good way to go. V7.3.2 seemed vary unstable and had at least an issue of not corrcetly port forwarding port 21 (FTP control).
just a suggestion.
hth
w

Security, Encryption, Open/Closed Network question

I use a 2010 model AirPort Extreme base station and set it up via Airport Utility. During setup, I selected "Closed" network and WPA2 encryption. I keep my "Guest Network" not enabled. In my residence, I can pick up signals from over 10 other networks going on in the neighborhood. I have both AirRadar 2.0.2 and iStumbler (Release 99). AirRadar says my network is "Open" and is not listed as "Secure" but lists "WPA2" as the encryption type. I've emailed their support for assistance understanding what seems to me to be conflicting information. iStumbler finds my network but as an "invisible" network. With the amount of wireless activity in my immediate area, I am very concerned about security issues.
My question: Is there a procedure I can follow that will help me determine the robustness of the security currently in place of my network?
I have only basic understanding of WiFi in general, security issues, and have only low to moderate computing skills. I'm no security expert, but a concerned consumer wanting to protect my family.
Thank you in advance for assistance in this matter.

a hidden (closed) network does not add much security, if any. there are freely available tools out there that will easily pick up a closed network. additionally, some wireless devices (iPod Touch, iPad) on your network may have problems picking up a hidden network when attempting to re-connect.
your network will be well protected with WPA2 and a long, non-dictionary password made up of letters and numbers - it would take a determined hacker with plenty of time to crack a thus protected network.
also make sure the extreme is password protected (again, choose a non-dictionary pw made up of letters and numbers.
you might find this useful: _*Take Control airport setup manuals*_.
JGG

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.

AE and closed network...deactivated my AE and won't hard or factory reset

Hi there. Simply set my AE to a closed network, but didn't get a chance to set name and password before AE shut down. Now I can't gain green light by unplugging and replugging, soft, hard or factory reset. Ugh! I can't locate AE on Airport Utility 1)b/c not up and running and 2) b/c is now set as closed network.
Can anybody tell me a trick to resetting AE beyond all the given resets?
Can I access what the closed network settings (name/password) may be?
Thanks.

Sure... first I tried just unplugging but it plugged back in as amber light. Then I tried the reset button for 5 seconds. Then I tried for 10 seconds. Then I unplugged and plugged back in while holding reset button. I did this as outlined in the link above for resetting AE. With Admin utilities open the the settings named. The only time I can get a green light is the first moment it hits the socket, but it immediately goes solid amber. If I press and hold for 10 seconds I get 3 or 4 flashing green lights but it immediately goes amber (in this case, flashing amber)after the 3rd or 4th flashing green light.
When I connected AE via Ethernet cable, I had to hold reset for 10 sec to get flashing amber in order to view AE details in AirPort Admin Utilities. I get a flashing amber light and the base station is named in the Admin Utilities with the name,Ethernet (WAN), the AirPort ID and Apple Base Station V6.3. When I choose configure, I get the error message, "The AirPort Admin Utility was unable to read the configuration fo the selected base station. An error occurred while reading the configuration." I always get this far and get stuck.
Is it that the AE is not "green", or have I blocked access to reconfigure when I put it on a closed network? or both?
Thanks...
Tracy

How to resolve network issue or dns to access web page on snow leopard server?

I have my network setup like as follows:
internet > router 1 > ethernet ports > switch > router 2
I have a mac osx snow leopard server connected to "router 1", but it is so slow when accessing a web page hosted on the server from a browser on a workstation connected to either router 1 or router 2?
Is there a problem with my network setup or maybe because I changed the name to newservername.local?

@Jeff and @Camelot,
I think it is a DNS issue. I completely reset the DNS settings on server and the local name with the steps below, but now cannot access the site hosted on the server at all
I used a modified version of http://www.mkahn.com/2010/09/configuring-dns-on-mac-os-x-10-6-snow-leopard-serve r-for-hosting/ to reset the server set
1. Stop DNS Service in Server Admin
2. Close Server Admin
3. Obtain 10.6 DNS Default files (below)
4. Overwrite the DNS files with DNS Default files:
/etc/dns/loggingOptions.conf.apple
/etc/dns/options.conf.apple
/etc/dns/publicView.conf.apple
/var/named/named.ca/etc/named.conf
/var/named/named.local
/var/named/localhost.zone
5. Restart your server
All machines have 1ms ping responses within the network including this snow leopard server that I am trying to setup. There is another test web server that return pages instantly within this network so I doubt it is a network issue, but a DNS issue.

Networking Issues after Upgrading to Windows 8.1

I have a Windows 8 desktop PC that is working fine with my network. I can browse the Internet fine using all major browsers etc. After upgrading to Windows 8.1 through the Windows Store I noticed that my wired networking was not working correctly.
The status of the network does not change (i.e. it doesn't change to Limited Connectivity) however browsing to sites in Chrome, IE or Firefox doesn't work as well as Windows 8.
IE11 gives me the error "This page can't be displayed, make sure the web address is correct" and other browsers give a similar error. I normally have to refresh 2-3 times to get a new page to load, sometimes even more. Everything works
fine from a laptop connected at the same time so it isn't an network issue with my provider.
I thought this might be a driver issue with the two on-board Marvell wired network adapters. I wasn't able to rollback the driver to older versions I found on the Internet. I then purchased another network card, Intel Desktop gigabit and the
issue still persists with that adapter. I then tried a USB wireless adapter and the issue still persists using wifi with the wired adapters disabled. I tried a new network cable and no luck either. I also tried resetting the IP stack using
the various netsh commands.
After that I thought I might try reset the Windows 8.1 PC, however that didn't work as I didn't have the restore image available as I upgraded from the Windows Store. I then tried installing Windows 8.1 fresh using a ISO with my Windows 8 key using
some of the recent guides that are available. That all worked but it didn't fix the networking issues.
I re-installed Windows 8.0 and the networking is now fixed and back to working normal again. I'd like to try again but I think I will have the same problems. I can't imagine why this would be a driver issue as I tried 3 different network adapters
and two installs of Windows 8.1. Any ideas what would be the cause of the Windows 8.1 issue?

HI,
Since this issue only occurred in the your desktop PC, and many network adapters you tried, failed, thus I think maybe we should focus on the model of your desktop PC, I suggest you update the BIOS and chipset from the manufacture to improve
the performance of win8.1.
Please also test this issue in safe mode with networking.
Please refer to:
Windows Startup Settings (including safe mode)
http://windows.microsoft.com/en-in/windows-8/windows-startup-settings-including-safe-mode
I’d like to share the following article with you:
Wired and wireless network problems
http://windows.microsoft.com/en-IN/windows/network-connection-problem-help#network-problems=windows-81&v1h=win81tab1&v2h=win7tab1&v3h=winvistatab1&v4h=winxptab1
Regards,
Yolanda
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
The issue occurs in safe mode as well under Windows 8.1. The motherboard is an Asus P5B Premium, however it works on Windows 8. How would I update the chipset when booted into Windows 8.1? In Device Manager it wasn't allowing me to update
the network drivers as they were newer versions already installed.
Edit: I also installed at Intel Chipset Device software dated 8/8/2013 with version 9.4.0.1026 and the issue still occurs. I am also running the latest BIOS that is available.

Very Strange Network Issue With Two Guests on 2012 R2 Hyper-V Failover Cluster

Hi all. We're having a odd issue with two guests on our 2012 R2 failover cluster.
In a nutshell, if we shutdown a particular server (I'll call it Server A) another totally different server (Server B) on the same node loses it's network connectivity to the domain. If we start server A back up, network connectivity returns on server B.
At first I thought server A might be running a service that was somehow linked to server B, so I decided to disable server A's NIC. Interestingly, that had no affect on server B's connectivity.
The next step I tried was pausing server A and again, no adverse affect on server B's connectivity.
Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
One other clue is that if I ping server B from either of the Hyper-V hosts in the cluster, I never lose network connection to server B.
So I would suspect this is some network issue on the cluster, but I'm kind of at a loss where to go from here.
Has anyone seen this behavior before or does anyone have any troubleshooting suggestions I can try?
Thanks!
George Moore

Hi Sir,
I'v never seen this before .
>>Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
They are connecting to same virtual switch ?
First please run cluster validation to check if there is any error .
If it is ok , please try the following items for troubleshooting :
1. shutdown serverA serverB
2. then add another virtual NIC for serverB
3. start server B check if the issue happens to both "old" and "new" virtual NIC .
In addition , you can live migrate both A and B to another node , then try to live migrate A to the original node .
If the issue persists , I would suggest you to remove that virtual switch on both nodes then re-create them .
Best Regards,
Elton Ji
If it is not the answer please unmark it to continue
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

HT201334 How does one set up profile manager on a completely closed network with no Internet access available or even possible?

I need to set up Profile Manager on a completely closed network that has no Internet access at all. I can sneaker-net files into the network if I need to.
Profile Manager (and Lion Server in general) seems to need outside access to complete setup and I've been unable to find any meaningful answers.
Does anyone any any ideas?
Thanks to all

you could try it without enabling apple push notifications in server
you wont' be able to push out profiles without enabling apple push notification
but users could download them, or you could install manually, e-mail etc

Closed network issue

Similar Messages

Maybe you are looking for