<?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: Things To Do When Your Motherboard OnBoard Lan Dies</title> <atom:link href="http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/feed/" rel="self" type="application/rss+xml" /><link>http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/</link> <description>A technology news blog covering software, mobile phones, gadgets, security, the Internet and other relevant areas.</description> <lastBuildDate>Sun, 12 Feb 2012 04:50:20 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: axl456</title><link>http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/comment-page-1/#comment-733831</link> <dc:creator>axl456</dc:creator> <pubDate>Sun, 19 Apr 2009 01:10:07 +0000</pubDate> <guid
isPermaLink="false">http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/#comment-733831</guid> <description>you should be preparing yourself for future mainboard components trouble :&#124;</description> <content:encoded><![CDATA[<p>you should be preparing yourself for future mainboard components trouble :|</p> ]]></content:encoded> </item> <item><title>By: Martin</title><link>http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/comment-page-1/#comment-732764</link> <dc:creator>Martin</dc:creator> <pubDate>Sat, 18 Apr 2009 16:31:10 +0000</pubDate> <guid
isPermaLink="false">http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/#comment-732764</guid> <description>I read up on it on some sites and it seems that it is quite common that the onboard LAN dies on this motherboard.</description> <content:encoded><![CDATA[<p>I read up on it on some sites and it seems that it is quite common that the onboard LAN dies on this motherboard.</p> ]]></content:encoded> </item> <item><title>By: toe</title><link>http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/comment-page-1/#comment-732755</link> <dc:creator>toe</dc:creator> <pubDate>Sat, 18 Apr 2009 16:23:06 +0000</pubDate> <guid
isPermaLink="false">http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/#comment-732755</guid> <description>OS - vista64bit
situation - all 32bit application no access to net connection, only 64bit application works.
problem - 64bit machines having tcp/ip stack corruption
solution
1. Click on Start button.
2. Type Cmd in the Start Search text box.
3. Type netsh winsock reset in the Command Prompt shell
4. Restart the computer.</description> <content:encoded><![CDATA[<p>OS &#8211; vista64bit</p><p>situation &#8211; all 32bit application no access to net connection, only 64bit application works.</p><p>problem &#8211; 64bit machines having tcp/ip stack corruption</p><p>solution<br
/> 1. Click on Start button.<br
/> 2. Type Cmd in the Start Search text box.<br
/> 3. Type netsh winsock reset in the Command Prompt shell<br
/> 4. Restart the computer.</p> ]]></content:encoded> </item> <item><title>By: Rarst</title><link>http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/comment-page-1/#comment-732749</link> <dc:creator>Rarst</dc:creator> <pubDate>Sat, 18 Apr 2009 16:17:01 +0000</pubDate> <guid
isPermaLink="false">http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/#comment-732749</guid> <description>From my experience a lot of problems of this type are from short circuits on backpanel where all ports are. Which most of the time is quite bad sign. At best it is solved by ignoring problematic port but often it gets worse and worse until motherboard fries.
Switching to external card is fine but being ready for further trouble is also good. :)</description> <content:encoded><![CDATA[<p>From my experience a lot of problems of this type are from short circuits on backpanel where all ports are. Which most of the time is quite bad sign. At best it is solved by ignoring problematic port but often it gets worse and worse until motherboard fries.</p><p>Switching to external card is fine but being ready for further trouble is also good. :)</p> ]]></content:encoded> </item> <item><title>By: joe</title><link>http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/comment-page-1/#comment-732725</link> <dc:creator>joe</dc:creator> <pubDate>Sat, 18 Apr 2009 15:49:35 +0000</pubDate> <guid
isPermaLink="false">http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/#comment-732725</guid> <description>less common these days but a few years ago any good DSL ISP plan would include a free dial-up account. a few times when my DSL went down i reverted to modem (also on motherboard) to get online until DSL was fixed</description> <content:encoded><![CDATA[<p>less common these days but a few years ago any good DSL ISP plan would include a free dial-up account. a few times when my DSL went down i reverted to modem (also on motherboard) to get online until DSL was fixed</p> ]]></content:encoded> </item> </channel> </rss>
