<?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: How To Fix Windows Live Messenger Login Error Code 80048820?</title>
	<atom:link href="http://www.walkernews.net/2009/04/08/how-to-fix-windows-live-messenger-login-error-code-80048820/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.walkernews.net/2009/04/08/how-to-fix-windows-live-messenger-login-error-code-80048820/</link>
	<description>A capsule of walker's experience in life...</description>
	<lastBuildDate>Mon, 06 Feb 2012 19:09:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Andrew</title>
		<link>http://www.walkernews.net/2009/04/08/how-to-fix-windows-live-messenger-login-error-code-80048820/#comment-9519</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 16 Apr 2010 19:07:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.walkernews.net/?p=2346#comment-9519</guid>
		<description>One of the people in my office was having a similar issue.  Though she could connect to the corporate network she could not use IE or Messenger.  Firefox worked fine, however, and we were able to ping internal and external resources.  After a minute of digging around, we selected Internet Options from the IE tool menu, selected the Connections Tab, Clicked on the LAN Settings button and enabled the &quot;Automatically Detect Network Settings&quot; option.  Her issues with IE and Messenger were instantly fixed.

I have no idea why this happened, but I hope this solution helps someone else!</description>
		<content:encoded><![CDATA[<p>One of the people in my office was having a similar issue.  Though she could connect to the corporate network she could not use IE or Messenger.  Firefox worked fine, however, and we were able to ping internal and external resources.  After a minute of digging around, we selected Internet Options from the IE tool menu, selected the Connections Tab, Clicked on the LAN Settings button and enabled the &#8220;Automatically Detect Network Settings&#8221; option.  Her issues with IE and Messenger were instantly fixed.</p>
<p>I have no idea why this happened, but I hope this solution helps someone else!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Duffin</title>
		<link>http://www.walkernews.net/2009/04/08/how-to-fix-windows-live-messenger-login-error-code-80048820/#comment-7267</link>
		<dc:creator>Michael Duffin</dc:creator>
		<pubDate>Sun, 03 May 2009 14:28:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.walkernews.net/?p=2346#comment-7267</guid>
		<description>We found a solution to the problem of gettin an error  trying to log in to windows live messenger that list wlcomm.exe and rpawinet.dll. Just rename rpawinet.dll and you can login fine. rpawinet.dll is a NetIdentity HTTP Filter from Novell, Inc.  *WARNING* Do not rename this file if you are using the Novell ZENworks
Desktop Management Agent to login to a ZENworks Middle Tier Server or
are using the Myapps.html web site to launch ZENworks applications
(i.e., if you are in an &quot;Agent Only&quot; with no Novell Client
environment). Renaming the file will result in the inability to
authenticate to the Middle Tier or launch applications from the
MyApps.html web page.&quot;</description>
		<content:encoded><![CDATA[<p>We found a solution to the problem of gettin an error  trying to log in to windows live messenger that list wlcomm.exe and rpawinet.dll. Just rename rpawinet.dll and you can login fine. rpawinet.dll is a NetIdentity HTTP Filter from Novell, Inc.  *WARNING* Do not rename this file if you are using the Novell ZENworks<br />
Desktop Management Agent to login to a ZENworks Middle Tier Server or<br />
are using the Myapps.html web site to launch ZENworks applications<br />
(i.e., if you are in an &#8220;Agent Only&#8221; with no Novell Client<br />
environment). Renaming the file will result in the inability to<br />
authenticate to the Middle Tier or launch applications from the<br />
MyApps.html web page.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guide To Fix Windows Live Messenger Login Error 80048820</title>
		<link>http://www.walkernews.net/2009/04/08/how-to-fix-windows-live-messenger-login-error-code-80048820/#comment-7101</link>
		<dc:creator>Guide To Fix Windows Live Messenger Login Error 80048820</dc:creator>
		<pubDate>Wed, 08 Apr 2009 16:18:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.walkernews.net/?p=2346#comment-7101</guid>
		<description>[...] thousand words is simply the best!  So, here I write this step-by-step guide that might solve your Windows Live Messenger login problem, particularly the one related to error code 80048820 or extended error code 80048416.    [...]</description>
		<content:encoded><![CDATA[<p>[...] thousand words is simply the best!  So, here I write this step-by-step guide that might solve your Windows Live Messenger login problem, particularly the one related to error code 80048820 or extended error code 80048416.    [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

