<?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 2013 Mac OS X Hints</copyright>
<generator>Geeklog</generator>
<pubDate>Mon, 25 Mar 2013 07:30:02 -0700</pubDate>
<language>en-gb</language>
<atom:link href="http://hints.macworld.com/backend/hintsnetwork.rss" rel="self" type="application/rss+xml" />
<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>
<item>
<title>10.7: Hidden Mobile Network Profile support</title>
<link>http://hints.macworld.com/article.php?story=20111023175231992</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20111023175231992</guid>
<pubDate>Fri, 28 Oct 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20111023175231992#comments</comments>
<dc:subject>Network</dc:subject>
<description>Opening a &lt;em&gt;.mobileconfig&lt;/em&gt; file in Lion exposes an otherwise hidden System Preference, 'Profiles' as shown &lt;a href=&quot;http://i.minus.com/ibvMpFQIrVKo0z.png&quot;&gt;here&lt;/a&gt;.&lt;br&gt;&lt;br&gt;The &lt;em&gt;.mobilconfig&lt;/em&gt; files are typically used to &lt;a href=&quot;http://manuals.info.apple.com/en_US/Enterprise_Deployment_Guide.pdf&quot;&gt;manage network settings on iOS&lt;/a&gt;, including the &lt;a href=&quot;http://en.wikipedia.org/wiki/Access_Point_Name&quot;&gt;Access Point Name (APN)&lt;/a&gt;.&lt;br&gt;&lt;br&gt;To view this in Lion, just open a &lt;em&gt;.mobileconfig&lt;/em&gt; file from Finder and System Preferences will now reveal 'Profiles' with a means to manage multiple profiles.&lt;br&gt;&lt;br&gt;If you install a &lt;em&gt;.mobileconfig&lt;/em&gt;, Profiles will remain available in System Preferences; if you delete all profiles, then Profiles no longer appears in System Preferences.&lt;br&gt;&lt;br&gt;This doesn't yet seem to affect network access or browsing at all, so it is possible this feature exists to pave the way for more unified management of APN on desktops with mobi ...</description>
</item>
<item>
<title>10.7: Manage firewall logs</title>
<link>http://hints.macworld.com/article.php?story=20110802132135228</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110802132135228</guid>
<pubDate>Wed, 05 Oct 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110802132135228#comments</comments>
<dc:subject>Network</dc:subject>
<description>After upgrading to 10.7 my firewall logs were filled with endless &quot;Firewall: Allow foo connecting from 1.2.3.4:1234 to port 1234 proto=x&quot;. Happily the logging system can be told to selectively ignore these messages.&lt;br&gt;&lt;br&gt;Certain applications use lots of incoming network connections, and the default behaviour in Lion when the firewall is enabled is to log every single allowed connection.&lt;br&gt;&lt;br&gt;A single rule line in &lt;em&gt;/etc/asl.conf&lt;/em&gt; can silence these useless messages.&lt;br&gt;&lt;br&gt;&lt;tt&gt;? [= Sender Firewall] [A= Message Allow foo] ignore&lt;/tt&gt;&lt;br&gt;&lt;br&gt;You can add this line using your favorite text editor, but you'll need one that can save files with root-level permissions (like the non-App Store version of TextWrangler).&lt;br&gt;&lt;br&gt;[&lt;b&gt;crarko adds:&lt;/b&gt; I haven't tested this one. To be honest, I don't run the OS X firewall.]
</description>
</item>
<item>
<title>MCX Refresh for Mobile Accounts</title>
<link>http://hints.macworld.com/article.php?story=20110921053832255</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110921053832255</guid>
<pubDate>Thu, 22 Sep 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110921053832255#comments</comments>
<dc:subject>Network</dc:subject>
<description>I needed to forcibly refresh the per user mcx for a large number of mobile users across many desktop machines under Snow Leopard so I wrote this short script that will do just that.&lt;br&gt;&lt;br&gt;Can be run from remote desktop (as root), or locally (sudo). It will not always successfully refresh the mcx, but it will force it to be reloaded from the server on the next logon.&lt;br&gt;&lt;br&gt;Here's the shell script:&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;#Brutally refresh mcx for a machine and all mobile accounts on it#Clear machine cachedscl . -list Computers | grep -v &quot;^localhost&amp;#36;&quot; | while read computer_name ; do sudo dscl . -delete Computers/&quot;&amp;#36;computer_name&quot; ; doneecho &quot;Cleared machine MCX cache.&quot;#Get a list of locally cached accountsfor usr in `dscl . -list /Users AuthenticationAuthority | grep LocalCachedUser | awk '{print &amp;#36;1}' | tr  ...&lt;/pre&gt;&lt;/div&gt;</description>
</item>
<item>
<title>Annotate information in Connect to Server dialog</title>
<link>http://hints.macworld.com/article.php?story=20110919094827346</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110919094827346</guid>
<pubDate>Wed, 21 Sep 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110919094827346#comments</comments>
<dc:subject>Network</dc:subject>
<description>In Finder, Command+K (&lt;em&gt;Finder &amp;raquo; Go &amp;raquo; Connect to Server…&lt;/em&gt;) permits the storing of frequently used server addresses and protocols. However, when servers are indicated only by their IPv4 or IPv6 addresses, it is not easy to remember which address corresponds with which server. There appears to be no way to include text information associated with server addresses.&lt;br&gt;&lt;br&gt;It is possible to include the &lt;em&gt;#&lt;/em&gt; anchor at the end of the address and to indicate some information after this #. No spaces are allowed after the #.&lt;br&gt;&lt;br&gt;Examples:&lt;br&gt;&lt;br&gt;vnc://fkm@[2b01:0670:3201:1137:0211:24ff:ffe0:4bc6]#eMac_Conservation&lt;br&gt;afp://mgi@[2a01:0e35:2d49:0580:9227:e2ff:fef2:29ff]#Macbook_d_Emelyne&lt;br&gt;smb://129.172.107.192#DataXlab&lt;br&gt;&lt;br&gt;Note that the true addresses have been changed of course in the examples.&lt;br&gt;&lt;br&gt;[&lt;b&gt;crarko adds:&lt;/b&gt; This works at least as far back as Leopard, and it wouldn't surprise me if it goes back further. I didn't find an obvious duplic ...</description>
</item>
<item>
<title>10.7: Enable AirDrop on Macs without supported wireless hardware</title>
<link>http://hints.macworld.com/article.php?story=20110913213649565</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110913213649565</guid>
<pubDate>Fri, 16 Sep 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110913213649565#comments</comments>
<dc:subject>Network</dc:subject>
<description>AirDrop is a handy way to share files between Macs. Unfortunately, it is only supported on newer models which have the hardware necessary to support a certain type of point-to-point WiFi connection. There is, however, a hidden setting to enable AirDrop on older Macs. Just type:&lt;br&gt;&lt;br&gt;&lt;tt&gt;defaults write com.apple.NetworkBrowser BrowseAllInterfaces 1&lt;/tt&gt;&lt;br&gt;&lt;br&gt;into a Terminal window, hit enter, and relaunch the Finder.&lt;br&gt;&lt;br&gt;Note that:&lt;ul&gt;  &lt;li&gt;You must do this on both the sending and receiving macs, even if one of them already has the correct WiFi hardware (I think).&lt;/li&gt;  &lt;li&gt;You will be able to see other macs on the same network, and they will be able to see your Mac (when AirDrop is open), even if they are not physically nearby. On a larger network with many Macs, this could potentially cause some confusion, although it shouldn't be a real security issue. This may be why Apple decided not to enable this feature by default.&lt;/li&gt;  &lt;li&gt;Both macs must be connected to th ...&lt;/li&gt;&lt;/ul&gt;</description>
</item>
<item>
<title>10.7: Monitor your Wi-Fi with  Wi-Fi Diagnostics</title>
<link>http://hints.macworld.com/article.php?story=20110807084920307</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110807084920307</guid>
<pubDate>Wed, 24 Aug 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110807084920307#comments</comments>
<dc:subject>Network</dc:subject>
<description>Lion ships with an app called Wi-Fi diagnostics. It allows you to monitor Wi-Fi networks your computer is connected to and collect various kinds of information. This utility could be very useful for finding problems or doing research on your Wi-Fi networks.&lt;br&gt;&lt;br&gt;The easiest way to launch Wi-Fi Diagnostics is to open it directly from the location &lt;em&gt;/System/Library/CoreServices&lt;/em&gt;.&lt;br&gt;&lt;br&gt;Once it launches, you get some options to choose from. As an example, let's use the first, Monitor Performance. Select that and click Continue.&lt;br&gt;&lt;br&gt;You are given a live-updating graph of the signal/noise ratio of your network. This could be useful for live testing to find problems with interference. For example, turn on your coordless phone and see if your ratio worsens. If it does, move your router farther away from the phone.&lt;br&gt;&lt;br&gt;The other options are also useful, allowing you to log events like people connecting and disconnecting, and allowing you to sample raw data sent acros ...</description>
</item>
<item>
<title>10.7: Active Directory Binding</title>
<link>http://hints.macworld.com/article.php?story=20110805100012401</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110805100012401</guid>
<pubDate>Tue, 23 Aug 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110805100012401#comments</comments>
<dc:subject>Network</dc:subject>
<description>Many people, myself included seem to be having problems binding 10.7 machines into Active Directory, a cryptic 'Error 5202' seems to be fairly common. Here's the fix that worked on our network.&lt;br&gt;&lt;br&gt;Initially I managed to get machines to bind by manually creating an edu.mit.Kerberos file and populating it before performing the actual bind. This would work but a reboot would often cause a 'Network Accounts Unavailable' message. &lt;br&gt;&lt;br&gt;The opendirectoryd logs were full of messages such as 'No preferred destination' and  'Failed to retrieve keychain password for 'MACHINENAME&amp;#36;' module '' node '/Active Directory/DOMAIN'.' &lt;br&gt;&lt;br&gt;On a whim I tried disabling IPv6 on the ethernet adapter -- which is apparently no longer possible using the GUI in 10.7. Once I disabled it from the command line the machine bound without the need to create a kerberos file and authentication worked perfectly. &lt;br&gt;&lt;br&gt;You can disable IPv6 from the command line with:&lt;br&gt;&lt;br&gt;&lt;tt&gt;networksetup -set ...&lt;/tt&gt;</description>
</item>
<item>
<title>10.7: Accessing Windows shares if files/folders do not appear in Finder</title>
<link>http://hints.macworld.com/article.php?story=2011072201375433</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=2011072201375433</guid>
<pubDate>Thu, 28 Jul 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=2011072201375433#comments</comments>
<dc:subject>Network</dc:subject>
<description>I'm experiencing a problem whereby the Windows shares I use at work mount in the Finder but don't reveal 'child of child' directories. So basically I can't see any of my working files/folders.&lt;br&gt;&lt;br&gt;Here's a workaround I used in this situation:&lt;br&gt;&lt;br&gt;Open Terminal, navigate to the share (once mounted) in &lt;em&gt;/Volumes&lt;/em&gt;. Navigate to one of the child of child folders (they appear in Terminal but were empty when viewed in the Finder) and type 'open.'&lt;br&gt;&lt;br&gt;This opens the folder in the Finder revealing the files/folders that were invisible before. In addition, you can now navigate 'up' in the Finder to see the previously hidden parent directory.&lt;br&gt;&lt;br&gt;[&lt;b&gt;crarko adds:&lt;/b&gt; I haven't tested this one.]
</description>
</item>
</channel>
</rss>
