<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The heartbreak of technology</title>
	<atom:link href="http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/</link>
	<description>Web design news and insights since 1995</description>
	<lastBuildDate>Sat, 20 Mar 2010 00:13:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Greg Bulmash</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-18665</link>
		<dc:creator>Greg Bulmash</dc:creator>
		<pubDate>Tue, 14 Aug 2007 16:45:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-18665</guid>
		<description>Just for posterity&#039;s sake, gotta agree with Danny.  If you&#039;re hooked into the router properly and your computer&#039;s networking settings are configured properly, you should have NO problem reaching the internal control panel screen for the router.  Connecting to the router&#039;s internal control panel by HTTP to 198.162.etc. has absolutely nothing to do with whether your broadband access is working.  That connectivity is on an independent network, created by the router, to which it will eventually deliver the broadband access.

Aside from the various &quot;check this&quot; and &quot;check that&quot; suggestions, I&#039;d also suggest checking your firewall settings.  If you&#039;re behind NAT provided by the router, it&#039;s safe to try turning off your machine&#039;s software-based firewall briefly to see if that solves things.  If it does, then you know that you need to configure your firewall properly.

In about 60% of the connectivity issues I&#039;ve encountered, a misconfigured firewall was the point of failure.</description>
		<content:encoded><![CDATA[<p>Just for posterity&#8217;s sake, gotta agree with Danny.  If you&#8217;re hooked into the router properly and your computer&#8217;s networking settings are configured properly, you should have NO problem reaching the internal control panel screen for the router.  Connecting to the router&#8217;s internal control panel by HTTP to 198.162.etc. has absolutely nothing to do with whether your broadband access is working.  That connectivity is on an independent network, created by the router, to which it will eventually deliver the broadband access.</p>
<p>Aside from the various &#8220;check this&#8221; and &#8220;check that&#8221; suggestions, I&#8217;d also suggest checking your firewall settings.  If you&#8217;re behind NAT provided by the router, it&#8217;s safe to try turning off your machine&#8217;s software-based firewall briefly to see if that solves things.  If it does, then you know that you need to configure your firewall properly.</p>
<p>In about 60% of the connectivity issues I&#8217;ve encountered, a misconfigured firewall was the point of failure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Hartman</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-17266</link>
		<dc:creator>Tom Hartman</dc:creator>
		<pubDate>Sun, 15 Jul 2007 03:37:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-17266</guid>
		<description>Any Airport Extreme Experts out there?

I bought a base station tonight. Have a house filled with Macs.

Have Bellsouth DSL.

Connected DSL to Airport Extreme Basestation.

Configured all computers in the house.

Using the Airport Utility, configured the network.

Everything in the house is working fine.

Except...

The AMBER light, which indicates no network connection, still blinks on the Airport box. I&#039;ve restarted the modem, Airport, etc. Still blinks. But everything in the house is working fine. 

If I open the Airport Utility, it says &#039;You have a base station that needs attention.&quot; So I reconfigure it again, the software says &quot;Congrats, you are up and running!&quot; and all the Macs throughout the house work fine.

And the AMBER LIGHT is still blinking.

Ideas?

Thanks
Tom</description>
		<content:encoded><![CDATA[<p>Any Airport Extreme Experts out there?</p>
<p>I bought a base station tonight. Have a house filled with Macs.</p>
<p>Have Bellsouth DSL.</p>
<p>Connected DSL to Airport Extreme Basestation.</p>
<p>Configured all computers in the house.</p>
<p>Using the Airport Utility, configured the network.</p>
<p>Everything in the house is working fine.</p>
<p>Except&#8230;</p>
<p>The AMBER light, which indicates no network connection, still blinks on the Airport box. I&#8217;ve restarted the modem, Airport, etc. Still blinks. But everything in the house is working fine. </p>
<p>If I open the Airport Utility, it says &#8216;You have a base station that needs attention.&#8221; So I reconfigure it again, the software says &#8220;Congrats, you are up and running!&#8221; and all the Macs throughout the house work fine.</p>
<p>And the AMBER LIGHT is still blinking.</p>
<p>Ideas?</p>
<p>Thanks<br />
Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Zeldman</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-14912</link>
		<dc:creator>Jeffrey Zeldman</dc:creator>
		<pubDate>Mon, 11 Jun 2007 11:33:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-14912</guid>
		<description>I got the problem resolved a while back. Thanks, everyone.</description>
		<content:encoded><![CDATA[<p>I got the problem resolved a while back. Thanks, everyone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmin</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-14802</link>
		<dc:creator>Dmin</dc:creator>
		<pubDate>Sun, 10 Jun 2007 02:15:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-14802</guid>
		<description>Hi! I work as a trainer for a call center that supports DSL connections. I understand what you may be going thru. I will go with the suggestion that someone made earlier.  Ask for a supervisor and insist for one. If you don&#039;t thru to one, hangup and callback. You may need to call the helpdesk around 3 times at the most, not more than that. You will get a supervisor to help you out. 

As far as your configuraition is concerned. The way we go about doing this is. First hold the reset switch on the modem for 3 secs. this clears your username and password from the modem. Also do it on the router, so you know that does not have your username and passoword stored in it.

Now, before you go wireless wih your router, &lt;b&gt;it is important that you are able to get online using an ethernet connection.&lt;/b&gt; this will let you isolate your problem. i.e. --&gt; Connect your modem to your router with ethernet &amp; connect your router to your computer with ethernet. If you are able to setup your internet connection with ethernet. You will know this is purely a wireless configuration issue.
A few tips on working around with wireless is :
1.Make sure distance is not an issue.
2.Disable all security and check if it works(disable WEP on the router)
3.Make sure your IP is set to DHCP(optained from the router rather than forced into the computer)

More info on setting up linksys with Verizon:
http://www.dslreports.com/faq/1372

If you need support with this, mail me your number. I&#039;d be glad to help you with this.</description>
		<content:encoded><![CDATA[<p>Hi! I work as a trainer for a call center that supports DSL connections. I understand what you may be going thru. I will go with the suggestion that someone made earlier.  Ask for a supervisor and insist for one. If you don&#8217;t thru to one, hangup and callback. You may need to call the helpdesk around 3 times at the most, not more than that. You will get a supervisor to help you out. </p>
<p>As far as your configuraition is concerned. The way we go about doing this is. First hold the reset switch on the modem for 3 secs. this clears your username and password from the modem. Also do it on the router, so you know that does not have your username and passoword stored in it.</p>
<p>Now, before you go wireless wih your router, <strong>it is important that you are able to get online using an ethernet connection.</strong> this will let you isolate your problem. i.e. &#8211;&gt; Connect your modem to your router with ethernet &amp; connect your router to your computer with ethernet. If you are able to setup your internet connection with ethernet. You will know this is purely a wireless configuration issue.<br />
A few tips on working around with wireless is :<br />
1.Make sure distance is not an issue.<br />
2.Disable all security and check if it works(disable WEP on the router)<br />
3.Make sure your IP is set to DHCP(optained from the router rather than forced into the computer)</p>
<p>More info on setting up linksys with Verizon:<br />
<a href="http://www.dslreports.com/faq/1372" rel="nofollow">http://www.dslreports.com/faq/1372</a></p>
<p>If you need support with this, mail me your number. I&#8217;d be glad to help you with this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cd</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-13148</link>
		<dc:creator>cd</dc:creator>
		<pubDate>Sun, 20 May 2007 00:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-13148</guid>
		<description>Try accessing just the wireless router without it being hooked to the WAN side. So, LAN on router to Enet port on Mac. See if you can get in that way. If not, the problem is not your network. Try a different cable if this is a problem. Also, try a different browser. And make a new location in Network that only uses the Ethernet port. A little narrowing down will go a long way with tier 2 (see below how to get there faster).

Also, every time you connect a different device to the modem, disconnect the power to the modem for about a minute. This will reset its MAC address memory. Otherwise, as you found, it will have to time out.

Ex-Applecare veteran here. The way to get to tier 2 quickly is to refuse to agree with the tier 1 agent in any way. They have a limited time to &quot;gain agreement&quot; with the customer, and if they can&#039;t they have to get T2 on the line. Politely but firmly disagree with everything, refuse to co-operate by doing stupid stuff, and call back if you get a T1 agent too obtuse to get it. The skill levels on T1 vary wildly, from die-hards to people who are looking up your issue in a stack of Macs for Idiots books.

Also, steve@apple.com can work wonders.</description>
		<content:encoded><![CDATA[<p>Try accessing just the wireless router without it being hooked to the WAN side. So, LAN on router to Enet port on Mac. See if you can get in that way. If not, the problem is not your network. Try a different cable if this is a problem. Also, try a different browser. And make a new location in Network that only uses the Ethernet port. A little narrowing down will go a long way with tier 2 (see below how to get there faster).</p>
<p>Also, every time you connect a different device to the modem, disconnect the power to the modem for about a minute. This will reset its MAC address memory. Otherwise, as you found, it will have to time out.</p>
<p>Ex-Applecare veteran here. The way to get to tier 2 quickly is to refuse to agree with the tier 1 agent in any way. They have a limited time to &#8220;gain agreement&#8221; with the customer, and if they can&#8217;t they have to get T2 on the line. Politely but firmly disagree with everything, refuse to co-operate by doing stupid stuff, and call back if you get a T1 agent too obtuse to get it. The skill levels on T1 vary wildly, from die-hards to people who are looking up your issue in a stack of Macs for Idiots books.</p>
<p>Also, <a href="mailto:steve@apple.com">steve@apple.com</a> can work wonders.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-13132</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Sat, 19 May 2007 22:46:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-13132</guid>
		<description>Dear Mr. Zeldman,
I feel your pain. Up until a series of frustrating problems with a new MacBook Pro, I wrongly assumed that when I needed customer care there would be a competent and professional customer support team ready to help.  My than six month old MacBook Pro ended up being out of service for a total of 32 days and was practically rebuilt three times before finally returning to me in working order. After this experience the next time I have to make a major purchase I think I will take a look at what other manufacturers have to offer. Apple customer support just does NOT deliver the professional and quality support that they tout.  I wish you best of luck and hope that some clever reader out there can help transform your paperweight into the functional piece of equipment that “just works” like it’s supposed to.</description>
		<content:encoded><![CDATA[<p>Dear Mr. Zeldman,<br />
I feel your pain. Up until a series of frustrating problems with a new MacBook Pro, I wrongly assumed that when I needed customer care there would be a competent and professional customer support team ready to help.  My than six month old MacBook Pro ended up being out of service for a total of 32 days and was practically rebuilt three times before finally returning to me in working order. After this experience the next time I have to make a major purchase I think I will take a look at what other manufacturers have to offer. Apple customer support just does NOT deliver the professional and quality support that they tout.  I wish you best of luck and hope that some clever reader out there can help transform your paperweight into the functional piece of equipment that “just works” like it’s supposed to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Smith</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-12113</link>
		<dc:creator>Daniel Smith</dc:creator>
		<pubDate>Wed, 09 May 2007 01:44:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-12113</guid>
		<description>Uh, maybe it&#039;s time to hire an IT staff?
Actually, I assumed all these years that you and a lot of the other early famous web people were on T1 or similar lines early on, and thus the ability to surf/congeal so much info so quickly. Guess I was wrong.
Suggestion only.</description>
		<content:encoded><![CDATA[<p>Uh, maybe it&#8217;s time to hire an IT staff?<br />
Actually, I assumed all these years that you and a lot of the other early famous web people were on T1 or similar lines early on, and thus the ability to surf/congeal so much info so quickly. Guess I was wrong.<br />
Suggestion only.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-12075</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Tue, 08 May 2007 04:20:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-12075</guid>
		<description>Jeff,

As a lot of people have said your initial problem appears to be your internal network setup, this is what allows your mac to connect to the Linksys via it&#039;s default IP which should be 198.162.0.1 or similar.  If you have tried what Josh suggested and plugged into the router directly and still had no joy then you need to reconfigure you IP config on your mac, check to make sure you are configured to just get an IP address via DHCP and do not have a hard coded IP in there.  Once you have this all working and you can get to the Linksys web interface then you can configure the Wireless Access point SSID and security and also the net connection/WAN/External network config and then plug in the modem and try from there.

Let me know via email if you need any further info or help or MSN instant chat.</description>
		<content:encoded><![CDATA[<p>Jeff,</p>
<p>As a lot of people have said your initial problem appears to be your internal network setup, this is what allows your mac to connect to the Linksys via it&#8217;s default IP which should be 198.162.0.1 or similar.  If you have tried what Josh suggested and plugged into the router directly and still had no joy then you need to reconfigure you IP config on your mac, check to make sure you are configured to just get an IP address via DHCP and do not have a hard coded IP in there.  Once you have this all working and you can get to the Linksys web interface then you can configure the Wireless Access point SSID and security and also the net connection/WAN/External network config and then plug in the modem and try from there.</p>
<p>Let me know via email if you need any further info or help or MSN instant chat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Zeldman</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-12049</link>
		<dc:creator>Jeffrey Zeldman</dc:creator>
		<pubDate>Mon, 07 May 2007 10:48:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-12049</guid>
		<description>Thanks, Travis, Josh, and everybody. Just a few quick notes:

&lt;ol&gt;&lt;li&gt;Verizon is not maintaining a hold on my equipment. &lt;/li&gt;
&lt;li&gt;Verizon is not my ISP. &lt;/li&gt;
&lt;li&gt;Verizon is merely the phone company. They supply the copper and switches.&lt;/li&gt;
&lt;li&gt;My ISP is Speakeasy.&lt;/li&gt;
&lt;li&gt;Speakeasy does not maintain a DHCP hold on any connected equipment.&lt;/li&gt;&lt;/ol&gt;

A lousy phone company policy is not the source of the problem. The source of the problem remains unknown. I&#039;ll post an update when the problem is resolved, if I learn anything of value.</description>
		<content:encoded><![CDATA[<p>Thanks, Travis, Josh, and everybody. Just a few quick notes:</p>
<ol>
<li>Verizon is not maintaining a hold on my equipment. </li>
<li>Verizon is not my ISP. </li>
<li>Verizon is merely the phone company. They supply the copper and switches.</li>
<li>My ISP is Speakeasy.</li>
<li>Speakeasy does not maintain a DHCP hold on any connected equipment.</li>
</ol>
<p>A lousy phone company policy is not the source of the problem. The source of the problem remains unknown. I&#8217;ll post an update when the problem is resolved, if I learn anything of value.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-11900</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Fri, 04 May 2007 18:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-11900</guid>
		<description>I had an identical problem with Verizon when we switched routers (from Linksys to having the XServer route everything. After a while on the phone with Verizon, it was explained that Verizon&#039;s systems maintain a IP lease to the previous router or computer and it stays there until it gets released and not renewed. If you attempt to simply reboot, that won&#039;t work, and trying to release via the previous router won&#039;t work either, because it releases and renews too fast before you disconnect it. In our case, the only thing we could do was attach a Windows machine directly to the modem, and then via the Command Line, release the DHCP, which had the unique effect of releasing the IP and then allowing a new device to get the IP. There are so many variables between different setups, but this sounds like it could apply.

Good luck.</description>
		<content:encoded><![CDATA[<p>I had an identical problem with Verizon when we switched routers (from Linksys to having the XServer route everything. After a while on the phone with Verizon, it was explained that Verizon&#8217;s systems maintain a IP lease to the previous router or computer and it stays there until it gets released and not renewed. If you attempt to simply reboot, that won&#8217;t work, and trying to release via the previous router won&#8217;t work either, because it releases and renews too fast before you disconnect it. In our case, the only thing we could do was attach a Windows machine directly to the modem, and then via the Command Line, release the DHCP, which had the unique effect of releasing the IP and then allowing a new device to get the IP. There are so many variables between different setups, but this sounds like it could apply.</p>
<p>Good luck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Wall</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-11894</link>
		<dc:creator>Jeremy Wall</dc:creator>
		<pubDate>Fri, 04 May 2007 16:03:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-11894</guid>
		<description>@Ben Ryan,

You can always try ubuntu. It&#039;s pretty painless these days to set up and when you have problems like this it will let you get some pretty detailed debugging information from the logs. Something difficult to get on Win or Mac OS&#039;s.

And when the DSL/Cable/ISP tech hears what OS your running they automatically forward you to someone who knows what your doing. Their script is useless on my OS :-)</description>
		<content:encoded><![CDATA[<p>@Ben Ryan,</p>
<p>You can always try ubuntu. It&#8217;s pretty painless these days to set up and when you have problems like this it will let you get some pretty detailed debugging information from the logs. Something difficult to get on Win or Mac OS&#8217;s.</p>
<p>And when the DSL/Cable/ISP tech hears what OS your running they automatically forward you to someone who knows what your doing. Their script is useless on my OS :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Travis</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-11863</link>
		<dc:creator>Travis</dc:creator>
		<pubDate>Fri, 04 May 2007 01:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-11863</guid>
		<description>Jeff, 
Send me an email and I can help you fix this problem. I work for the phone company (AT&amp;T not Verizon), but the systems they both use are similar, they used to be the same company as we all know.
I agree with Josh. First you need to setup the router without hooking it up to your modem. Once you know the router is configured properly, then connect your modem. If this fails then you have a problem with the modem.</description>
		<content:encoded><![CDATA[<p>Jeff,<br />
Send me an email and I can help you fix this problem. I work for the phone company (AT&amp;T not Verizon), but the systems they both use are similar, they used to be the same company as we all know.<br />
I agree with Josh. First you need to setup the router without hooking it up to your modem. Once you know the router is configured properly, then connect your modem. If this fails then you have a problem with the modem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Ryan</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-11854</link>
		<dc:creator>Ben Ryan</dc:creator>
		<pubDate>Thu, 03 May 2007 21:29:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-11854</guid>
		<description>I&#039;d answer that last question Jeffrey, but it took so long for me to get a connection I&#039;d forgot the pithy response I&#039;d worked out ;). 

I&#039;ve got a MacBook Pro which has been totally unreliable, prone to crashing and requires a wipe of the PDRAM every time I move to a new location (which given it&#039;s a laptop, is fairly often). I&#039;ve sent it back for repairs 3 times in six months to have the logic board replaced, RAM replaced, and finally, the techs threw up their hands and said it was the third party RAM I&#039;d put in it (I HAVEN&#039;t put anything in it - that was the Apple reseller I bought the machine from).

When I called Apple, their tech support couldn&#039;t help me, they&#039;re customer relations people picked up the phone for long enough to hang up, and then when I called back, their operator told me it was my fault I&#039;d been disconnected.

Their products are shit. Their customer service smells just as bad. Depressingly, I still can&#039;t quite bring myself to go back to windows.

For some reason when I moved to my current apartment, the wireless wouldn&#039;t connect in the way you mentioned. I ran the setup assistant and it got me a connection, but it&#039;s very exclusive. My wireless no longer works ANYWHERE else.</description>
		<content:encoded><![CDATA[<p>I&#8217;d answer that last question Jeffrey, but it took so long for me to get a connection I&#8217;d forgot the pithy response I&#8217;d worked out ;). </p>
<p>I&#8217;ve got a MacBook Pro which has been totally unreliable, prone to crashing and requires a wipe of the PDRAM every time I move to a new location (which given it&#8217;s a laptop, is fairly often). I&#8217;ve sent it back for repairs 3 times in six months to have the logic board replaced, RAM replaced, and finally, the techs threw up their hands and said it was the third party RAM I&#8217;d put in it (I HAVEN&#8217;t put anything in it &#8211; that was the Apple reseller I bought the machine from).</p>
<p>When I called Apple, their tech support couldn&#8217;t help me, they&#8217;re customer relations people picked up the phone for long enough to hang up, and then when I called back, their operator told me it was my fault I&#8217;d been disconnected.</p>
<p>Their products are shit. Their customer service smells just as bad. Depressingly, I still can&#8217;t quite bring myself to go back to windows.</p>
<p>For some reason when I moved to my current apartment, the wireless wouldn&#8217;t connect in the way you mentioned. I ran the setup assistant and it got me a connection, but it&#8217;s very exclusive. My wireless no longer works ANYWHERE else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pablo</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-11780</link>
		<dc:creator>Pablo</dc:creator>
		<pubDate>Thu, 03 May 2007 01:22:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-11780</guid>
		<description>Jeff, your old friend in London... heard you were having a spot of bother over there. Wish I could fly over and help... Good luck!</description>
		<content:encoded><![CDATA[<p>Jeff, your old friend in London&#8230; heard you were having a spot of bother over there. Wish I could fly over and help&#8230; Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Zeldman</title>
		<link>http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-11764</link>
		<dc:creator>Jeffrey Zeldman</dc:creator>
		<pubDate>Wed, 02 May 2007 19:57:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2007/04/26/the-heartbreak-of-technology/#comment-11764</guid>
		<description>How many web professionals does it take to plug in a router?</description>
		<content:encoded><![CDATA[<p>How many web professionals does it take to plug in a router?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
