<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Network Garage Engineers</title>
    <link rel="alternate" type="text/html" href="http://www.networkgarage.com/brett/" />
    <link rel="self" type="application/atom+xml" href="http://www.networkgarage.com/brett/atom.xml" />
   <id>tag:www.networkgarage.com,2008:/brett/4</id>
    <link rel="service.post" type="application/atom+xml" href="http://www.networkgarage.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=4" title="Network Garage Engineers" />
    <updated>2006-05-08T22:30:02Z</updated>
    <subtitle>Where you can talk with our engineering team and tell them what you think!</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.2</generator>
 
<entry>
    <title>Wireless Network Manager Is Going Back To Beta</title>
    <link rel="alternate" type="text/html" href="http://www.networkgarage.com/brett/2006/05/a_blue_day_at_network_magic.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.networkgarage.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=247" title="Wireless Network Manager Is Going Back To Beta" />
    <id>tag:www.networkgarage.com,2006:/brett//4.247</id>
    
    <published>2006-05-05T15:09:08Z</published>
    <updated>2006-05-08T22:30:02Z</updated>
    
    <summary>We had to make a hard decision today at Network Magic that will affect many of our customers. We decided to remove our &quot;Wireless Network Manager&quot; feature from our latest release and put it back into Beta for more testing....</summary>
    <author>
        <name>Brett Marl</name>
        
    </author>
            <category term="Brett" />
    
    <content type="html" xml:lang="en" xml:base="http://www.networkgarage.com/brett/">
        <![CDATA[<p>We had to make a hard decision today at Network Magic that will affect many of our customers. We decided to remove our "Wireless Network Manager" feature from our latest release and put it back into Beta for more testing. Read on and I'll give you some more insight into why we made this decision and when you can expect to get your feature back! <br />
</p>]]>
        <![CDATA[<p>When we launched our recent set of improvements earlier this month, one of the great new features we added was "Wireless Network Manager". It allows Network Magic to be the primary manager of your wireless connections. We were excited to get this feature to our users as we thought it was a huge improvement over what the standard wireless connection manager in Windows XP (Known as Microsoft ZeroConfig) provides. In our (humble) opinion, we added some improved features and a better interface to manage your wireless networks.</p>

<p>However, we ran into one major snag: <b>The feature didn't work with every wireless card out there.</b></p>

<p>Building a wireless manager feature is hard. You need to build a component known as an "NDIS driver", and to do this have to write what is known as kernel-level code. This is code the runs in the very low level guts of Windows and works directly with your specific hardware. Josh – one of our developers worked hard on our NDIS driver for months. In our QA lab (and in Dogfood testing), we have tested the driver with over a hundred different wireless network cards. Our confidence was high as we didn't see any show-stopper bugs in our lab.</p>

<p>After we launched 3.0 our support team started receiving a lot of calls from users that were having stability issues with our NDIS driver. We’ve been working hard these last few weeks trying to replicate or reproduce the problems in house, so that our development team can fix them. However, we're not having much luck. So far we have not been able to replicate a single hang or blue-screen in house. There are so many network cards out there with so many different permutations of software people have installed on their machines. It's really tricky to replicate the same environment in the lab so we can reproduce the issue. To compound things further - our NDIS driver is at the mercy of buggy 3rd party driver software. For example, we've found a few drivers that ask for an n-byte buffer to write data into but then proceed to write n+1 bytes into it. Get the wrong byte out of line and BOOM! - you blue-screen. </p>

<p>While this is only affecting a very small percentage of Network Magic users (~1%) at this time, the severity of the impact to those users is very painful. We think it's prudent to remove this feature from the product until we can make it bomb-proof. We can only do magic to peoples networks if we're making things better, not if we're making things worse. </p>

<p>Our plan is to package "Wireless Network Manager" into a separate Beta download and post it on the <a href="http://www.networkmagic.com/labs">Network Magic Labs</a> page. That way if users still want to try it, they can simply download the beta installer without being forced to get it as part of the base Network Magic install. Once we have had enough beta testing and have stabilized across the majority of network cards out there, we'll put the feature back into the main product release.</p>

<p>Of course, we're going to be very dependant on a few loyal beta users that are willing to put our Wireless Network Manager feature through it's paces and give us feedback along the way. Keep checking the <a href="http://www.networkmagic.com/labs/">Labs page</a> and we will have more info about our Beta program!</p>

<p>Please post comments on this entry and let us know what you think. Did we make the right call?<br />
</p>]]>
    </content>
</entry>
<entry>
    <title>Free Network Backup</title>
    <link rel="alternate" type="text/html" href="http://www.networkgarage.com/brett/2006/04/poor_mans_backup.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.networkgarage.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=239" title="Free Network Backup" />
    <id>tag:www.networkgarage.com,2006:/brett//4.239</id>
    
    <published>2006-04-27T09:07:15Z</published>
    <updated>2006-04-27T19:47:46Z</updated>
    
    <summary>Have you ever lost sleep at night worrying about the funny scraping noise your hard drive was starting to make and trying to remember if you backed up any of your photos or files in the last year? I have...</summary>
    <author>
        <name>Brett Marl</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.networkgarage.com/brett/">
        <![CDATA[<p>Have you ever lost sleep at night worrying about the funny scraping noise your hard drive was starting to make and trying to remember if you backed up any of your photos or files in the last year?</p>

<p>I have the cure for your insomnia. Read on and I'll show you how to cobble together a Network Backup system with <a href="http://www.networkmagic.com">Network Magic</a> and <a href="http://www.microsoft.com/windowsxp/using/digitalphotography/prophoto/synctoy.mspx">Microsoft SyncToy</a>.</p>]]>
        <![CDATA[<h3 class="entry-header">Overview</h3>
Microsoft has a nifty free app called <a href="http://www.microsoft.com/windowsxp/using/digitalphotography/prophoto/synctoy.mspx">SyncToy</a> that allows you to do many  different types of file synchronization between folders. By using the Network Magic <b>Shared Folders</b> feature, you can also set it up to do syncrhonization across your network from one computer (Backup "Source") to another computer (Backup "Target"). I'll also show you how to use the task scheduler on Windows XP to make it automatically happen every night at 3am.

<p>Here are the prerequisites for the steps in this post:<br />
<ul><br />
    <li>Install <a href="http://www.networkmagic.com">Network Magic</a> on at least 2 PCs (The backup "Source" and the backup "Target")<br />
    <li>Download and install <a href="http://www.microsoft.com/windowsxp/using/digitalphotography/prophoto/synctoy.mspx">SyncToy</a> on the <b>Backup Source</b> PC<br />
<li>Create a <a href="http://www.networkmagic.com">Network Magic</a> Shared Folder on the <b>Backup Target</b> PC where you want <br />
your backups to go<br />
</ul><br />
Okay, if you're sitting comfortably, let's begin:</p>

<p>1. Open SyncToy and click on the <b>"Create New Folder Pair"</b> button.<br />
<div align="center"><img style="margin-top: 20px; margin-bottom: 20px" src="/brett/1.sync.toy.main.jpg"></div></p>

<p>2. On page 1 of the wizard, set the <b>Left Folder</b> to be the <b>Backup Source</b> location you want to backup. In my case, I like to keep a backup of things under "My Documents". Then hit <b>Next</b>.<br />
<div align="center"><img style="margin-top: 20px; margin-bottom: 20px" src="/brett/2.wiz.part1.jpg"></div></p>

<p>3. On page 2, click on the <b>Browse</b> button for the right folder pair.<br />
<div align="center"><img style="margin-top: 20px; margin-bottom: 20px" src="/brett/3.wiz.part2.jpg"></div></p>

<p>4. This will bring up the <b>Browse for Folder</b> dialog. You can use the "<a href="http://www.networkmagic.com">Network Magic</a> Folders" node to easily navigate to the shared folder on your network where you want the backups to be stored - the <b>Backup Target</b>. Once you are done, click <b>OK</b> and then <b>Next</b> on the Wizard page.<br />
<div align="center"><img style="margin-top: 20px; margin-bottom: 20px" src="/brett/4.wiz.part2b.jpg"></div></p>

<p>5. On the 3rd page of the Wizard you will be asked what type of sync operation you want to perform. For doing backups, I prefer to use the <b>"Echo"</b> option. This will perform a one-way sync always from the source machine to the target machine. It's useful incase I ever want to modify the target machine files - (e.g. archive them into a .zip file) and I don't want the changes to affect my desktop PC. Click <b>Next</b> when you're done.<br />
<div align="center"><img style="margin-top: 20px; margin-bottom: 20px" src="/brett/5.wiz.part3.jpg"></div></p>

<p>6. On the final page of the Wizard enter a <b>name</b> for your backup. Pick something easy to remember as we'll us this again later when setup an automatic schedule.<br />
<div align="center"><img style="margin-top: 20px; margin-bottom: 20px" src="/brett/6.wiz.part4.jpg"></div></p>

<p>7. OK... We're half way there. Now you can go into Sync Toy at any time and perform a backup. But, let's automate it, so that our backups happen at 3am every day. First step is to open the <b>Scheduled Tasks</b> application from the Control Panel, and choose "Add Scheduled Task"<br />
<div align="center"><img style="margin-top: 20px; margin-bottom: 20px" src="/brett/ts.1.menu.jpg"></div></p>

<p>8. On Page 1 of the Scheduled Task Wizard, choose <b>SyncToy</b> for the program to schedule. Then click Next.<br />
<div align="center"><img style="margin-top: 20px; margin-bottom: 20px" src="/brett/ts.2.app.select.jpg"></div></p>

<p>9. On the Next Page, choose the Daily Option and click Next. On the next 2 screens (Not shown here), enter the time you want to  start and also your Windows username and password. Task Scheduler will use this logon information to get access to your documents if nobody  is logged into the machine. Make sure the Windows username you select has permissions to access to the folder you want to sync.<br />
<div align="center"><img style="margin-top: 20px; margin-bottom: 20px" src="/brett/ts.3.schedule.jpg"></div></p>

<p>10. On the Last Page, check the <b>"Open Advanced Properties"</b> option and click Finish.<br />
<div align="center"><img style="margin-top: 20px; margin-bottom: 20px" src="/brett/ts.4.edit.advanced.jpg"></div></p>

<p>11. Now for the final step, when the Advanced properties come up you need to add the following to the end of the command: <br />
<div style="margin-left: 30px"><br />
<b>-R "[Your SyncToy Task Name]"</b><br />
<i>where [Your SyncToy Task Name] is the name you chose in step 6. If the name has spaces in it, it needs to be enclosed in quotes.</i><br />
</div><br />
<div align="center"><img style="margin-top: 20px; margin-bottom: 20px" src="/brett/ts.5.edit.cmdline.jpg"></div><br />
<br><br />
That should do it, fresh automatic backups every day. I hope you sleep well tonight.<br />
</p>]]>
    </content>
</entry>
<entry>
    <title>Just how secure is our Wireless Protection feature?</title>
    <link rel="alternate" type="text/html" href="http://www.networkgarage.com/brett/2006/04/just_how_secure_is_our_wireles_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.networkgarage.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=228" title="Just how secure is our Wireless Protection feature?" />
    <id>tag:www.networkgarage.com,2006:/brett//4.228</id>
    
    <published>2006-04-14T22:25:37Z</published>
    <updated>2006-04-18T07:16:43Z</updated>
    
    <summary>For Network Magic 3.0 we implemented the ability to lock a wireless network. We call this feature &quot;Wireless Protection&quot;. There are three common ways to secure a wireless network using the most common infrastructure available today. Deciding which one to...</summary>
    <author>
        <name>Brett Marl</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.networkgarage.com/brett/">
        <![CDATA[<p>For Network Magic 3.0 we implemented the ability to lock a wireless network. We call this feature "Wireless Protection". </p>

<p>There are three common ways to secure a wireless network using the most common infrastructure available today. Deciding which one to base our initial security approach on met a lot of debate here at Network Magic. There are usually two camps in the debate – the <b>security purists</b> and the <b>user advocates</b>. <img style="margin: 5px" src="http://www.networkgarage.com/brett/images/wsc.normal.128.gif" align=right></p>

<p>I’m more in the latter camp. I care about security as much as it :</p>

<p>a) provides reasonable defense against my most likely threat and <br />
b) is easy for me to implement.</p>

<p>We’ve all heard the "IT policy" horror-stories. Where the IT department decided to crack down on <a href="http://en.wikipedia.org/wiki/Strong_password">strong passwords</a>: </p>

<div style="margin: 20px; padding: 5px; background-color: #F0FFFF; border: gray solid 1px">&quot;Your password must be 10 digits or longer, contain a mix of upper and lowercase, contain several numbers and at least one punctuation character. Oh – and you have to change it once a month, and you can’t pick from the last 9 passwords that you’ve used.&quot;</div> 

<p>Bomb proof. Secure, right? Not really, it’s so unusable from a user-point of view that people have to write their passwords down on sticky notes in front of their workstation to remember them all. Great technical solution, flawed execution.</p>

<p>So let's look at each of the 3 main ways and hear the debate… then I’ll tell you what we did and why we did it.<br />
</p>]]>
        <![CDATA[<h1 class=entry-header>Security Options</h1>

<p><b>1. MAC Address Filtering</b><br />
<br>MAC address filtering is a simple security measure. A MAC address is a unique address assigned to devices and computers. By maintaining an ‘approved’ list of MAC addresses on the router, it can deny access to any new machine that is not on the list. There are several shortcomings to this approach:</p>

<p>a) you need to know the MAC addresses of the devices you want to add, not an easy thing to figure out (Unless you have <a href="http://www.networkmagic.com/product/">Network Map</a> handy). <br />
b) If a hacker knows the addresses of someone on the ‘approved list’, <img alt="tab.topo.128.gif" src="http://www.networkgarage.com/brett/images/tab.topo.128.gif" width="128" height="128" align=right style="margin: 5px" ><br />
 they can easily spoof the address and get on your network and <br />
c) even when your network is denying requests to other machines, it *is* transmitting information in the air-waves. This information is in clear-text and not encrypted in any way. A sophisticated hacker with a signal sniffer can watch what you are doing online and where you are browsing too. They can’t see the credit-card that you sent as part of check-out of a commerce transaction (Amazon.com for instance), as most commerce sites use a secure-connection (SSL) to transmit this data. </p>

<p><b>2. WEP Encryption</b><br />
WEP was the first form of wireless encryption to be available on wireless networks. To use it you have to setup a fancy password (known as a WEP-Key) in the router, and configure each computer and/or device to also know this password. <img src="http://www.networkgarage.com/brett/images/wsc.unlocked.128.gif" align=left style="margin: 5px"> Unfortunately the ‘password’ isn’t pretty - you cant use a simple password such as “BobLikesJane”. It has to be a “128-bit encryption key” that is represented as 26 hexadecimal characters. Confused? You can be sure that you mum will be. The nice thing about WEP is that once you have it setup, your data transmissions are encrypted and anyone wanting to join your network needs to enter the ‘key’. So it feels fairly secure. Another bonus is that most other network devices – such as cameras and TiVos and media-players all support it. Although punching in a 128-bit hex-key on your TiVo remote is no fun way to spend a Saturday night.</p>

<p>The biggest downside of WEP? Any hacker worth their salt can crack your key in about <a href=" http://www.tomsnetworking.com/2005/03/31/the_feds_can_own_your_wlan_too/">3 minutes or less</a>.</p>

<p><b>3. WPA Encryption</b><br />
The most common form of WPA <img alt="wsc.locked.128.gif" src="http://www.networkgarage.com/brett/wsc.locked.128.gif" width="128" height="128" style="margin: 5px" align=right> encryption in the home network space, is WPA-PSK or “Pre-Shared Key” Mode. The good news is that WPA uses a more friendly ‘password’ metaphor, so no weird hex-key voodoo. The bad news is that most home users don’t bother creating <a href="http://en.wikipedia.org/wiki/Strong_password">strong passwords</a>, and pick something like “banana” or “Johnny” which are well known words found in the dictionary. This weak-password approach can render <a href="http://wifinetnews.com/archives/002452.html">WPA as weak as WEP</a> in many cases. Which makes any WPA enabled network vulnerable to automated dictionary attacks. Another big downside to WPA is that older routers don’t support it and a lot of consumer networking devices do not support it either. This is starting to change however, and more recent updates of devices such as the <a href="http://www.slimdevices.com/">SqueezeBox</a> are coming to market with WPA. <br />
</ol></p>

<h1 class=entry-header>The Real Threat?</h1>
So where does all this leave us? Putting the technical details aside, to truly understand the merits of each approach you have to consider WHO you are defending against. I give you two possible categories of people to defend against:

<p><b>1. The intruding neighbor</b><br />
This is your busy-body, freeloading neighbor who wants to get on your network to steal bandwidth and maybe poke around to see what interesting files he can find. He’s not that talented when it comes to hacking networks and can’t really do that much damage.</p>

<p><b>2. The professional hacker</b><br />
This is the guy that sits outside your house in a white van with a <a href="http://www.oreillynet.com/cs/weblog/view/wlg/448"> Pringles can</a> over his antenna pointing directly at your network. He knows all the tricks of the trade and knows how to get into a network.</p>

<p>For the intruding neighbor, any of the security methods above are a sufficient deterrent to keep him out. For the professional hacker, MAC Address filtering is like leaving the door to your house closed with no lock. Using WEP is like barricading your door with a single strand of wet spaghetti. Using WPA is like having a box of assemble-yourself lock-parts. If you know how to arrange them in the right way, you can make a decent lock. But if the hacker REALLY wants in, he can still break the windows.</p>

<h1 class=entry-header>Conclusion</h1>
To determine the right security solution for <b>you</b>, you have to consider a) what is your real threat and b) what is your worst exposure in the event of a compromise. 

<p>I don’t keep a <a href="http://www.interamer.net/index.asp?PageAction=VIEWCATS&Category=251">Bio-Hazard</a> suit in my basement, because I really don’t think there’s going to be a chemical terrorist attack on downtown Seattle anytime soon and for <a href="http://www.interamer.net/index.asp?PageAction=VIEWCATS&Category=251">$60</a>, I’ll take my chances.</p>

<p>For Network Magic 3.0, we chose to implement MAC Filtering as our first-step security solution. We believe that this has maximum ease-of-use and still provides an improved level of security over what most people have today – no security at all.  For a future release of Network Magic, WPA seems like the next natural step.<br />
</p>]]>
    </content>
</entry>
<entry>
    <title>WEP-Open more secure than WEP-Shared? Who knew?</title>
    <link rel="alternate" type="text/html" href="http://www.networkgarage.com/brett/2006/04/wepopen_more_secure_than_wepsh.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.networkgarage.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=225" title="WEP-Open more secure than WEP-Shared? Who knew?" />
    <id>tag:www.networkgarage.com,2006:/brett//4.225</id>
    
    <published>2006-04-09T04:01:15Z</published>
    <updated>2006-04-13T18:56:31Z</updated>
    
    <summary>If you have ever setup security on a wireless network, then you have probably heard the term &quot;WEP&quot; before. While WEP has weaknesses that make it easily crackable by a sophisticated hacker, I did learn something new this weekend from...</summary>
    <author>
        <name>Brett Marl</name>
        
    </author>
            <category term="Brett" />
    
    <content type="html" xml:lang="en" xml:base="http://www.networkgarage.com/brett/">
        <![CDATA[<p>If you have ever setup security on a wireless network, then you have probably heard the term "<a href="http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy">WEP</a>" before. While <a href="http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy">WEP</a> has <a href="http://en.wikipedia.org/wiki/Related-key_attack">weaknesses</a> that make it easily crackable by a sophisticated hacker, I did learn something new this weekend from my IM with Matthew our Development Manager . </p>

<p>When configuring a <a href="http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy">WEP</a>-key in your router, <img src="http://www.networkgarage.com/brett/images/wsc.normal.128.gif" align=right style="margin: 5px"> there are two options you can choose: “<a href="http://documentation.netgear.com/reference/sve/wireless/WirelessNetworkingBasics-3-09.html">Shared</a>” or “<a href="http://documentation.netgear.com/reference/sve/wireless/WirelessNetworkingBasics-3-08.html">Open</a>”. At first glance, without knowing anything about the nuances of the technology one might think that “Shared” sounds better than “Open”. Open suggests that it’s not especially secure and anyone can get in. “Shared” sounds safer - like you tell everyone what your key is ahead of time. Naturally I assumed that Shared was more secure. </p>

<p>How wrong I was! Read on and I'll tell you why...<br />
</p>]]>
        <![CDATA[<p><br />
It turns out that <a href="http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy">WEP</a>-Shared has a weakness in its authentication challenge. The way I understand it to work is something like this:</p>

<ul>
<li>your laptop associates with the Access Point
<li>the Access Point sends your laptop some 'challenge text' in clear-text
<li>the laptop encrypts the challenge-text using the <a href="http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy">WEP</a> key and sends it back
<li>if the Access-Point sees the data is encrypted with the same key they handshake succeeds and things move along...
</ul>

<p>What's so bad about this? Well because the ‘challenge-text’ is passed in the clear, <strong>and </strong>the encrypted response to the challenge is also passed in the clear, if a hacker could see this request happen, they could use it to perform an offline <a href="http://en.wikipedia.org/wiki/Dictionary_attack">dictionary attack</a> on the data to find your key. </p>

<p>This is a big leg-up on hacking your network. </p>

<p>The open authentication option doesn’t have this challenge request so it’s a little harder to crack, (but still <a href="http://www.tomsnetworking.com/2005/03/31/the_feds_can_own_your_wlan_too/">very crackable</a>).<br />
</p>]]>
    </content>
</entry>
<entry>
    <title>Cancel your GoToMyPC subscription!</title>
    <link rel="alternate" type="text/html" href="http://www.networkgarage.com/brett/2006/04/cancel_your_gotomypcsubscripti.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.networkgarage.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=231" title="Cancel your GoToMyPC subscription!" />
    <id>tag:www.networkgarage.com,2006:/brett//4.231</id>
    
    <published>2006-04-05T10:00:04Z</published>
    <updated>2006-04-05T19:06:56Z</updated>
    
    <summary>I&apos;m always amazed that people actually pay twenty bucks a month for GoToMyPC or even $200 for PC Anywhere. If you have Windows XP Professional at home then you already have this feature! It&apos;s called &quot;Remote Desktop&quot;. Read on, and...</summary>
    <author>
        <name>Brett Marl</name>
        
    </author>
            <category term="Brett" />
    
    <content type="html" xml:lang="en" xml:base="http://www.networkgarage.com/brett/">
        <![CDATA[<p>I'm always amazed that people actually pay <a href="http://www.gotomypc.com/pricing.tmpl">twenty bucks</a> a month for <a href="http://www.gotomypc.com/">GoToMyPC</a> or even <a href="http://www.symantec.com/home_homeoffice/products/remote_pc_fax/pca12/index.html">$200 for PC Anywhere.</a></p>

<p>If you have Windows XP Professional at home then you already have this feature! It's called "Remote Desktop".</p>

<p>Read on, and I'll give you step-by-step instructions on how to enable it for your home network.<br />
</p>]]>
        <![CDATA[<h1 class=entry-header>How to enable Remote Desktop</h1>
To enable Remote Desktop on a PC in your home network, simply do this:

<p>1. Go to Control Panel | System and select the "Remote" tab<br />
2. Make sure the Remote Desktop check box is selected<br />
<div align=center><img alt="remotetab.jpg" src="http://www.networkgarage.com/brett/images/remotetab.jpg" width="439" height="506" /></div><br />
3. If you are an admin on the machine then you already have access. Just make sure you have a nice <a href="http://en.wikipedia.org/wiki/Strong_password">strong password</a> that no hacker can guess.<br />
4. Go to you router and open Port 3389 (TCP) and map it to the local IP-Address of the machine you want to access. <br />
<p style="font-size: 8pt"><i>Note: you may need to use either a static IP-Address or ensure your router always gives your home PC the same internal IP-Address by using a reserved range in your DHCP settings. Otherwise it can sometimes change when you reboot.</i></p></p>

<div align=center><img alt="portmap.jpg" src="http://www.networkgarage.com/brett/images/portmap.jpg" width="600" height="320" /></div>

<p>You should be all set. Your configuration is complete.</p>

<h1 class=entry-header>How to connect from work</h1>
To connect to your home computer from work (or a friends house) go to <b>Programs | Accessories | Communications</b> and choose "Remote Desktop".

<div align=center><img alt="rdpmenu.jpg" src="http://www.networkgarage.com/brett/images/rdpmenu.jpg" width="423" height="204" /></div>

<p>Now you just need to know your WAN IP-Address to get access... but have no fear - if you have configured the Network Magic Net2Go feature, then we will automatically keep a mapping for you. </p>

<p>You can simply use <b><i>[yourhostname].home.net2go.com</i></b> to always find your home network. <br />
eg. "jonesfamily.home.net2go.com". </p>

<div align=center><img alt="rdp.jpg" src="http://www.networkgarage.com/brett/images/rdp.jpg" width="431" height="203" /></div>

<p>Click <b>Connect</b> and you're looking at your home desktop!</p>

<h1 class=entry-header>Advanced Features</h1>
Now... if you want to get <b>really fancy</b> you can go to the "Local Resources" tab and choose to map your printers and disk drives. With this checked - when you are in remote desktop, you can print to your home printer and drag & drop files between home and work in Windows Explorer. How cool is that?

<div align=center><img alt="rdp-advanced.jpg" src="http://www.networkgarage.com/brett/images/rdp-advanced.jpg" width="431" height="491" /></div>

<h1 class=entry-header>Pay it forward</h1>
So what are you going to do with that extra $20 a month? Easy - buy 5 Network Magic subscriptions instead and give them to your favorite friends and pass on this little secret. You'll be their hero.
]]>
    </content>
</entry>
<entry>
    <title>I love My Job(s)</title>
    <link rel="alternate" type="text/html" href="http://www.networkgarage.com/brett/2006/04/i_love_my_jobs.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.networkgarage.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=221" title="I love My Job(s)" />
    <id>tag:www.networkgarage.com,2006:/brett//4.221</id>
    
    <published>2006-04-04T04:26:36Z</published>
    <updated>2006-04-09T23:20:38Z</updated>
    
    <summary>I love my jobs(s). All three of them. My first job is as CTO of Network Magic where I help set the vision and technical direction. My second job is the backend-systems guy/accountant/handyman for my wifes Art Schools in Seattle....</summary>
    <author>
        <name>Brett Marl</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.networkgarage.com/brett/">
        <![CDATA[<p>I love my jobs(s). All three of them. My first job is as <b>CTO</b> of <a href="http://www.networkmagic.com">Network Magic</a> where I help set the vision and technical direction. My second job is the <b>backend-systems guy/accountant/handyman</b> for my wifes <a href="http://www.drawingschool.com">Art School</a>s in Seattle. And my third, but no less important job, is as <b><a href="http://www.networkgarage.com/brett/2006/04/the_technical_head_of_househol.html">Technical Head of Household</a></b> for my home and many of my friends and relatives.</p>

<p>One essential enabler for each of my jobs that I always take for granted is the ability to use networks.  It’s a powerful thing that has affected my life in many ways, yet it does so with ease and somewhat transparently.</p>

<p>Let me walk you a few hours of my life this weekend, and touch on how much I rely on “networks” to perform my jobs and stay in touch. <br />
</p>]]>
        <![CDATA[<p>This weekend was the final weekend before the launch of <a href="http://www.networkmagic.com">Network Magic 3.0</a>. It’s been a huge push and the team has been working hard on some of the features since Christmas. We had a number of bugs spring up last minute, and so a fair amount of the team is cranking away in Seattle as I type. </p>

<p>Not me. For better or worse, I had a trip planned to <a href="http://maps.google.com/maps?f=q&hl=en&sll=37.0625,-95.677068&sspn=81.694375,96.328125&q=orcas+island&ll=48.646067,-122.77977&spn=0.654197,1.141205">Orcas Island</a> in the San Juan Islands of Washington. My wife (Theresa) and I own some land up there and it’s infested with <a href="http://dnr.metrokc.gov/Weeds/gorse.htm">Gorse</a> – a noxious weed that we have to keep under control by law. So while the team works hard on squeezing out the last of the bugs, Theresa and I have been working hard cutting and chipping and poisoning big bushes of this weed we inherited.</p>

<div align=center><img align=center src="http://www.networkgarage.com/brett/images/orcas.jpg" style="margin: 5px"></div>

<p>We’re done weeding now and it’s early evening on Sunday. I’ve been sitting on the couch of <a href="http://trunky.blogspot.com/">Nigels</a> cottage on Orcas for several hours – with surprising productivity. The cottage has a pretty cool Wireless setup. It has an 802.11 network, which is hooked to a <a href="http://www.trangobroadband.com/products/m900s.shtml?id=bb">900Mhz wireless WAN network</a> to a <a href="http://www.orcasonline.com">small ISP</a> on the island. The link is speedy enough that my location is somewhat irrelevant. </p>

<p>The team is working hard and just released the latest ‘Release-Candidate’ to the <a href="http://www.networkgarage.com/brett/2006/04/what_is_dogfood.html">Dogfood</a> alias. We are hoping that these are the final bits that we will release to our customers on Monday and they need some final testing to make sure everything works ok. To do my part, I needed to put on my <a href="http://www.networkgarage.com/brett/2006/04/the_technical_head_of_househol.html">THH</a> hat and install it on every PC in my home. Only I am on Orcas… no problem…</p>

<p>My first mission was to get the Network Magic 3.0 Installer from our private corporate network into my home network. So I used <a href="http://en.wikipedia.org/wiki/Virtual_private_network">VPN</a> to tunnel into our corporate network. <img src="http://www.networkgarage.com/brett/images/brett/laptop.jpg" style="margin: 2px" align=right> To transfer the file to home, I used a share that I had previously shared out using <a href="http://www.foldershare.com">FolderShare</a> that I have setup between my work machine and my home machines. I dropped the new build into my shared folder on my work pc, took another sip of tea, and watched some ducks flying over the orchard and land with a splash in the pond. Before I look back at the keyboard, the bits are already in my home waiting.</p>

<p>My second mission was to get onto my home PC and install Network Magic. For this I used <a href="http://www.microsoft.com/windowsxp/using/mobility/getstarted/remoteintro.mspx">Remote Desktop</a> to connect directly to my desktop. In seconds, I’m in and using the PC as if I were there. Once Network Magic was installed there, I opened another Remote Desktop connection and connected to the Server in my basement. 5 minutes later and Network Magic is up and running on all PCs in my home.</p>

<p>My sister in law, Becky called on my mobile phone, which gets surprisingly good coverage at this remote location. While I was talking with her I found a potential show-stopper bug in Network Magic. For some reason our new wireless connection manager was not able to connect to this wireless network in WEP-Shared mode. I sent a quick IM to Matthew - our development manager back at the office. He wasn’t aware of the bug, and so I grabbed the logs from the log-directory and sent them over to Matthew via email. </p>

<p>I hung up my conversation with Becky and noticed that I had a new voicemail at home. <img src="http://www.networkgarage.com/brett/images/brett/voip.jpg" align=left style=margin:2px"> I have a Voice-Over-IP phone with <a href="http://ww.vonage.com">Vonage</a> and it delivers voicemails as a .wav file direct to my email inbox. I listened to the message and it was my mum – calling from England. I looked at the clock – it was way past midnight UK time – too late to call.</p>

<p>The Release-Candidate build of Network Magic was looking good. Time to turn my attention to my second job…</p>

<p>Theresa has two art schools in Seattle, in the same way I do at home, we have dynamic DNS (via the Network Magic Net2Go Service) setup at each location and I can securely tunnel into the machines there too. It’s the end of march and we need to file quarterly payroll taxes. I “remoted” into the <a href="http://www.drawingschool.com">Art School</a> computer, opened up QuickBooks and spent a quick hour reconciling the accounts. While I was doing this Theresa mentioned a bug on the <a href="http://www.drawingschool.com">Art School</a> web site. I flipped Remote Desktop sessions – back to my office PC again, debugged the problem and propped a new version of the code to the website. All in the bat of an eye. And then carried on with the accounting work.</p>

<p>I checked email and got mail from Libby and <a href="http://www.networkgarage.com/tim/">Tim</a>. Our site goes live tomorrow and we’re going to put a blog up there. I want to contribute some articles... I scratched my head for inspiration and then reflected on the last few hours on the couch. Wow. Amazing how much technology I used and how many PCs I interacted with. 802.11 networks, 900Mhz networks, cable modem, DSL modems, <img src="http://www.networkgarage.com/brett/images/brett/home.jpg" align=right> corporate networks and even cellular networks. Now, you could argue that I’m some kind of alien freak of nature and nobody else would ever be so extreme. But it really struck me how much remote-desktop, remote-email, remote-access to voice-mail and cellular networks have liberated my need to be chained to a single office PC. I think there are more people like me that would love to be so unchained, but don’t know all the technical mumbo jumbo to make it happen. That’s what we’re planning to solve here with Network Magic. Easy Networking for normal people – not alien freaks like me.</p>

<p>Then my final epiphany came…. All this time I’ve been sitting here on the couch, warmed by the glow of my laptop screen, Theresa has been laying in the last few rays of the sun, feeling the grass between her toes. Perhaps all this technology really isn’t as liberating as I think it is…<br />
</p>]]>
    </content>
</entry>
<entry>
    <title>What is Dogfood?</title>
    <link rel="alternate" type="text/html" href="http://www.networkgarage.com/brett/2006/04/what_is_dogfood.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.networkgarage.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=222" title="What is Dogfood?" />
    <id>tag:www.networkgarage.com,2006:/brett//4.222</id>
    
    <published>2006-04-04T02:34:05Z</published>
    <updated>2006-04-04T03:00:56Z</updated>
    
    <summary>At Network Magic we use the term &apos;dogfooding&apos; to refer to the act of running our own software in early pre-release form on our home computers. It&apos;s a term that we inherited from a previous life at Microsoft. Generally speaking,...</summary>
    <author>
        <name>Brett Marl</name>
        
    </author>
            <category term="Brett" />
    
    <content type="html" xml:lang="en" xml:base="http://www.networkgarage.com/brett/">
        <![CDATA[<p>At Network Magic we use the term 'dogfooding' to refer to the act of running our own software in early pre-release form on our home computers. It's a term that we inherited from a previous life at Microsoft.</p>

<p>Generally speaking, a "dogfood build" has been lightly tested and is hot off the press of the nightly build machine. They contain many bugs, but usually the latest and greatest features. </p>

<p>They're somewhat edible, but not fit for broad human consumption :)</p>

<p>It's a requirement of working at Network Magic to eat your own dogfood!</p>]]>
        
    </content>
</entry>

</feed> 


