<?xml version="1.0" encoding="iso-8859-1"?>

<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>macosxhints.com network tips</title>
<link>http://hints.macworld.com/index.php?topic=network</link>
<description>Tips and tricks for networking OS X with Windows, Linux, OS X, whatever, from macosxhints.com</description>
<managingEditor>webteam@macosxhints.com</managingEditor>
<webMaster>webteam@macosxhints.com</webMaster>
<copyright>Copyright 2014 Mac OS X Hints</copyright>
<generator>Geeklog</generator>
<pubDate>Wed, 30 Apr 2014 07:00:00 -0700</pubDate>
<language>en-gb</language>
<atom:link href="http://hints.macworld.com/backend/hintsnetwork.rss" rel="self" type="application/rss+xml" />
<item>
<title>Creating a kill switch for the OSX VPN client</title>
<link>http://hints.macworld.com/article.php?story=20140423225754712</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20140423225754712</guid>
<pubDate>Wed, 30 Apr 2014 07:00:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20140423225754712#comments</comments>
<dc:subject>Network</dc:subject>
<description>I live in China so I have to use VPN all the time if I want any kind of stable connection to sites in the west. Unfortunately the VPN will at times randomly disconnect and then all traffic will immediately start going over chinese Internet again. While this is not a big deal really, I would just prefer not to be logged in to Facebook or Gmail and have my traffic open to be sniffed by the great firewall. It also occurred to me that many people use VPNs in the states in order to safely torrent.&lt;br&gt;&lt;br&gt;I know some VPN providers have 'Internet kill switches' for their VPN that will cut your Internet connection incase of a disconnect and make sure you are not leaking anything. The problem with these is that they are almost all using openVPN, while I use L2TP over IPSec for my VPN. I searched for a long time for a way to do this and could not find one so I thought of a way to do it on my own. The following is how I set my system up. Please keep in mind that I am not an experienced Term ...</description>
</item>
<item>
<title>10.9: Enable experimental network commands</title>
<link>http://hints.macworld.com/article.php?story=20131216083254449</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20131216083254449</guid>
<pubDate>Fri, 28 Mar 2014 07:00:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20131216083254449#comments</comments>
<dc:subject>Network</dc:subject>
<description>Many advanced network configuration commands can be reached with the &lt;code&gt;scutil&lt;/code&gt; command line tool. Launch Terminal.app and run:&lt;br&gt;&lt;br&gt;&lt;code&gt;ENABLE_EXPERIMENTAL_SCUTIL_COMMANDS=1 scutil --net&lt;/code&gt;, then type &lt;code&gt;help&lt;/code&gt; and press the Return key to see the available options.&lt;br&gt;&lt;br&gt;For example:&lt;div style=&quot;margin-left: 20px; margin-top:10px; margin-bottom:10px; padding: 5px; border:1px solid; width:520px; height:120px; overflow:scroll;white-space:nowrap;resize:both&quot;&gt;&lt;pre&gt;localhost:~ user&amp;#36; ENABLE_EXPERIMENTAL_SCUTIL_COMMANDS=1 scutil --netset &quot;Automatic&quot; selected&gt; helpAvailable commands: help                          : list available commands f.read file                   : process commands from file quit [!]                      : quit commit                        : commit any changes apply                         : apply any changes create interface &lt;interfaceType&gt; [ &lt;interfaceName&gt; | &lt;interface#&gt; ] create protocol &lt;protocolType&gt; create ser ...&lt;/protocolType&gt;&lt;/interfaceName&gt;&lt;/interfaceType&gt;&lt;/pre&gt;&lt;/div&gt;</description>
</item>
<item>
<title>Make Time Machine use a Local Volume as a Network Volume</title>
<link>http://hints.macworld.com/article.php?story=20140308141622774</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20140308141622774</guid>
<pubDate>Tue, 11 Mar 2014 07:00:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20140308141622774#comments</comments>
<dc:subject>Network</dc:subject>
<description>This procedure shows you how to prevent Time Machine from using all available free space on a local volume by backing up to a sparse disk image bundle stored on a shared folder on a local volume.&lt;br&gt;&lt;br&gt;Time machine uses a feature of the HFS+ filesystem that was introduced in Mac OS X 10.5 (Leopard) called '&lt;i&gt;directory hard links&lt;/i&gt;.' Like file hard links, a directory that is hard linked to another directory is not actually a distinct directory, but is instead a pointer to the original directory. Time Machine uses these directory hard links to reduce duplication and save space by making references to entire directory trees whose contained files have not been modified.To properly copy or duplicate a Time Machine backup, these directory hard links must be preserved. Unfortunately, directory hard links are proprietary to Apple. Apple discourages their casual use by third party developers because, if used incorrectly, they could create recursive directory structures that would ren ...</description>
</item>
<item>
<title>Mount a SanDisk Connect Wireless Flash Drive</title>
<link>http://hints.macworld.com/article.php?story=20130903155152381</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20130903155152381</guid>
<pubDate>Fri, 06 Dec 2013 07:00:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20130903155152381#comments</comments>
<dc:subject>Network</dc:subject>
<description>&lt;a href=&quot;http://www.sandisk.com/products/wireless/flash-drive/&quot;&gt;The SanDisk Connect Wireless Flash Drive&lt;/a&gt; includes all the benefits of a regular flash drive plus wireless mobile access.&lt;br&gt;&lt;br&gt;Sandisk gives you an app that allows you to connect to the Flash Drive's WiFi and transfer files. You can either connect via USB on the Mac or  connect using a WiFi network. But what was not very clear was how to do this if you wanted to connect to the drive and upload or download files to and from your Mac wirelessly.&lt;br&gt;&lt;br&gt;I tried to do this once I had connected to the drive's WiFi network and using a browser (as they suggest) to connect to the given URL. The address is served from the Flash Drive's WiFi network and in turn shows you the files on the drive. But I could not see my files and realised the page was being directed via my Ethernet connection across the Internet to a SandDisk page telling me the drive was not connected.&lt;br&gt;&lt;br&gt;Turning off the Ethernet connection fixed th ...</description>
</item>
<item>
<title>Let VNC viewers connect to currently logged in user</title>
<link>http://hints.macworld.com/article.php?story=20131003103827136</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20131003103827136</guid>
<pubDate>Tue, 08 Oct 2013 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20131003103827136#comments</comments>
<dc:subject>Network</dc:subject>
<description>Want to connect with the currently logged in user when using a VNC viewer rather than seeing the Login Window (ARD 3.5/OS X 10.7 and later)?&lt;br&gt;&lt;br&gt;&lt;code&gt;sudo defaults write /Library/Preferences/com.apple.RemoteManagement VNCAlwaysStartOnConsole -bool true&lt;/code&gt;
</description>
</item>
<item>
<title>Find devices connected to your AirPort base station without AirPort Utility 5.6</title>
<link>http://hints.macworld.com/article.php?story=20130821063020920</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20130821063020920</guid>
<pubDate>Wed, 21 Aug 2013 06:35:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20130821063020920#comments</comments>
<dc:subject>Network</dc:subject>
<description>&lt;p&gt;AirPort Utility 5.6 could show you all the devices connected to your AirPort base station—wired and wireless alike. &lt;a href=&quot;http://hints.macworld.com/article.php?story=20120203094920282&quot;&gt;AirPort Utility 6.x&lt;/a&gt;, however, only lists devices connected to your base station over Wi-Fi. There’s no way to use the app to list off the IP addresses and names of devices plugged directly into the base station.&lt;/p&gt;&lt;p&gt;You can stil &lt;a href=&quot;http://hints.macworld.com/comment.php?mode=view&amp;cid=128027&quot;&gt;grab the old version of the utility&lt;/a&gt; from Apple, though you need &lt;a href=&quot;http://www.macworld.com/article/1167965/mountain_lion_and_the_ancient_airport_base_station.html&quot;&gt;a little help to install the app on Mountain Lion&lt;/a&gt;, since the installer (falsely) reports that AirPort Utility 5.6 is incompatible with Mac OS X 10.8.&lt;/p&gt;&lt;p&gt;But while you can force AirPort Utility 5.6 to install on Mountain Lion, there’s no guarantee that the app will continue to work on OS X 10.9 Mavericks or beyond.  ...&lt;/p&gt;</description>
</item>
<item>
<title>How to set up a Mac as a PXE boot server, with Debian Live</title>
<link>http://hints.macworld.com/article.php?story=20130625164022823</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20130625164022823</guid>
<pubDate>Fri, 28 Jun 2013 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20130625164022823#comments</comments>
<dc:subject>Network</dc:subject>
<description>Here is how to set up a Mac, running OS X Client 10.5 or later, as a PXE boot server.&amp;nbsp; We will configure OS X's built-in DHCP, TFTP, and NFS servers, start the servers, and put the client boot files in place.&amp;nbsp; (The NFS server may be optional, depending on the operating system we are booting.)&lt;br&gt;&lt;br&gt;You'll need the Mac, a PXE-capable PC, and an ethernet cable.&amp;nbsp; Some steps will require being logged in as an administrator on the Mac.&lt;br&gt;&lt;br&gt;We'll boot Debian Live on the client PC as an example.&amp;nbsp; We'll show a regular setup with NFS, an alternate setup without NFS, and how to uninstall.&lt;br&gt;Regular setup (with NFS):&lt;ol&gt;&lt;li&gt;Connect the Mac and the client PC with the ethernet cable.&lt;br&gt;&lt;br&gt;&lt;/li&gt;&lt;li&gt;On the Mac, in System Preferences &amp;gt; Network, click &quot;Ethernet&quot; and enter the following settings:&lt;pre&gt;Configure IPv4: ManuallyIP Address: 192.168.1.1Subnet Mask: 255.255.255.0(All others can be left blank)&lt;/pre&gt;Note the status may read &quot;Cable Unplugge ...&lt;/li&gt;&lt;/ol&gt;</description>
</item>
<item>
<title>Making Juniper Network Connect use Keychain</title>
<link>http://hints.macworld.com/article.php?story=20130623135353765</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20130623135353765</guid>
<pubDate>Wed, 26 Jun 2013 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20130623135353765#comments</comments>
<dc:subject>Network</dc:subject>
<description>Password managers are a good thing, as they encourage you to maintain strong passwords. Just the sort of thing you’d want if you were opening every port on every computer on your enterprise network. Unfortunately, Juniper doesn’t see it this way. This can be resolved with some crafty scripting.&lt;br&gt;&lt;br&gt; First, we need a scripting addition called &lt;a href=&quot;http://www.red-sweater.com/blog/2035/usable-keychain-scripting-for-lion&quot;&gt;Useable Keychain Scripting&lt;/a&gt;. Download it and copy it to &lt;em&gt;/Library/Scripting Additions&lt;/em&gt;. You'll need to type your password to do this.&lt;br&gt;&lt;br&gt; Next, you need to be able to connect to your VPN, so do this, then disconnect. Network Connect should retain the address of your server (e.g. https://vpn.example.com).&lt;br&gt;&lt;br&gt; Now create a password item for the server (https://vpn.example.com), and grant access to Usable Keychain Scripting. Or not, your call.&lt;br&gt;&lt;br&gt; Now fire up the script. It will get the address of the server from Network Connect, get  ...</description>
</item>
<item>
<title>&amp;quot;Airplane mode&amp;quot; for OS X </title>
<link>http://hints.macworld.com/article.php?story=20130325002258846</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20130325002258846</guid>
<pubDate>Mon, 25 Mar 2013 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20130325002258846#comments</comments>
<dc:subject>Network</dc:subject>
<description>A reader at Stack Exchange asked &lt;a href=&quot;http://apple.stackexchange.com/questions/86351/airplane-mode-in-os-x-alternative-command-for-rfkill&quot;&gt;an interesting question&lt;/a&gt; about whether it was possible to set up an &quot;airplane mode&quot; for OS X. The idea was to ensure that there is no network activity through any possible network interfaces. &lt;br&gt;&lt;br&gt; It's actually pretty simple to do this. If you go to the Network pane of System Preferences, you'll see a Location popup menu at the top of the window. Click on that menu and choose Edit Locations. Click on the + icon to add a new location, then enter a name, such as AirplaneMode. Click on Done.&lt;br&gt;&lt;br&gt; Next, choose that location in the Location menu, and click on each available network interface in the list at the left of the window. Click on the Configure iPv4 menu, and choose Off. For Wi-Fi, just click on the Turn Wi-Fi Off button. Click Apply, and this location will block all network activity.&lt;br&gt;&lt;br&gt; To activate the location, ther ...</description>
</item>
<item>
<title>Generate list of wi-fi networks a Mac has used</title>
<link>http://hints.macworld.com/article.php?story=20121226001352647</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20121226001352647</guid>
<pubDate>Thu, 27 Dec 2012 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20121226001352647#comments</comments>
<dc:subject>Network</dc:subject>
<description>You can find out which wi-fi networks a Mac has connected to by going to the Network preference pane, then clicking on Advanced, then on the Wi-Fi tab; they'll be listed in Preferred Networks. But if you want to do this from Terminal - say for a Mac you've connected to via ssh - this hint, &lt;a href=&quot;http://osxdaily.com/2012/12/21/list-wi-fi-networks-mac-has-connected-to-before/&quot;&gt;posted on OS X Daily&lt;/a&gt;, can do it as well:&lt;div style=&quot;margin-left: 20px; margin-top:10px; margin-bottom:10px; padding: 5px; border:1px solid; width:700px; height:50px; overflow:scroll;white-space:nowrap;resize:both&quot;&gt;&lt;pre&gt;defaults read /Library/Preferences/SystemConfiguration/com.apple.airport.preferences RememberedNetworks | egrep -o '(SSID_STR|_timeStamp).+' | sed 's/^.*= &amp;#092;(.*&amp;#092;);&amp;#36;/&amp;#092;1/' | sed 's/^&quot;&amp;#092;(.*&amp;#092;)&quot;&amp;#36;/&amp;#092;1/' | sed 's/&amp;#092;([0-9]&amp;#092;{4&amp;#092;}-..-..&amp;#092;).*/&amp;#092;1/'&lt;/pre&gt;&lt;/div&gt; The list will be the same as that in Preferred Networks, and you can't alter it, ...</description>
</item>
<item>
<title>Use Back to My Mac to manage remote server </title>
<link>http://hints.macworld.com/article.php?story=20121108132616918</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20121108132616918</guid>
<pubDate>Fri, 16 Nov 2012 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20121108132616918#comments</comments>
<dc:subject>Network</dc:subject>
<description>When managing a server at work, I noticed my home server was showing up in the list of managed servers. Trying to see if I could connect by supplying my credentials was unsuccessful. I figured it must be showing up because I had signed into the same iCloud account on both machines. I then wondered if using the Back to My Mac URL for iCloud would allow me to connect. &lt;br&gt;&lt;br&gt; To test, in Server.app I selected Manage &gt; Connect to Server...  From there chose &quot;Other Mac.&quot;  For the Hostname I inserted the Back to My Mac URL in the form server.XXXXXXXX.members.btmm.icloud.com. (see &lt;a href=&quot;http://hints.macworld.com/article.php?story=20120724152214581&quot;&gt;this hint&lt;/a&gt; to find how to construct the correct URL for your Mac), supplied my credentials and clicked Connect. The remote server came right up and I was able to manage my home server with no issues.
</description>
</item>
<item>
<title>Option-click Airport menu to launch Wi-Fi Diagnostics</title>
<link>http://hints.macworld.com/article.php?story=20120905082310287</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20120905082310287</guid>
<pubDate>Thu, 06 Sep 2012 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20120905082310287#comments</comments>
<dc:subject>Network</dc:subject>
<description>&lt;a href=&quot;http://hints.macworld.com/article.php?story=20110807084920307&quot;&gt;A hint last year&lt;/a&gt; mentioned Wi-Fi Diagnostics, an application hidden in /System/Library/CoreServices. It turns out that you can also access this by Option-clicking the AirPort menu in your menubar and choosing Open Wi-Fi Diagnostics.&lt;br&gt;&lt;br&gt; [&lt;b&gt;kirkmc adds&lt;/b&gt;: This was available under Lion, but wasn't in the original hint, so it's worth posting.] 
</description>
</item>
<item>
<title>Remotely connect to a Mac via SSH using iCloud's network </title>
<link>http://hints.macworld.com/article.php?story=20120724152214581</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20120724152214581</guid>
<pubDate>Fri, 10 Aug 2012 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20120724152214581#comments</comments>
<dc:subject>Network</dc:subject>
<description>If you're running two Macs with iCloud support (Lion or Mountain Lion), then you can use iCloud's network to remote SSH back into your home computer no matter where you are with just a few commands in Terminal.&lt;br&gt;&lt;br&gt; The process is explained by the &lt;a href=&quot;http://onethingwell.org/post/27835796928/remote-ssh-bact-to-my-mac&quot;&gt;One Thing Well&lt;/a&gt; blog, but you need to set up a few things before you get started. First, you need to make sure Back to My Mac is enabled in iCloud (System Preferences &gt; iCloud &gt; Back to My Mac). Next, you need to set up your home computer for sharing if it isn't already. Head to System Preferences &gt; Sharing and turn on at least File Sharing and Remote Login. With everything set, you can now remotely log in to your home computer using iCloud's network wherever you have internet access.&lt;br&gt;&lt;br&gt; To start with, you need to do is find your Back to My Mac account number. In Terminal (Applications &gt; Utilities), type:&lt;pre&gt;dns-sd -E&lt;/pre&gt; The final nine digit  ...</description>
</item>
<item>
<title>Flush DNS cache in Lion and Mountain Lion </title>
<link>http://hints.macworld.com/article.php?story=20120808001623238</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20120808001623238</guid>
<pubDate>Wed, 08 Aug 2012 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20120808001623238#comments</comments>
<dc:subject>Network</dc:subject>
<description>I came across &lt;a href=&quot;http://support.apple.com/kb/HT5343&quot;&gt;this Apple technical note this morning&lt;/a&gt;, which describes how to flush the DNS cache on your Mac. We have a &lt;a href=&quot;http://hints.macworld.com/article.php?story=20071027100807321&quot;&gt;hint for 10.5&lt;/a&gt;, which is also valid for 10.6, but we're not up to date.&lt;Br&gt;&lt;br&gt;So, as a reminder, to flush the DNS cache in Mac OS X 10.5 and 10.6, run this command in Terminal:&lt;br&gt;&lt;pre&gt;sudo dscacheutil -flushcache &lt;/pre&gt;   To do the same in 10.7 and 10.8, run this command:&lt;br&gt;&lt;pre&gt;sudo killall -HUP mDNSResponder &lt;/pre&gt;  As Apple points out, you might need to do this in the following situation:&lt;Br&gt;&lt;br&gt;&quot;OS X keeps a local cache of resolved DNS queries for a time defined by the DNS server, but sometimes it may be necessary to reset the cache immediately and re-query a DNS server. For example, you might do this after an entry on the server is changed or a new entry is added.&quot;
</description>
</item>
<item>
<title>Clear out phantom NFS shares</title>
<link>http://hints.macworld.com/article.php?story=20120717055242729</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20120717055242729</guid>
<pubDate>Mon, 23 Jul 2012 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20120717055242729#comments</comments>
<dc:subject>Network</dc:subject>
<description>This is a hint about phantom NFS shares that may linger on your system long after you stopped accessing the share, and that may cause slowdowns and errors with various disk utilities. The information here applies to Lion, and may differ in earlier and later versions.&lt;br&gt;&lt;br&gt; I used to have a NAS device that I named &quot;dns323,&quot; and which was visible in the Finder as an NFS share. (The unit used a Linux-formatted disk.) In the past few months, whenever I used the excellent Yasu system maintenance utility, it would report an error message, saying that the file &quot;dns323&quot; wasn't found. I eventually realized that this problem started when I stopped using that NAS device. I also noticed that Find Any File was starting very slowly; and when I used Find Any File to see if it could find any trace of &quot;dns323,&quot; it listed the file in its results list, but said that the item had disappeared.&lt;br&gt;&lt;br&gt; I eventually realized that there was a directory named &quot;dns323&quot; in my user folder, but that dire ...</description>
</item>
<item>
<title>Airport Utility 6.0</title>
<link>http://hints.macworld.com/article.php?story=20120203094920282</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20120203094920282</guid>
<pubDate>Tue, 07 Feb 2012 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20120203094920282#comments</comments>
<dc:subject>Network</dc:subject>
<description>Airport Utility 6.0 was released a few days ago.&lt;br&gt;&lt;br&gt;You may want to keep both 5.6 and 6.0 versions. I used &lt;a href=&quot;http://www.charlessoft.com/&quot;&gt;Pacifist&lt;/a&gt;, and manually reinstalled the 5.6 version side by side. Lots of missing features in the new utility. No way to tweak wireless options for Mode, Frequency, Multicast Rate or Transmit Power, and such a tiny window for port mapping list. An elegant interface, but at a price.&lt;br&gt;&lt;br&gt;For a thorough review and pointers to stand alone updates, read &lt;a href=&quot;http://www.tuaw.com/2012/01/31/in-pictures-airport-utility-6-0s-missing-features/&quot;&gt;here&lt;/a&gt;.&lt;br&gt;&lt;br&gt;[&lt;b&gt;crarko adds:&lt;/b&gt; Consider this a public service announcement. It also appears that AirPort Utility 6.0 only functions with the 802.11(n) compatible base stations, so that old AirPort Express you may have (like I do) is not supported. I've actually saved many older versions of the utility, even for the original Graphite (flying saucer) bases.]
</description>
</item>
<item>
<title>Fix dropout problems when streaming music over Airport Express g</title>
<link>http://hints.macworld.com/article.php?story=20120108083136856</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20120108083136856</guid>
<pubDate>Tue, 10 Jan 2012 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20120108083136856#comments</comments>
<dc:subject>Network</dc:subject>
<description>I've been using Airport Express wireless-g for years to stream music to my stereos. And they work great once you get them working, but with the wireless-g models, I have always had problems setting them up on a new network after they have already been setup on another network. I use it as a streaming device, so it is set up as a device on my network, and not as my router. The problem with dropouts when streaming music over an Airport Express g can be resolved by changing the network settings on the wireless router.&lt;br&gt;&lt;br&gt;First of all, the Airport Utility never seems able to find an Airport Express that does not have factory settings and is not set to communicate with the existing wireless network. Sometimes holding down the reset button on the AE until the light blinks rapidly while it is plugged in works. In other cases, I have had to hold it down before plugging it in and then plug it in to get it to work. I have often had to repeat these steps multiple times before I can get  ...</description>
</item>
<item>
<title>10.7: Mount AFP volume with root bug</title>
<link>http://hints.macworld.com/article.php?story=20120106082818768</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20120106082818768</guid>
<pubDate>Mon, 09 Jan 2012 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20120106082818768#comments</comments>
<dc:subject>Network</dc:subject>
<description>I'm sick of waiting for Apple to come up with a fix to trying to mount a volume in 10.7 while logged in as root so I came up with my own solution.&lt;div style=&quot;margin-left: 20px; margin-top:10px; margin-bottom:10px; padding: 5px; border:1px solid; width:520px; height:120px; overflow:scroll;white-space:nowrap;resize:both&quot;&gt;&lt;pre&gt;cat &gt;/tmp/mountVolume.sh &lt;&lt;-&quot;EOF&quot;osascript -e 'mount volume &quot;afp://username:password@server/path/&quot;'EOFchmod 755 /tmp/mountVolume.shsu -l guest /tmp/mountVolume.shrm -f /tmp/mountVolume.sh&lt;/pre&gt;&lt;/div&gt;When run as root this will use the guest account to mount the volume -- it's a work around and only recommended for those whom understand the root account.&lt;br&gt;&lt;br&gt;[&lt;b&gt;crarko adds:&lt;/b&gt; I haven't tested this one.]
</description>
</item>
<item>
<title>10.7: Slowdown with  a new MobileMe/iCloud Password</title>
<link>http://hints.macworld.com/article.php?story=20111029193853639</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20111029193853639</guid>
<pubDate>Fri, 30 Dec 2011 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20111029193853639#comments</comments>
<dc:subject>Network</dc:subject>
<description>My Mac started working extremely slowly and I couldn't understand the reason for a while.&lt;br&gt;&lt;br&gt;I knew my wireless was working seemingly without problems (iPad and iPhone working normally) but I thought to run the AirPort Utility to check out the wireless network.&lt;br&gt;&lt;br&gt;My AirPort Extreme was reporting a problem. It turns out that I had changed my password on MobileMe to match iCloud, and of course my AirPort Extreme did not know that. It was trying to connect to the MobileMe servers with no success. I guess it was trying to connect to MobileMe non-stop and it was slowing down my system significantly. Fixing the password within the AirPort Extreme resolved the issue.&lt;br&gt;&lt;br&gt;[&lt;b&gt;crarko adds:&lt;/b&gt; It's always worth looking at network related issues when an unexpected slowdown happens. And when a transition happens (like the Mobile Me -&gt; iCloud migration) expect to see issues like this happen. Fortunately they're easy to correct once identified.]
</description>
</item>
<item>
<title>Getting port mappings and DHCP usage from an Airport Device</title>
<link>http://hints.macworld.com/article.php?story=20111226173953274</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20111226173953274</guid>
<pubDate>Thu, 29 Dec 2011 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20111226173953274#comments</comments>
<dc:subject>Network</dc:subject>
<description>If you're like me, I'm frustrated by the way the Airport Utility displays NAT port mappings and DHCP assignments. I have a lot of ports mapped, and quite a few devices on my network and it's painful to remember which ports are mapped to which devices. I've searched high and low to find something to help and come up blank.&lt;br&gt;&lt;br&gt;I wrote the following bash script which relies on the built-in utility PListBuddy to extract the relevant values from the property list that can be exported from the Airport Utility. To use it, open Airport Utility and select the device that has the mappings.&lt;br&gt;&lt;br&gt;Press the 'Manual Setup' button (or Cmd+L) and the Utility will load the information from the device. Next choose Export Configuration File... from the file menu and save it to disk. Now run the bash script below and it will extract the values and send them to stdout in tab delimited form. You can then open the result in a spreadsheet or editor of your choice and see all your port mappings,  ...</description>
</item>
</channel>
</rss>
