<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<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>robg@macosxhints.com</managingEditor>
<webMaster>robg@macosxhints.com</webMaster>
<copyright>Copyright 2009 macosxhints.com</copyright>
<generator>GeekLog</generator>
<pubDate>Tue, 07 Jul 2009 07:35:02 -0700</pubDate>
<language>en-gb</language>
<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/MacosxhintscomNetworkTips" type="application/rss+xml" /><item>
<title>How to help AirPort recall passwords</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/ZbSUph5l4OM/article.php</link>
<guid isPermaLink="false">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...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=ZbSUph5l4OM:deFwo7a8Z1k:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=ZbSUph5l4OM:deFwo7a8Z1k:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=ZbSUph5l4OM:deFwo7a8Z1k:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=ZbSUph5l4OM:deFwo7a8Z1k:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=ZbSUph5l4OM:deFwo7a8Z1k:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=ZbSUph5l4OM:deFwo7a8Z1k:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=ZbSUph5l4OM:deFwo7a8Z1k:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/ZbSUph5l4OM" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=2009063022354146</feedburner:origLink></item>
<item>
<title>Make SMB shares appear in Devices section of Finder sidebar</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/eVH0SKO6TrM/article.php</link>
<guid isPermaLink="false">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 » 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.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=eVH0SKO6TrM:0AV6XClPRgg:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=eVH0SKO6TrM:0AV6XClPRgg:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=eVH0SKO6TrM:0AV6XClPRgg:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=eVH0SKO6TrM:0AV6XClPRgg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=eVH0SKO6TrM:0AV6XClPRgg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=eVH0SKO6TrM:0AV6XClPRgg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=eVH0SKO6TrM:0AV6XClPRgg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/eVH0SKO6TrM" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20090628121906122</feedburner:origLink></item>
<item>
<title>One way to quickly connect to a Cisco VPN</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/0cOKNDbWJzA/article.php</link>
<guid isPermaLink="false">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="http://www.macosxhints.com/article.php?story=20090220063523591"&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="http://pdb.finkproject.org/pdb/package.php/vpnc"&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 vpnc is...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=0cOKNDbWJzA:oi3wi9tdo-E:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=0cOKNDbWJzA:oi3wi9tdo-E:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=0cOKNDbWJzA:oi3wi9tdo-E:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=0cOKNDbWJzA:oi3wi9tdo-E:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=0cOKNDbWJzA:oi3wi9tdo-E:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=0cOKNDbWJzA:oi3wi9tdo-E:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=0cOKNDbWJzA:oi3wi9tdo-E:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/0cOKNDbWJzA" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20090625012729678</feedburner:origLink></item>
<item>
<title>Mutihoming with one Ethernet interface</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/f2-gE9WJb08/article.php</link>
<guid isPermaLink="false">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 accesses ...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=f2-gE9WJb08:MOy6oi28w7o:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=f2-gE9WJb08:MOy6oi28w7o:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=f2-gE9WJb08:MOy6oi28w7o:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=f2-gE9WJb08:MOy6oi28w7o:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=f2-gE9WJb08:MOy6oi28w7o:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=f2-gE9WJb08:MOy6oi28w7o:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=f2-gE9WJb08:MOy6oi28w7o:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/f2-gE9WJb08" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=2007101109301541</feedburner:origLink></item>
<item>
<title>Easily stream audio and video between two Macs</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/VSZs6M4wPDo/article.php</link>
<guid isPermaLink="false">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="http://abyssoft.com/software/soundfly/"&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 ...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=VSZs6M4wPDo:UTEgElByNtw:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=VSZs6M4wPDo:UTEgElByNtw:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=VSZs6M4wPDo:UTEgElByNtw:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=VSZs6M4wPDo:UTEgElByNtw:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=VSZs6M4wPDo:UTEgElByNtw:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=VSZs6M4wPDo:UTEgElByNtw:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=VSZs6M4wPDo:UTEgElByNtw:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/VSZs6M4wPDo" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20090501102602524</feedburner:origLink></item>
<item>
<title>A fix for failed Airport Extreme-N access control list updates</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/j6ldEAXrzQ4/article.php</link>
<guid isPermaLink="false">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 » (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 ACL ...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=j6ldEAXrzQ4:EgLGB9Aq35o:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=j6ldEAXrzQ4:EgLGB9Aq35o:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=j6ldEAXrzQ4:EgLGB9Aq35o:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=j6ldEAXrzQ4:EgLGB9Aq35o:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=j6ldEAXrzQ4:EgLGB9Aq35o:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=j6ldEAXrzQ4:EgLGB9Aq35o:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=j6ldEAXrzQ4:EgLGB9Aq35o:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/j6ldEAXrzQ4" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20090427121326738</feedburner:origLink></item>
<item>
<title>10.5: Back to My Mac fails to start due to incorrect time</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/NbUi5v0FtxU/article.php</link>
<guid isPermaLink="false">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="http://www.macosxhints.com/images/105only.png" align="left" style="margin-right: 10px"&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="http://en.wikipedia.org/wiki/Ipsec"&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...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=NbUi5v0FtxU:G-ICpDh9xBA:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=NbUi5v0FtxU:G-ICpDh9xBA:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=NbUi5v0FtxU:G-ICpDh9xBA:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=NbUi5v0FtxU:G-ICpDh9xBA:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=NbUi5v0FtxU:G-ICpDh9xBA:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=NbUi5v0FtxU:G-ICpDh9xBA:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=NbUi5v0FtxU:G-ICpDh9xBA:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/NbUi5v0FtxU" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20090426003359543</feedburner:origLink></item>
<item>
<title>Log in to a single SMB share with multiple user names</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/92QdNrccHgE/article.php</link>
<guid isPermaLink="false">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 "Connect to Server..." 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 » 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.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=92QdNrccHgE:tye8RR_l9Bo:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=92QdNrccHgE:tye8RR_l9Bo:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=92QdNrccHgE:tye8RR_l9Bo:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=92QdNrccHgE:tye8RR_l9Bo:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=92QdNrccHgE:tye8RR_l9Bo:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=92QdNrccHgE:tye8RR_l9Bo:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=92QdNrccHgE:tye8RR_l9Bo:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/92QdNrccHgE" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20090408122756546</feedburner:origLink></item>
<item>
<title>Wirelessly connect Nintendo systems to Time Capsule</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/fmzFyGcxu8k/article.php</link>
<guid isPermaLink="false">http://www.macosxhints.com/article.php?story=2009040608233466</guid>
<pubDate>Tue, 07 Apr 2009 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=2009040608233466#comments</comments>
<dc:subject>Network</dc:subject>
<description>For some reason, the Nintendo DSi cannot currently connect to a WEP-protected network on the Time Capsule. However, when you remove the WEP key, the Wii will no longer be able to connect as-is. Here is the only way I've found so far to get all three current Nintendo systems to connect to the Time Capsule's network:&lt;ul&gt;&lt;li&gt;Remove any security settings (you can still use MAC address filtering and have a closed network, however).&lt;/li&gt;&lt;li&gt;Manually set up the connection on the DS/DS lite/DSi by just entering the network's name&lt;/li&gt;&lt;li&gt;Manually set up the connection on the Wii by entering the network's name and DNS servers&lt;/li&gt;&lt;/ul&gt;You should now have all three systems connected to your network, and be able to use all the online features. If anyone finds a better solution, please post it in the comments.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=fmzFyGcxu8k:uTJWIh2gurI:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=fmzFyGcxu8k:uTJWIh2gurI:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=fmzFyGcxu8k:uTJWIh2gurI:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=fmzFyGcxu8k:uTJWIh2gurI:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=fmzFyGcxu8k:uTJWIh2gurI:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=fmzFyGcxu8k:uTJWIh2gurI:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=fmzFyGcxu8k:uTJWIh2gurI:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/fmzFyGcxu8k" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=2009040608233466</feedburner:origLink></item>
<item>
<title>One way to share links to networked files</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/fjqSRPmid88/article.php</link>
<guid isPermaLink="false">http://www.macosxhints.com/article.php?story=20090313071515523</guid>
<pubDate>Mon, 23 Mar 2009 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090313071515523#comments</comments>
<dc:subject>Network</dc:subject>
<description>Problem: You work with 50 people using Macs, and you need to direct someone to a file on the server which is buried 12 layers deep in the folder hierarchy. Unlike the web, OS X provides no way to "bookmark" a file.&lt;br&gt;&lt;br&gt;Solution:&lt;ol&gt;&lt;li&gt;Drag the file into an empty Firefox window. &lt;/li&gt;&lt;li&gt;Copy and paste the file path from Firefox's address bar.&lt;/li&gt;&lt;li&gt;Share by email, iChat, or whatever.&lt;/li&gt;&lt;/ol&gt; Comment: This is the most elegant solution -- and it's far from that  -- that I can find. It seems absurd the Finder can't do this. We waste thousands of man hours per year because there's no easy way to share locations of files on our server; that seems as sensible as the web without hyperlinks! If you have alternative solutions, please share them in the comments.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=fjqSRPmid88:fWvSz2hzGAk:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=fjqSRPmid88:fWvSz2hzGAk:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=fjqSRPmid88:fWvSz2hzGAk:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=fjqSRPmid88:fWvSz2hzGAk:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=fjqSRPmid88:fWvSz2hzGAk:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=fjqSRPmid88:fWvSz2hzGAk:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=fjqSRPmid88:fWvSz2hzGAk:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/fjqSRPmid88" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20090313071515523</feedburner:origLink></item>
<item>
<title>10.5: Install (or boot from) an image over local network</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/woLz8h3PkO4/article.php</link>
<guid isPermaLink="false">http://www.macosxhints.com/article.php?story=20090317042911165</guid>
<pubDate>Fri, 20 Mar 2009 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090317042911165#comments</comments>
<dc:subject>Network</dc:subject>
<description>&lt;img src="http://www.macosxhints.com/images/105only.png" align="left" style="margin-right: 10px"&gt;I needed to reinstall OS X, but my discs were broken. Fortunately, I had an image of the installation DVD on my server, so I figured that I should be able to boot into that image over the network. Well, it wasn't &lt;em&gt;that&lt;/em&gt; easy.
&lt;br&gt;&lt;br&gt;
In the end what you will need is a computer running two servers: one tftp server and one web or NFS server, preferably NFS, since you don't have to worry about making sure you have Apache 2 or newer to support huge file transfers over http. You'll also need some command-line skills, too.
&lt;br&gt;&lt;br&gt;
The first step is to get four files:
&lt;ol&gt;
&lt;li&gt;A bootloader&lt;/li&gt;
&lt;li&gt;A kernel&lt;/li&gt;
&lt;li&gt;An mkext file (which is a bunch of drivers)&lt;/li&gt;
&lt;li&gt;The image you wish to boot&lt;/li&gt;
&lt;/ol&gt;
All of these items are actually relatively easy to get. The first three are obtainable from inside a functioning OS X environment (or rather, an environment into which you, at the ver...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=woLz8h3PkO4:YPJZ0GTEIaI:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=woLz8h3PkO4:YPJZ0GTEIaI:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=woLz8h3PkO4:YPJZ0GTEIaI:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=woLz8h3PkO4:YPJZ0GTEIaI:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=woLz8h3PkO4:YPJZ0GTEIaI:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=woLz8h3PkO4:YPJZ0GTEIaI:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=woLz8h3PkO4:YPJZ0GTEIaI:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/woLz8h3PkO4" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20090317042911165</feedburner:origLink></item>
<item>
<title>10.5: Enable and disable the firewall via AppleScript</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/cFFafMkB3jw/article.php</link>
<guid isPermaLink="false">http://www.macosxhints.com/article.php?story=20090217124731597</guid>
<pubDate>Fri, 20 Feb 2009 07:30:03 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090217124731597#comments</comments>
<dc:subject>Network</dc:subject>
<description>&lt;img src="http://www.macosxhints.com/images/105only.png" align="left" style="margin-right: 10px"&gt;I started using &lt;A HREF="http://www.symonds.id.au/marcopolo/"&gt;MarcoPolo&lt;/A&gt; recently to switch networks on my Macbook when moving between home and work. I also wanted to turn the firewall on and off easily, but could not find and scripts to switch the Leopard firewall between "Allow all incoming connections" (my definition of OFF) and "Allow only essential services" (ON).
&lt;br&gt;&lt;br&gt;
So here is the ON script:

&lt;div style="margin-left: 20px; margin-top:10px; margin-bottom:10px; padding: 5px; border:1px solid; width:520px; height:120px; overflow:scroll;white-space:nowrap"&gt;&lt;a title="Drag-select from top-to-bottom, then copy, and paste into Script Editor"&gt;&lt;pre&gt;&lt;code&gt;-- Firewall on script
--
-- Growl support - remove next line if you don't use Growl
register_growl()
-- Make sure support for assistive devices is active
tell application "System Events"
  if UI elements enabled is false then
    te...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=cFFafMkB3jw:LgkzRb1lfCs:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=cFFafMkB3jw:LgkzRb1lfCs:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=cFFafMkB3jw:LgkzRb1lfCs:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=cFFafMkB3jw:LgkzRb1lfCs:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=cFFafMkB3jw:LgkzRb1lfCs:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=cFFafMkB3jw:LgkzRb1lfCs:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=cFFafMkB3jw:LgkzRb1lfCs:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/cFFafMkB3jw" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20090217124731597</feedburner:origLink></item>
<item>
<title>Install vpnc as a replacement for the Cisco VPN client</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/o1I9gQR0Z9M/article.php</link>
<guid isPermaLink="false">http://www.macosxhints.com/article.php?story=20090220063523591</guid>
<pubDate>Fri, 20 Feb 2009 07:30:02 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090220063523591#comments</comments>
<dc:subject>Network</dc:subject>
<description>Here's how to build &lt;tt&gt;vpnc&lt;/tt&gt; as a drop-in replacement for the Cisco VPN client. Why on earth would I want to do this? Because, in my opinion, Cisco's client is a pretty poor piece of software, you shouldn't have to have a Cisco contract to download the thing, and I am a big proponent of open source software.
&lt;br&gt;&lt;br&gt;
This process has been tested under Mac OS X 10.5.5 and Ubuntu Intrepid 64 bit, and it's written up in detail on &lt;a href="http://www.gdanko.net/vpnc.html"&gt;this page&lt;/a&gt; on my site. Here's the executive summary version:

Requirements:
&lt;ul&gt;
&lt;li&gt;A UNIX system. (Sorry, Windows folks. I have neither the time nor patience to even try to set it up under Windows).&lt;/li&gt;
&lt;li&gt;A development environment (Xcode).&lt;/li&gt;
&lt;li&gt;A basic working knowledge of UNIX.&lt;/li&gt;
&lt;li&gt;The ability to follow instructions.&lt;/li&gt;
&lt;/ul&gt;
Required software:
&lt;ul&gt;
&lt;li&gt;libgpg-error [&lt;a href="ftp://ftp.gnupg.org/gcrypt/libgpg-error/libgpg-error-1.6.tar.bz2"&gt;download&lt;/a&gt;]&lt;/li&gt;
&lt;li&gt;libgrcypt  ...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=o1I9gQR0Z9M:1Y_RHt5IV_k:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=o1I9gQR0Z9M:1Y_RHt5IV_k:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=o1I9gQR0Z9M:1Y_RHt5IV_k:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=o1I9gQR0Z9M:1Y_RHt5IV_k:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=o1I9gQR0Z9M:1Y_RHt5IV_k:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=o1I9gQR0Z9M:1Y_RHt5IV_k:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=o1I9gQR0Z9M:1Y_RHt5IV_k:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/o1I9gQR0Z9M" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20090220063523591</feedburner:origLink></item>
<item>
<title>Enable mounting of remote CD/DVDs on any Mac</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/BvTEomLKuL0/article.php</link>
<guid isPermaLink="false">http://www.macosxhints.com/article.php?story=2009012605560521</guid>
<pubDate>Mon, 26 Jan 2009 07:30:04 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=2009012605560521#comments</comments>
<dc:subject>Network</dc:subject>
<description>The CD/ROM in my computer busted, so I decided to try to remotely mount the CD from another computer on mine.  I know the MacBook Air can do this, so I reasoned that any Mac could. It turns out it is possible, but the solution is far from obvious -- after much searching, I &lt;a href="http://jasonevangelho.com/2008/11/02/how-to-really-enable-remote-disc-dvd-drive-sharing-non-air-macbook"&gt;found the solution here&lt;/a&gt;.
&lt;br&gt;&lt;br&gt;
Here's a quick synopsis. Go to System Preferences » Sharing, and enable 'DVD or CD Sharing.' (I think you need to do this on both machines -- the one with the drive and the one without the CD/ROM drive). Then, on the computer that does &lt;em&gt;not&lt;/em&gt; have the CD drive on it, go to a Terminal window and enter:

&lt;pre&gt;&lt;code&gt;&amp;#36; defaults write com.apple.NetworkBrowser EnableODiskBrowsing -bool true
&amp;#36; defaults write com.apple.NetworkBrowser ODSSupported -bool true&lt;/code&gt;&lt;/pre&gt;

Reboot this machine, and when the reboot is finished, you'll see the remote CD/DVD under...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=BvTEomLKuL0:RI3hkYGPNlU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=BvTEomLKuL0:RI3hkYGPNlU:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=BvTEomLKuL0:RI3hkYGPNlU:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=BvTEomLKuL0:RI3hkYGPNlU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=BvTEomLKuL0:RI3hkYGPNlU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=BvTEomLKuL0:RI3hkYGPNlU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=BvTEomLKuL0:RI3hkYGPNlU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/BvTEomLKuL0" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=2009012605560521</feedburner:origLink></item>
<item>
<title>Use VLC to watch movies before they're fully copied</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/56ShK9mGFiI/article.php</link>
<guid isPermaLink="false">http://www.macosxhints.com/article.php?story=20090117133023639</guid>
<pubDate>Fri, 23 Jan 2009 07:30:01 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090117133023639#comments</comments>
<dc:subject>Network</dc:subject>
<description>I have two computers -- a Power Mac and a MacBook. I have massive amount of storage space on my desktop, but for portability's sake, I don't typically connect hard drives to my MacBook. This means I keep all my movies on my desktop. But what if I want to watch them on my MacBook? I don't want to deal with plugging in hard drives, or waiting for a movie to transfer over the network before I start watching.
&lt;br&gt;&lt;br&gt;
So here's what I do. I first begin a file transfer across the network of the movie I want to watch. (I typically do a file copy, not a move, so when I'm done, I can just trash the file on my MacBook.) I wait a second to let it get a head start, and then open the partially-transfered movie in &lt;a href="http://www.videolan.org/vlc/download-macosx.html"&gt;VLC&lt;/a&gt;. Note that opening from the Finder won't work; either open the file inside VLC, or drag the file onto VLC in the Dock.
&lt;br&gt;&lt;br&gt;
Now, VLC is going to think the file is broken, and ask if you want to repair it -- don't. Y...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=56ShK9mGFiI:GeatGPrgYIE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=56ShK9mGFiI:GeatGPrgYIE:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=56ShK9mGFiI:GeatGPrgYIE:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=56ShK9mGFiI:GeatGPrgYIE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=56ShK9mGFiI:GeatGPrgYIE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=56ShK9mGFiI:GeatGPrgYIE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=56ShK9mGFiI:GeatGPrgYIE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/56ShK9mGFiI" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20090117133023639</feedburner:origLink></item>
<item>
<title>Require Admin rights to create Ad Hoc network</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/BqPpmV4MF8A/article.php</link>
<guid isPermaLink="false">http://www.macosxhints.com/article.php?story=20090114065040740</guid>
<pubDate>Wed, 21 Jan 2009 07:30:03 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20090114065040740#comments</comments>
<dc:subject>Network</dc:subject>
<description>In some cases, you may not want your OS X users to have the ability to create an Ad Hoc network. This can cause all kinds of issues if they are broadcasting their own SSIDs through out your network. After some extensive Google searching and hitting up some mailing lists, I was able to configure the AirPort daemon to require Administrative privileges to create an Ad Hoc network.
&lt;br&gt;&lt;br&gt;
This is not widely documented, and I have only tested it in 10.5. I also rebooted my machine to restart all daemons after running the command. If you try running it in 10.4, you will have to test it as I do not have a Tiger machine around me to test this out.
&lt;br&gt;&lt;br&gt;
Open up Terminal and run the following command:

&lt;pre&gt;&lt;code&gt;sudo /usr/libexec/airportd en1 ‑ibss_admin 1&lt;/code&gt;&lt;/pre&gt;

To undo this, simply rerun the code, but replace the ending &lt;tt&gt;1&lt;/tt&gt; with a &lt;tt&gt;0&lt;/tt&gt;, and then all users will be able to create Ad Hoc networks.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=BqPpmV4MF8A:mPkgajORMb8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=BqPpmV4MF8A:mPkgajORMb8:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=BqPpmV4MF8A:mPkgajORMb8:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=BqPpmV4MF8A:mPkgajORMb8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=BqPpmV4MF8A:mPkgajORMb8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=BqPpmV4MF8A:mPkgajORMb8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=BqPpmV4MF8A:mPkgajORMb8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/BqPpmV4MF8A" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20090114065040740</feedburner:origLink></item>
<item>
<title>Set up an AirPort Base Station for fast 802.11n-only use</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/mzfmoho8Q7c/article.php</link>
<guid isPermaLink="false">http://www.macosxhints.com/article.php?story=20081221202441899</guid>
<pubDate>Wed, 24 Dec 2008 07:30:00 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20081221202441899#comments</comments>
<dc:subject>Network</dc:subject>
<description>If you want the fastest possible wireless network, and you have all N-compatible clients, then on your AirPort Base Station, set the following options:&lt;ul&gt;&lt;li&gt;Radio Mode: 802.11n only (5GHz)&lt;/li&gt;&lt;li&gt;In the Wireless Options section, insure that Wide Channels are selected&lt;/li&gt;&lt;/ul&gt;Other vendors use wide channels in the 2.4GHz spectrum, but this is a problem as doing so can use up to 75% of this spectrum. Not great if you have a cordless phone, or neighbors that are also using 2.4GHz hardware mentioned above. As the 5GHz the channels don't overlap like they do in the 2.4GHz range, then this can be done. In 2.4GHz, if you wanted to have three non-interfering networks, they would each have to be five channels apart so that they don't overlap -- 1,6,11 for example. &lt;br&gt;&lt;br&gt;You should get speeds up to 500MB per minute between two 802.11n clients with this setup.&lt;br&gt;&lt;br&gt;[&lt;b&gt;robg adds:&lt;/b&gt; I don't know if these are ideal settings or not -- if you have advice on setting up the fastest N-only ...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=mzfmoho8Q7c:P2DWbVYcNa8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=mzfmoho8Q7c:P2DWbVYcNa8:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=mzfmoho8Q7c:P2DWbVYcNa8:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=mzfmoho8Q7c:P2DWbVYcNa8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=mzfmoho8Q7c:P2DWbVYcNa8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=mzfmoho8Q7c:P2DWbVYcNa8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=mzfmoho8Q7c:P2DWbVYcNa8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/mzfmoho8Q7c" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20081221202441899</feedburner:origLink></item>
<item>
<title>Older wireless Macs and D-Link wireless N routers</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/gHGdtmI5jrM/article.php</link>
<guid isPermaLink="false">http://www.macosxhints.com/article.php?story=20081216073411143</guid>
<pubDate>Fri, 19 Dec 2008 07:30:03 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20081216073411143#comments</comments>
<dc:subject>Network</dc:subject>
<description>I bought a new D-Link DIR-625 router and got it to work with all my computers except one -- an older PowerBook Pismo with an AirPort wireless card. I kept getting the error that it couldn't connect to the airport network. The machine would connect to my old router, and to my neighbor's router, just not my new D-Link router. For days, I tried everything I could find to fix it. I called support multiple times, and tried everything that they suggested.  Their suggestions were of no help, however.
&lt;br&gt;&lt;br&gt;
I finally stumbled on to the fix myself. I had to change the wireless mode from "B,G and N" to just "B and G," and then it worked fine. The problem is that my new MacBook has N wireless and now can't use my new N router at full speed. I guess that is why it is still called "draft" N router!&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=gHGdtmI5jrM:Y9UBxo8KZ50:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=gHGdtmI5jrM:Y9UBxo8KZ50:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=gHGdtmI5jrM:Y9UBxo8KZ50:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=gHGdtmI5jrM:Y9UBxo8KZ50:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=gHGdtmI5jrM:Y9UBxo8KZ50:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=gHGdtmI5jrM:Y9UBxo8KZ50:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=gHGdtmI5jrM:Y9UBxo8KZ50:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/gHGdtmI5jrM" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20081216073411143</feedburner:origLink></item>
<item>
<title>Toggle HTTP, FTP and HTTPS proxies via widget</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/JrCDBBabhz0/article.php</link>
<guid isPermaLink="false">http://www.macosxhints.com/article.php?story=20081212060418421</guid>
<pubDate>Mon, 15 Dec 2008 07:30:01 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20081212060418421#comments</comments>
<dc:subject>Network</dc:subject>
<description>I wrote &lt;a href="http://www.nextsoft.cz/~malina/cs/projects/fps/fps.htm"&gt;a free widget&lt;/a&gt; for switching HTTP, FTP or HTTPS proxies, and it currently works for Ethernet or AirPort networks.
&lt;br&gt;&lt;br&gt;
The widget is basically a front end for a &lt;tt&gt;bash&lt;/tt&gt; script, which does the hard work. I also had to write an Objective C tool for parsing of current configuration information. It is all free, so if somebody would like to see the source, just let me know.
&lt;br&gt;&lt;br&gt;
[&lt;b&gt;robg adds:&lt;/b&gt; I haven't tried this one.]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=JrCDBBabhz0:9Sc8JF8TsHk:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=JrCDBBabhz0:9Sc8JF8TsHk:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=JrCDBBabhz0:9Sc8JF8TsHk:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=JrCDBBabhz0:9Sc8JF8TsHk:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=JrCDBBabhz0:9Sc8JF8TsHk:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=JrCDBBabhz0:9Sc8JF8TsHk:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=JrCDBBabhz0:9Sc8JF8TsHk:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/JrCDBBabhz0" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20081212060418421</feedburner:origLink></item>
<item>
<title>10.5: Enable X11 listening on port 6000</title>
<link>http://feedproxy.google.com/~r/MacosxhintscomNetworkTips/~3/zzdvDWeKCeI/article.php</link>
<guid isPermaLink="false">http://www.macosxhints.com/article.php?story=20081208062918906</guid>
<pubDate>Wed, 10 Dec 2008 07:30:00 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20081208062918906#comments</comments>
<dc:subject>Network</dc:subject>
<description>Are you having difficulty redirecting X11 to your Mac running Leopard without using &lt;tt&gt;ssh -X&lt;/tt&gt;? Someone figured out that Leopard turns off listening to X11 traffic on TCP port 6000 by default. The following steps will TCP listening back on, so that the X11 server will service a client request. &lt;br&gt;&lt;br&gt;First see if your server has TCP listening turned off by executing the following command: &lt;tt&gt;defaults read org.x.X11 | grep nolisten&lt;/tt&gt;. The output will read either &lt;tt&gt;"nolisten_tcp" = 1;&lt;/tt&gt; which is bad, or &lt;tt&gt;"nolisten_tcp" = 0;&lt;/tt&gt; which is good. If TCP listening is off, turn it back on. I did this both as root and my default non-root username, as I didn't know which one took precedence:&lt;pre&gt;&lt;code&gt;sudo defaults write org.x.X11 nolisten_tcp 0defaults write org.x.X11 nolisten_tcp 0&lt;/code&gt;&lt;/pre&gt;Shut down your X11.app, then in Terminal, type &lt;tt&gt;xterm&lt;/tt&gt;, and as normal, the X11 terminal should pop-up. In the xterm, enable all remote users by typing &lt;tt&gt;xhost +&lt;/tt&gt;. Back ...&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=zzdvDWeKCeI:DTJ-MX8sEWA:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=zzdvDWeKCeI:DTJ-MX8sEWA:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=zzdvDWeKCeI:DTJ-MX8sEWA:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=zzdvDWeKCeI:DTJ-MX8sEWA:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=zzdvDWeKCeI:DTJ-MX8sEWA:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?a=zzdvDWeKCeI:DTJ-MX8sEWA:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/MacosxhintscomNetworkTips?i=zzdvDWeKCeI:DTJ-MX8sEWA:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/MacosxhintscomNetworkTips/~4/zzdvDWeKCeI" height="1" width="1"/&gt;</description>
<feedburner:origLink>http://www.macosxhints.com/article.php?story=20081208062918906</feedburner:origLink></item>
</channel>
</rss>
