Shoutbox

Log in error code 80048820 extended error code 80048401 - Printable Version

-Shoutbox (https://shoutbox.menthix.net)
+-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58)
+--- Forum: Skype & Technology (/forumdisplay.php?fid=9)
+---- Forum: Skype & Live Messenger (/forumdisplay.php?fid=10)
+----- Thread: Log in error code 80048820 extended error code 80048401 (/showthread.php?tid=80683)

Log in error code 80048820 extended error code 80048401 by dht240 on 01-04-2008 at 02:45 PM

[font=Verdana][size=1][color=purple]
My PC recently had tojan.mespam and since then I've been unable to log into Windows Live Messenger. the error codes I get are listed above.

Additionally, since the trojan.mespam issue I cannot access any symantec.com or microsoft.com websites - is this linked to the Messenger problem?

Can anyone help me solve the problem?

Many thanks.


RE: Log in error code 80048820 extended error code 80048401 by djdannyp on 01-04-2008 at 03:18 PM

click here for some information that may help you

in particular this part:

quote:
Originally posted by www.imzers.com
Automatic solution

First you will have to download this zip file which includes a batch file that can register the dll files for you. After downloading unzip it and run register-messenger-dll-files.bat, a black screen will pop up and update you on the process. When done your Messenger should work again!


see if that helps you with your Messenger problem


RE: Log in error code 80048820 extended error code 80048401 by fatty on 06-19-2008 at 12:38 PM

The Solutions to MSN Error Code 80048820
Internet Explorer - Try removing Internet Explorer proxy server settings and go with the

'Automatically detect settings'.

1) Launch Internet Explorer, click Tools and then click Internet Options.
From the Internet Options dialog box, go to the Connections tab.
Click LAN Setting. Un check the Use a proxy server for your LAN (These settings will not

apply to dial-up or VPN connections) checkbox. Finally positively tick: 'Automatically

detect settings'.

2) Register softpub.dll.

Click Start (Button), and then click Run, type regsvr32 softpub.dll. Restart MSN Messenger.

See also Error code 81000314

3) If necessary, logon as a local administrator, set the computer's clock to the correct

date and time. (Check on the internet if possible.)

4) Turn off the firewall temporarily. Check firewall settings such as Norton: "Block access

to secure sites". If this cures the problem, make sure that Microsoft's MSN Messenger is

allowed full access through your firewall.

NetGear problem
a) Enter IP address 192.168.0.1 in the IE address bar.
b) Log on with ISP user name and password.
c) Enter Admin, password
d) Navigate to advanced menu, WAN set-up
e) Change MTU size to 1400

5) Try a password of no more than 8 characters.

6) If you are using IE 7.0 check the SSL Settings. Internet options advanced (Tab) scroll

down to the bottom. Security section. Tick 'Use ssl 2.0'.

6) Drastic! Try uninstalling MSN Messenger version 7.5 and install Microsoft MSN version

7.0.

Summary of MSN Error Code 80048820
If you are suffering from MSN Error Code 80048820, check your system clock. If both time and

date are correct, try turning off your firewall.


RE: Log in error code 80048820 extended error code 80048401 by CookieRevised on 06-20-2008 at 03:11 AM

quote:
Originally posted by dht240
Additionally, since the trojan.mespam issue I cannot access any symantec.com or microsoft.com websites - is this linked to the Messenger problem?
absolutely. Messenger needs access to several (Microsoft) domains. The trojan probably blocked several things.

Removing a virus or trojan quite often does not repair what it had done (common misconception).

Before trying to solve any Messenger problem, make sure your computer (internet connection) is back to normal because any problem you'd see in Messenger would be directly related to incorrect settings for your internet connection.

Thus, simply re-registering some DLLs, turning of your firewall or even reinstalling Messenger, and the likes (like posted above), will not fix this.

So you might wanna check your hosts file, proxy settings, blocked sites/domains, etc.

But do all that after the trojan is completely removed. To remove a virus properly you need to turn System Restore OFF and boot up in SAFE MODE. Only then you can properly run a decent anti-virus. Read this post.


Some quick info to get you started:

hosts file info:
http://vlaurie.com/computers2/Articles/hosts.htm
http://www.mvps.org/winhelp2002/hostsfaq.htm

other settings you might wanna check:
MSIE > Tools > Options > Security > Internet > Standard
MSIE > Tools > Options > Security > Trusted sites > Websites > blank
MSIE > Tools > Options > Security > Not-Trusted sites > Websites > blank
MSIE > Tools > Options > Privacy > Normal
MSIE > Tools > Options > Privacy > Websites > needs to be blank
MSIE > Tools > Options > Content > Restrictions > Disable
etc...

RE: Log in error code 80048820 extended error code 80048401 by Chas7 on 10-22-2008 at 10:56 AM

I have just solved this problem, my machine was perfectly fine runnung live messenger last night - somehow a problem occurred overnight.  I tried all the solutions which were suggested but none worked, in the end I decided to try a different browser - Mozilla Firefox, I immediately was able to log on to live messenger again.
There is obviously an inherent problem with Internet Explorer 8 and possibly previous versions also.

I believe if you use Firefox browser you will not encounter the errors (H)


RE: Log in error code 80048820 extended error code 80048401 by Spunky on 10-22-2008 at 02:33 PM

quote:
Originally posted by Chas7
I have just solved this problem, my machine was perfectly fine runnung live messenger last night - somehow a problem occurred overnight.  I tried all the solutions which were suggested but none worked, in the end I decided to try a different browser - Mozilla Firefox, I immediately was able to log on to live messenger again.
There is obviously an inherent problem with Internet Explorer 8 and possibly previous versions also.

I believe if you use Firefox browser you will not encounter the errors (H)

WLM uses IE settings to connect to the servers. I highly doubt it was your transition to Fx that fixed this. It was most likely just a connection issue due to server maintenance ;)