<?xml version="1.0" encoding="utf-8"?>

<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://www.macosxhints.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 2009 Mac OS X Hints</copyright>
<generator>Geeklog</generator>
<pubDate>Wed, 11 Nov 2009 07:30:02 -0800</pubDate>
<language>en-gb</language>
<atom:link href="http://www.macosxhints.com/backend/hintsnetwork.rss" rel="self" type="application/rss+xml" />
<item>
<title>Automatically start Internet Sharing via LaunchDaemon</title>
<link>http://www.macosxhints.com/article.php?story=2009110114123254</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=2009110114123254</guid>
<pubDate>Wed, 11 Nov 2009 07:30:00 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=2009110114123254#comments</comments>
<dc:subject>Network</dc:subject>
<description>In the past, people have submitted hints on how to get their Macs to start internet sharing automatically at boot. All of them are either editing files in hidden directories or creating a &lt;tt&gt;StartupItem&lt;/tt&gt; to do the task. Most people may not want to edit files that are for the system, and Leopard and later versions of OS X use &lt;tt&gt;LaunchDaemons&lt;/tt&gt;, not &lt;tt&gt;StartupItems&lt;/tt&gt; to run scripts or executables at boot.
&lt;br&gt;&lt;br&gt;
I created a &lt;tt&gt;LaunchDaemon&lt;/tt&gt; plist based on the composition of the iStat Server's &lt;tt&gt;LaunchDaemon&lt;/tt&gt; plist to run the &lt;tt&gt;InternetSharing&lt;/tt&gt; executable automatically at boot. Here's what it looks like:

&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;&amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&amp;lt;!DOCTYPE plist PUBLIC &quot;-//Apple//DTD PLIST 1.0//EN&quot; &quot;http://www.apple.com/DTDs/PropertyList-1.0.dtd&quot;&gt;
&amp;lt;plist version=&quot;1.0&quot;&gt;
&amp;...</description>
</item>
<item>
<title>10.6: A fix for failure to connect to new wireless networks</title>
<link>http://www.macosxhints.com/article.php?story=20091023172523809</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20091023172523809</guid>
<pubDate>Wed, 04 Nov 2009 07:30:23 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20091023172523809#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;After upgrading from 10.5.8 to 10.6.1 on my MacBook Pro, I was unable to connect to wireless networks unless I had already connected to them running under 10.5.8. Snow Leopard would &quot;see&quot; the new networks, but could not connect to them.
&lt;br&gt;&lt;br&gt;
The Genius Bar at the Apple Store helped me solve the problem. We opened Library &amp;raquo; Preferences &amp;raquo; SystemConfiguration, and trashed the entire contents of that folder. We also deleted all locations in System Preferences &amp;raquo; Network, and recreated the location Automatic. Finally, we rebooted.
&lt;br&gt;&lt;br&gt;
So far, I have been able to connect to all wireless networks that I want to using OS X 10.6.1.</description>
</item>
<item>
<title>Set Screen Sharing image quality via Terminal</title>
<link>http://www.macosxhints.com/article.php?story=20091012012014486</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20091012012014486</guid>
<pubDate>Tue, 27 Oct 2009 07:30:05 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20091012012014486#comments</comments>
<dc:subject>Network</dc:subject>
<description>I have to manage several Macs in a lot of locations and I was very confortable with the Bonjour discovery, saved connections, and hidden features of the 10.5 Screen Sharing app. Alas, with the release of 10.6, they have gone -- Apple wants to sell Apple Remote Desktop.
&lt;br&gt;&lt;br&gt;
I have found that using this command in Terminal...

&lt;pre&gt;&lt;code&gt;defaults write com.apple.ScreenSharing controlObserveQuality n&lt;/code&gt;&lt;/pre&gt;

...changes the quality of the connection's display, based on the value of &lt;tt&gt;n&lt;/tt&gt;:
&lt;ul&gt;
&lt;li&gt;&lt;tt&gt;1&lt;/tt&gt; = black and white&lt;/li&gt;
&lt;li&gt;&lt;tt&gt;2&lt;/tt&gt; = grayscale&lt;/li&gt;
&lt;li&gt;&lt;tt&gt;3&lt;/tt&gt; = 8-bit color&lt;/li&gt;
&lt;li&gt;&lt;tt&gt;4&lt;/tt&gt; = 16-bit color&lt;/li&gt;
&lt;li&gt;&lt;tt&gt;5&lt;/tt&gt; = full color&lt;/li&gt;
&lt;/ul&gt;
I also set up shortcuts using the &lt;tt&gt;vnc://192.168.0.1&lt;/tt&gt; URL convention in Safari, as discussed in &lt;a href=&quot;http://www.macosxhints.com/article.php?story=20080310160740170&quot;&gt;this hint and comments&lt;/a&gt;. I save all my connection shortcuts in a folder, and put that folder in my Dock. I now have a Saved Conne...</description>
</item>
<item>
<title>Enable anonymous FTP in 10.5 and 10.6</title>
<link>http://www.macosxhints.com/article.php?story=20091013094149180</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20091013094149180</guid>
<pubDate>Tue, 27 Oct 2009 07:30:02 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20091013094149180#comments</comments>
<dc:subject>Network</dc:subject>
<description>To enable anonymous FTP in Snow Leopard (and probably Leopard as well), just execute the following commands in Terminal:

&lt;pre&gt;&lt;code&gt;$ sudo dscl . -create /Users/ftp
$ sudo dscl . -create /Users/ftp NFSHomeDirectory /path/to/ftp/folder&lt;/code&gt;&lt;/pre&gt;

Replace &lt;tt&gt;/path/to/ftp/folder&lt;/tt&gt; with the path to the directory that the guest account will have access to. To disable anonymous access, use this command:

&lt;pre&gt;&lt;code&gt;$ sudo dscl . -delete /Users/ftp&lt;/code&gt;&lt;/pre&gt;

You may have to restart the FTP daemon by stopping File Sharing and starting it again in System Preferences. Although I didn't test it in Leopard, I see no reason why it shouldn't work there as well.
&lt;br&gt;&lt;br&gt;
[&lt;b&gt;robg adds:&lt;/b&gt; I haven't tested this one.]</description>
</item>
<item>
<title>Delete file from network volume without warning dialog</title>
<link>http://www.macosxhints.com/article.php?story=2009092105385625</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=2009092105385625</guid>
<pubDate>Mon, 19 Oct 2009 07:30:05 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=2009092105385625#comments</comments>
<dc:subject>Network</dc:subject>
<description>Whenever I delete a file from a network volume, I'm warned: 'The item &quot;File name&quot; will be deleted immediately. Are you sure you want to continue?' with Cancel or Delete as options. The Cancel button is always the default option. If you really want to delete the file, you need to use the mouse to select the non-default Delete button. Since I am always sure that I really want to delete this file, I'm a little annoyed by always having to use the mouse after typing Command-Backspace (the Move to Trash shortcut). After all, I am using a shortcut because I want to &lt;i&gt;avoid&lt;/i&gt; using the mouse.
&lt;br&gt;&lt;br&gt;
If you press Command-Option-Delete, however, the networked file will be deleted immediately, without any warning at all. As with the normal method of deleting a networked file, this deletes the file immediately.
&lt;br&gt;&lt;br&gt;
[&lt;b&gt;robg adds:&lt;/b&gt; You can avoid the mouse with the Command-Delete method by pressing Tab then Space after the dialog appears. If you look at the File menu with the Option ...</description>
</item>
<item>
<title>10.6: Switch between two wireless networks in one location</title>
<link>http://www.macosxhints.com/article.php?story=20090917125055502</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20090917125055502</guid>
<pubDate>Wed, 07 Oct 2009 07:30:03 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090917125055502#comments</comments>
<dc:subject>Network</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;For one reason or another, I have two wireless networks available to me to use in one location. One is DHCP enabled, while the other requires manual setup.
&lt;br&gt;&lt;br&gt;
The obvious solution for switching between these networks is to use the Locations feature in Networking to save two profiles, and then use the drop-down Location menu to switch between them. However, I have found that because my MacBook has the logins for both networks saved, it does not switch the wireless network, just the settings. Once you mix DHCP with manual settings, it just fails to work, and requires more intervention.
&lt;br&gt;&lt;br&gt;
My solution (admittedly inelegant, but I don't know how to implement a better way), was to create a shell script that will switch the locations, and power cycle the AirPort card (which means it picks up the 'preferred' network). This is then set as a Service using Automator, and assigned a key...</description>
</item>
<item>
<title>Safely and socially share a wireless network</title>
<link>http://www.macosxhints.com/article.php?story=20090902131809240</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20090902131809240</guid>
<pubDate>Wed, 16 Sep 2009 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090902131809240#comments</comments>
<dc:subject>Network</dc:subject>
<description>This is not really Mac-specific, but still a good idea. I like two things: sharing and encryption. But you can't have both with wi-fi. Either you share it or you encrypt the OTA transmissions with WPA.
&lt;br&gt;&lt;br&gt;
My compromise, which works for anyone in an apartment building is simple. Name your network like this:

&lt;pre&gt;&lt;code&gt;Bring beer to &amp;#91;apt number&amp;#93; for Password&lt;/code&gt;&lt;/pre&gt;

It's a nice way to get to know your neighbors, gets you free beer (pro tip: you can substitute other items for beer), and lets you be generous with your wi-fi while giving you some added level of security from the WPA encryption.
&lt;br&gt;&lt;br&gt;
[&lt;b&gt;robg adds:&lt;/b&gt; I can think of both upsides and downsides to this idea; it will be interesting to read what others think of it.]</description>
</item>
<item>
<title>10.6: Snow Leopard IPSec VPN and Cisco VPN client</title>
<link>http://www.macosxhints.com/article.php?story=20090901200411622</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20090901200411622</guid>
<pubDate>Tue, 15 Sep 2009 07:30:01 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090901200411622#comments</comments>
<dc:subject>Network</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;If you previously used the Cisco VPN Client and want to use the native Snow Leopard client, you need to un-install all of the Cisco configs, kernel extensions, etc. To do this, just run &lt;tt&gt;sudo /usr/local/bin/vpn_uninstall&lt;/tt&gt; in Terminal.
&lt;br&gt;&lt;br&gt;
If you don't, the menu bar VPN control won't work, and will be very sluggish to click around in.  The same goes for the Verizon Access Manager and the CDMA 3G built-in drivers.</description>
</item>
<item>
<title>10.6: Use 'special' keys in screen sharing</title>
<link>http://www.macosxhints.com/article.php?story=20090901084044529</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20090901084044529</guid>
<pubDate>Wed, 09 Sep 2009 07:30:08 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090901084044529#comments</comments>
<dc:subject>Network</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;I'm not sure if it's well-known, but Screen Sharing in Snow Leopard now supports all keyboard commands, including Command-Tab, Command-Space, and Command-Option-Escape. In 10.5, these keystrokes were sent to the local machine; in 10.6, they go to the screen sharing session.
&lt;br&gt;&lt;br&gt;
[&lt;b&gt;robg adds:&lt;/b&gt; In 10.6, whether you're sharing the screen of a 10.5 or 10.6 Mac, basically all keystrokes are sent to the remote machine, including kyes for Exposé and Dashboard -- if you've programmed separate keys beyond the hardwired keys -- F9 for Exposé's All Windows mode, for instance, gets sent from my MBP to my Mac Pro, but F3 (the hardwired Exposé key) does not. To send the keys locally, you'll need to click on a visible window (or the Desktop) behind the Screen Sharing session.]</description>
</item>
<item>
<title>10.6: Add NFS Mounts using Disk Utility</title>
<link>http://www.macosxhints.com/article.php?story=20090830073912179</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20090830073912179</guid>
<pubDate>Wed, 02 Sep 2009 07:30:04 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090830073912179#comments</comments>
<dc:subject>Network</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;NFS mounts are now added using Disk Utility. To add a Linux-hosted NFS share on my network, I did the following
&lt;div style=&quot;margin-left:60px&quot;&gt;&lt;ol&gt;
&lt;li&gt;Start Disk Utility&lt;/li&gt;
&lt;li&gt;Select NFS Mounts from the File menu&lt;/li&gt;
&lt;li&gt;Click the plus sign in the lower left corner&lt;/li&gt;
&lt;li&gt;Enter in your remote NFS URL info as described&lt;/li&gt;
&lt;li&gt;Enter the mount point.  If you add it to /Network, then it will show up in the Shared section of Finder, in an entry called All.&lt;/li&gt;
&lt;li&gt;If you're using secure ports on your server, then click the Advanced option and enter &lt;tt&gt;-P&lt;/tt&gt;&lt;/li&gt;
&lt;li&gt;Click Verify&lt;/li&gt;
&lt;li&gt;Save your settings&lt;/li&gt;
&lt;/ol&gt;&lt;/div&gt;
The NFS mount is now available.</description>
</item>
<item>
<title>10.6: Save Cisco IPSec password in the Keychain</title>
<link>http://www.macosxhints.com/article.php?story=2009082703155512</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=2009082703155512</guid>
<pubDate>Fri, 28 Aug 2009 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=2009082703155512#comments</comments>
<dc:subject>Network</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;Mac OS X Snow Leopard adds support for Cisco IPSec VPN connections -- that is, plain IPSec with XAuth authentication and mode_cfg.
&lt;br&gt;&lt;br&gt;
That makes it two layers of authentication: first, Machine Authentication with a password (Shared Secret) or an X509 certificate. Then a traditional username-password pair for XAuth, both of which you can enter and save in the Account Name and Password fields respectively when you set up the connection. Trouble is, even though you entered your password and it is apparently saved in the keychain properly, Mac OS X keeps nagging you to manually enter the password every time you connect. Turns out this is a just bug with a simple fix.
&lt;br&gt;&lt;br&gt;
Open the Keychain Access Application, select the System keychain and find your saved XAuth password entry in the list. Its Kind field will say &lt;tt&gt;IPSec XAuth Password&lt;/tt&gt;. Open it, then on the Access Control tab...</description>
</item>
<item>
<title>A script to automtically enable and disable the firewall</title>
<link>http://www.macosxhints.com/article.php?story=20090714140555465</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20090714140555465</guid>
<pubDate>Wed, 22 Jul 2009 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090714140555465#comments</comments>
<dc:subject>Network</dc:subject>
<description>This hints allows your firewall to automatically turn on or off based upon which network you are on. A LaunchAgent watches &lt;tt&gt;resolv.conf&lt;/tt&gt; in order to detect when there are changes in the network. Save the following in /Library/LaunchAgents:
&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;&lt;code&gt;&amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
&amp;lt;!DOCTYPE plist PUBLIC &quot;-//Apple//DTD PLIST 1.0//EN&quot; &quot;http://www.apple.com/DTDs/PropertyList-1.0.dtd&quot;&amp;gt;
&amp;lt;plist version=&quot;1.0&quot;&amp;gt;
&amp;lt;dict&amp;gt;
  &amp;lt;key&amp;gt;KeepAlive&amp;lt;/key&amp;gt;
  &amp;lt;false/&amp;gt;
  &amp;lt;key&amp;gt;Label&amp;lt;/key&amp;gt;
  &amp;lt;string&amp;gt;com.yourcompany.autofirewall&amp;lt;/string&amp;gt;
  &amp;lt;key&amp;gt;ProgramArguments&amp;lt;/key&amp;gt;
  &amp;lt;array&amp;gt;
    &amp;lt;string&amp;gt;/Library/Scripts/yourcompany/autofirewall.sh&amp;lt;/string&amp;gt;
  &amp;lt;/array&amp;gt;
  &amp;lt;key&amp;gt;RunAtLoad&amp;lt;/key&amp;gt;
  &amp;lt;false/&amp;gt;
  &amp;lt;key&amp;gt;WatchPat...</description>
</item>
<item>
<title>How to help AirPort recall passwords</title>
<link>http://www.macosxhints.com/article.php?story=2009063022354146</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=2009063022354146</guid>
<pubDate>Tue, 07 Jul 2009 07:30:03 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=2009063022354146#comments</comments>
<dc:subject>Network</dc:subject>
<description>The following situation describes a common problem people seem to be having with AirPort reconnections. While most people do not seem to have these symptoms, many, including me, have experienced the following problem with AirPort:
&lt;br&gt;&lt;br&gt;
You connect to a password-protected wireless network. In the process, you check the box requesting that AirPort remember the network and password. When you start up your computer, or when you restart your AirPort card, AirPort connects to your preferred network with no difficulty. Hooray, AirPort remembers the password!
&lt;br&gt;&lt;br&gt;
However, if you get disconnected and try to reconnect without restarting AirPort or rebooting, AirPort prompts you for a password. For some reason, AirPort forgets that it already has the password. If you try to switch networks on-the-fly, the same thing happens -- AirPort seems to forget that it already has the password.
&lt;br&gt;&lt;br&gt;
What's really going on here is that on-the-fly network switches utilize password and permissi...</description>
</item>
<item>
<title>Make SMB shares appear in Devices section of Finder sidebar</title>
<link>http://www.macosxhints.com/article.php?story=20090628121906122</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20090628121906122</guid>
<pubDate>Thu, 02 Jul 2009 07:30:01 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090628121906122#comments</comments>
<dc:subject>Network</dc:subject>
<description>It was driving me nuts that SMB shares from my Windows server would not reappear under DEVICES in the sidebar. However, I then figured out that I can do this:
&lt;ol&gt;
&lt;li&gt;Open System Preferences &amp;raquo; Network&lt;/li&gt;
&lt;li&gt;Click the network interface you use for the shares&lt;/li&gt;
&lt;li&gt;Click on the Advanced button at lower right&lt;/li&gt;
&lt;li&gt;Click on WINS tab, and manually enter the workgroup name of the server&lt;/li&gt;
&lt;li&gt;Click the '+' under the WINS Servers list&lt;/li&gt;
&lt;li&gt;Enter the IP of the server (you &lt;em&gt;are&lt;/em&gt; using static IP on your server, right?)&lt;/li&gt;
&lt;li&gt;Click OK, Apply, etc. until you're done&lt;/li&gt;
&lt;/ol&gt;
The next time I dragged a mounted share to Devices, it then showed up there automatically after the next unmount/mount. My shares seem to mount much faster now, as well. Now if only I could find a way to increase the transfer speed...sigh.</description>
</item>
<item>
<title>One way to quickly connect to a Cisco VPN</title>
<link>http://www.macosxhints.com/article.php?story=20090625012729678</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20090625012729678</guid>
<pubDate>Mon, 29 Jun 2009 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090625012729678#comments</comments>
<dc:subject>Network</dc:subject>
<description>In February, &lt;a href=&quot;http://www.macosxhints.com/article.php?story=20090220063523591&quot;&gt;this hint&lt;/a&gt; explainted how to install &lt;tt&gt;vpnc&lt;/tt&gt; as a replacement for the Cisco VPN client. I finally got it working with a little tweaking and divergence from the original instructions, based in part on follow-up comments.
&lt;br&gt;&lt;br&gt;
But what I really wanted was to have my VPN as easy (or easier) to activate than using the (otherwise awful) Cisco application: largely because I use my company's VPN in conjunction with 3G mobile broadband, which has a habit of dropping connection when my commuter train goes through a tunnel, requiring regular reconnection!
&lt;br&gt;&lt;br&gt;
I tried using Shimo and vpntool with no success, and finally got it working using the following solution...
&lt;ol&gt;
&lt;li&gt;Install &lt;a href=&quot;http://pdb.finkproject.org/pdb/package.php/vpnc&quot;&gt;vpnc using Fink&lt;/a&gt; (as per earlshango's suggestion in the original comments). You need to add the 'unstable' repository when you configure Fink, since vp...</description>
</item>
<item>
<title>Mutihoming with one Ethernet interface</title>
<link>http://www.macosxhints.com/article.php?story=2007101109301541</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=2007101109301541</guid>
<pubDate>Mon, 08 Jun 2009 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=2007101109301541#comments</comments>
<dc:subject>Network</dc:subject>
<description>Like many small businesses we have taken advantage of the 'free' DSL services offered as part of an existing mobile phone contract. In this case we use Orange for mobile service (we're based in the UK) and they offer 2 Mbit internet with a wireless router for no extra if you have at least one pay monthly account. I thought that it would be a useful addition to our network for testing and backup, especially as it is from a different ISP and delivered over a physically separate landline from our business internet.
&lt;br&gt;&lt;br&gt;
The wireless router arrived yesterday and the DSL activation happened on time so that the line came up first time when I plugged the line into the router. I'd heard a few horror stories about Orange's support for Macs so I was pleasantly surprised when I popped the install CD into my MacBook and it came with full OSX installation instructions. 5 minutes later I was surfing on the internet via my shiny new Orange broadband.
&lt;br&gt;&lt;br&gt;
Now that we had two internet acces...</description>
</item>
<item>
<title>Easily stream audio and video between two Macs</title>
<link>http://www.macosxhints.com/article.php?story=20090501102602524</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20090501102602524</guid>
<pubDate>Mon, 04 May 2009 07:30:02 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090501102602524#comments</comments>
<dc:subject>Network</dc:subject>
<description>Problem: I wanted to watch Live TV from a Mac upstairs in a room downstairs with another Mac. Hardware: Elgato EyeTV EZ, AirPort, and two Macs. There are some streaming solutions out there (VLC, CyTV, EyeTV, etc.), but they either do not support my hardware, or seem complicated, or stream re-encoded video only (no live TV, of course).
&lt;br&gt;&lt;br&gt;
But there's a really simple solution: OS X 10.5's Screen Sharing, which works flawlessly and 'streams' all of my Mac's contents. The only pity is that it doesn't send the audio as well. Enter &lt;a href=&quot;http://abyssoft.com/software/soundfly/&quot;&gt;Soundfly&lt;/a&gt; -- it streams audio in good quality (various settings available). Now with Screen Sharing and Soundfly running, I can watch live TV and movies downstairs. Because I also can remotely control the Mac upstairs, it's also possible to start and stop recordings, and more. This works quite well.
&lt;br&gt;&lt;br&gt;
Note: As far as I can tell, Soundfly simply redirects the audio from one Mac to the other -- the ...</description>
</item>
<item>
<title>A fix for failed Airport Extreme-N access control list updates</title>
<link>http://www.macosxhints.com/article.php?story=20090427121326738</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20090427121326738</guid>
<pubDate>Wed, 29 Apr 2009 07:30:03 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090427121326738#comments</comments>
<dc:subject>Network</dc:subject>
<description>I have confirmed this bug at two sites using seven different AirPort Base Stations. I thought I had updated the Access Control List (ACL) on multiple Base Stations to allow several new computers and devices on the networks. Afterwards, however, users claimed trouble accessing in some locations -- that turned out to be true anywhere there was an AirPort Extreme-N Base Station; the older AirPort-Gs worked fine. Here's the mix of gear I was using to confirm this issue:
&lt;ul&gt;
&lt;li&gt;Airport Utility v5.4.1&lt;/li&gt;
&lt;li&gt;Airport Extreme-N Firmware v7.4.1&lt;/li&gt;
&lt;li&gt;Airport Extreme-N Base Station (both 10/100 and 10/100/1000 versions) with an existing ACL&lt;/li&gt;
&lt;li&gt;PowerMac G5 - Mac OS 10.5.6 Server &lt;/li&gt;
&lt;li&gt;PowerMac G4 - Mac OS 10.4.11&lt;/li&gt;
&lt;/ul&gt;
The Problem: Using Airport Utility v5.4.1, importing an Access Control List (File &amp;raquo; (Option key) Import Access Controls) shows the updated ACL in the Access tab list.  When the Base Station is updated and the configuration redisplayed, none of the new...</description>
</item>
<item>
<title>10.5: Back to My Mac fails to start due to incorrect time</title>
<link>http://www.macosxhints.com/article.php?story=20090426003359543</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20090426003359543</guid>
<pubDate>Mon, 27 Apr 2009 07:30:03 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090426003359543#comments</comments>
<dc:subject>Network</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/105only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;For some time now, Back to My Mac (BTMM) has failed to start on my Mac Mini at home, although it worked fine on my MacBook Pro from the same network. After trying many many different things and following a number of hints, I remembered reading that BTMM uses &lt;a href=&quot;http://en.wikipedia.org/wiki/Ipsec&quot;&gt;IPsec&lt;/a&gt;. IPsec tunnels require endpoints to have their clocks synced, or at least to be set to times that are relatively close to one another. 
&lt;br&gt;&lt;br&gt;
I noticed the time on my Mac Mini differed from that of my MacBook Pro by about 10 minutes, and was failing to update its local time via &lt;em&gt;time.apple.com&lt;/em&gt; (on the Date &amp;amp; Time tab of the Date &amp;amp; Time System Preferences panel). I switched it to &lt;em&gt;time.asia.apple.com&lt;/em&gt;, the clock updated, and BTMM connected immediately after I clicked Start in the Mobile Me System Preferences panel.
&lt;br&gt;&lt;br&gt;
See the comments for some recom...</description>
</item>
<item>
<title>Log in to a single SMB share with multiple user names</title>
<link>http://www.macosxhints.com/article.php?story=20090408122756546</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20090408122756546</guid>
<pubDate>Thu, 09 Apr 2009 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090408122756546#comments</comments>
<dc:subject>Network</dc:subject>
<description>I was having trouble connecting to multiple directories on a single SMB share in Leopard, where the directories had different logins. If I was logged into one directory as one user, then the &quot;Connect to Server...&quot; option in the Finder would default to that user for all directories on the same share and error out. I found a workaround for this.
&lt;br&gt;&lt;br&gt;
With one directory already mounted under the first user login, select  Go &amp;raquo; Connect to Server. Type in your share name with the user before the drive name:

&lt;pre&gt;&lt;code&gt;smb://2ndusername@drivename/2ndDirectory&lt;/code&gt;&lt;/pre&gt;

Finder will then prompt you for a password, and mount the directory as a separate network drive. This should also work for AFP shares, though I haven't tried it.</description>
</item>
</channel>
</rss>
