<?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 2012 Mac OS X Hints</copyright>
<generator>Geeklog</generator>
<pubDate>Tue, 10 Jan 2012 07:30:03 -0800</pubDate>
<language>en-gb</language>
<atom:link href="http://hints.macworld.com/backend/hintsnetwork.rss" rel="self" type="application/rss+xml" />
<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>
<item>
<title>A cross-platform text Clipboard using Dropbox</title>
<link>http://hints.macworld.com/article.php?story=20110617041836290</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110617041836290</guid>
<pubDate>Thu, 30 Jun 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110617041836290#comments</comments>
<dc:subject>Network</dc:subject>
<description>This hint describes how to set up a cross-platform text-only clipboard using Dropbox.
&lt;br&gt;&lt;br&gt;
I've found myself frequently having a piece of text in one computer and wanting to have it in another one. I use Dropbox all the time, so the 'easiest' was to save the text to a text file in the Dropbox folder and open it in the other computer. Hey, it's like a Dropbox Clipboard!
&lt;br&gt;&lt;br&gt;
See, the thing I haven't mentioned is that the two machines in question are a MacBook and a Windows 7 box, so that leaves out any Mac- or Windows-only solution. I also want something simple (so Synergy  is out too) and tweakable. Full clipboard support is not simple, but fortunately I just need plain text and AppleScript (for OS X) and &lt;a href=&quot;http://www.autohotkey.net/~Lexikos/AutoHotkey_L/&quot;&gt;AutoHotkey&lt;/a&gt; (for Windows) can do everything I'll need, so let's code a bit.
&lt;br&gt;&lt;br&gt;
One of AutoHotkey's strengths is its complete keyboard control so it can do it all in one punch:
 ...</description>
</item>
<item>
<title>Toggle Airport On and Off</title>
<link>http://hints.macworld.com/article.php?story=20110522082622506</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110522082622506</guid>
<pubDate>Tue, 24 May 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110522082622506#comments</comments>
<dc:subject>Network</dc:subject>
<description>The hint 'Control Airport Without Menu Bar' in the June issue of Macworld (also see &lt;a href=&quot;http://www.macworld.com/article/158220/2011/03/toggleairportpower.html&quot;&gt;this article&lt;/a&gt;) was very informative and useful.  I devised a simple script based on the article hint that toggles airport on and off.&lt;br&gt;&lt;br&gt;Here is the script. Copy and Paste it into AppleScript Editor and save it as an Application.&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;---- Toggle Airport Power On and Off--if (offset of &quot;On&quot; in (do shell script &quot;networksetup -getairportpower en1&quot;)) &gt; 0 then	do shell script &quot;networksetup -setairportpower en1 off&quot;else	do shell script &quot;networksetup -setairportpower en1 on&quot;end if&lt;/pre&gt;&lt;/div&gt;&lt;br&gt;[&lt;b&gt;crarko adds:&lt;/b&gt; I tested this, and it works as described. It follows precisely the method described in the linked Macworld article, in c ...</description>
</item>
<item>
<title>Not a hint, but a funny networking Easter egg</title>
<link>http://hints.macworld.com/article.php?story=20100716061424857</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20100716061424857</guid>
<pubDate>Thu, 12 May 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20100716061424857#comments</comments>
<dc:subject>Network</dc:subject>
<description>Not really a hint but I thought this was hilarious.&lt;br&gt;&lt;br&gt;I did a Get Info on one of the PC Servers connected to my Mac when I noticed the contents of the icon on the preview area. Yes, it is a picture of the Blue Screen of Death. All the connected PC servers get this icon. Cannot tell what version of Windows BSOD this is though.&lt;ul&gt;  &lt;li&gt;Open a Finder window.&lt;/li&gt;  &lt;li&gt;Right click on a server (under 'Shared' in the Sidebar).&lt;/li&gt;  &lt;li&gt;Select Get Info.&lt;/li&gt;&lt;/ul&gt;I love the extra attention Apple gives to details in OS X. &lt;br&gt;&lt;br&gt;[&lt;b&gt;crarko adds:&lt;/b&gt; Another reader (titaniumtroop) set in a similar submission about the Quick Look icon for a Windows Server being the BSOD. Apple has removed so many of the good old Easter eggs it's nice to see an indication that a sense of humor still thrives in Cupertino.]
</description>
</item>
<item>
<title>10.6: Slow SMB browsing of Windows Servers fixed</title>
<link>http://hints.macworld.com/article.php?story=20110430173901534</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110430173901534</guid>
<pubDate>Wed, 04 May 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110430173901534#comments</comments>
<dc:subject>Network</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; alt=&quot;Snow Leopard only hint&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;By default in Mac OS X browsing to Windows 2008 and 2003 Servers is extremely slow, navigating from one directory level to the next can take a minute or longer. I utilize my Mac to access the office Windows 2008 and 2003 file servers and the speed to access these shares makes it almost impossible to work from a Mac.&lt;br&gt;&lt;br&gt;To make things even worse I do most of my work through a Cisco SSL VPN loaded on my Mac from home over a broadband connection. Out of pure frustration I started playing with settings in my SMB configuration and have found a way in Mac OS 10.6.7 to speed the process up drastically to where navigating folders is almost instantaneous (including over my VPN). This makes the Mac work just as fast as my Windows 7 workstation when connecting to Windows servers.&lt;br&gt;&lt;br&gt;In order to fix the slow SMB browsing you will need to edit the smb.conf fi ...</description>
</item>
<item>
<title>Several networked and non-networked options for Time Machine backups</title>
<link>http://hints.macworld.com/article.php?story=20110406195505167</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110406195505167</guid>
<pubDate>Fri, 08 Apr 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110406195505167#comments</comments>
<dc:subject>Network</dc:subject>
<description>This hint collects together what I have learned about solutions for Time Machine backups. There are a number of viable solutions, and I cover several of them.&lt;br&gt;&lt;br&gt;&lt;b&gt;External USB or Firewire drive&lt;/b&gt;&lt;br&gt;&lt;br&gt;The most basic solution is a directly-attached external USB drive enclosure. This might be okay for desktop machines, but what bothers me about this is that both the Mac and the drive are on the same power circuit. If lighting strikes, then both can get hit at the same time. In a Mac Pro, you can use another internal drive for TM. And there are also external RAID solutions like I mention below. Unless you are particularly disciplined, this is a lousy solution for portable Macs. When I was going this route, I was lucky if I remembered to plug in the backup drive once a week. Maybe other people can do better than that, but it's still inconvenient. &lt;br&gt;&lt;br&gt;Thus, I prefer networked solutions. However, at the end of this hint, I go into a discussion on why TM is a great des ...</description>
</item>
<item>
<title>Keep attempting reconnection to wireless network</title>
<link>http://hints.macworld.com/article.php?story=20110223124409352</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110223124409352</guid>
<pubDate>Thu, 24 Feb 2011 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110223124409352#comments</comments>
<dc:subject>Network</dc:subject>
<description>Having trouble automatically reconnecting your unattended Mac to a wireless network because of unreliable signal quality? If you would like to have it keep reattempting reconnection until it manages to connect it's fairly simple to setup.&lt;br&gt;&lt;br&gt;You need to use the &lt;em&gt;airport&lt;/em&gt; command line tool in the Terminal. Open a terminal and run the following command (with no line breaks), typing in your password when prompted:&lt;div style=&quot;margin-left: 20px; margin-top:10px; margin-bottom:10px; padding: 5px; border:1px solid; width:520px; height:60px; overflow:scroll;white-space:nowrap;resize:both&quot;&gt;&lt;pre&gt;sudo /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport prefs joinmode=automatic joinmodefallback=keeplooking&lt;/pre&gt;&lt;/div&gt;Unlike the &lt;em&gt;JoinModeFallback&lt;/em&gt; setting of 'prompt' (which can be set in System Preferences) or 'donothing,' if it fails to join a network it will wait about a minute and then scan for a network to join again. It will do  ...</description>
</item>
<item>
<title>Simulate Airport Express network audio</title>
<link>http://hints.macworld.com/article.php?story=20110219044920654</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110219044920654</guid>
<pubDate>Wed, 23 Feb 2011 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110219044920654#comments</comments>
<dc:subject>Network</dc:subject>
<description>Have you ever wanted to wirelessly stream all audio from your Mac to the Unix/Windows/Mac box in your cupboard connected to your beefy stereo? Here is an alternative to buying an Airport Express for the purpose.&lt;br&gt;&lt;br&gt;&lt;p&gt;This tip is &lt;a href='http://hints.macworld.com/article.php?story=20060602065532384&amp;amp;query=esdrec'&gt;similar to this hint&lt;/a&gt; but after experimenting with that technique and various other options I think I've hit on an improved setup.
Steps to perform on your Mac:&lt;ul&gt;&lt;li&gt;Download and install &lt;a href=&quot;http://cycling74.com/products/soundflower/&quot;&gt;Soundflower&lt;/a&gt;. This will allow you to redirect all audio played on your Mac over the network.&lt;/li&gt;&lt;li&gt;Install &lt;a href=&quot;http://www.macports.org/&quot;&gt;MacPorts&lt;/a&gt; as well; this will make it easy to install esound and ffmpeg which are needed later.&lt;/li&gt;&lt;li&gt;Install esound with the command &lt;tt&gt;sudo port install esound&lt;/tt&gt; in Terminal.&lt;/li&gt;&lt;li&gt;Similarly install ffmpeg with &lt;tt&gt;sudo port install ffmpeg&lt;/tt&gt;.&lt;/li&gt;&lt;li&gt;In Syst ...&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;</description>
</item>
<item>
<title>Stop Finder from rounding file sizes on Samba shares </title>
<link>http://hints.macworld.com/article.php?story=20110208234803495</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110208234803495</guid>
<pubDate>Thu, 10 Feb 2011 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110208234803495#comments</comments>
<dc:subject>Network</dc:subject>
<description>If you have a Linux or BSD machine running Samba you may notice that its exported shares round up all files under a megabyte (i.e. 720kB becomes 1MB) by Finder.&lt;br&gt;&lt;br&gt;To fix this problem add the following line to the server's smb.conf:&lt;br&gt;&lt;br&gt;&lt;em&gt;allocation roundup size = 0&lt;/em&gt;&lt;br&gt;&lt;br&gt;Restart the Samba daemon, reconnect to the share, and files under one megabyte should now be calculated correctly in Finder. &lt;br&gt;&lt;br&gt;[&lt;b&gt;crarko adds:&lt;/b&gt; I haven't tested this one. I would assume (but don't know) that this change may also be needed to the Samba server on a Mac.&lt;br&gt;&lt;br&gt;On most systems this file is located at &lt;em&gt;/etc/samba/smb.conf&lt;/em&gt; or &lt;em&gt;/usr/local/samba/lib/smb.conf&lt;/em&gt;. In Snow Leopard the location is &lt;em&gt;/etc/smb.conf&lt;/em&gt;. You may want to save off a backup copy of the file prior to editing it. To save it you need an editor that can authenticate as root, such as TextWrangler or BBedit or you can use a command line editor invoked with sudo.]
</description>
</item>
</channel>
</rss>

