Skip to main content

Windows Live Messenger: Error Code: 80048820 (80048439)

Fanatic Live - All about MSN Messenger & Windows Live technologies

If you're using a NetGear wireless router and you're experiencing Windows Live Messenger (or MSN Messenger)
Error Code: 80048820 / Extended Error Code: 80048439,

Windows Live Messenger: Error Code: 80048820 (80048439): Symptom
try reducing the size of the MTU (Maximum Transmission Unit) in the Router's WAN Setup page – from 1500 bytes to 1400 bytes. (However, see Updates below for optimal values.)
Windows Live Messenger: Error Code: 80048820 (80048439): Fixed
I have had this problem for several months. My office network is connected to the Internet via a set of transparent proxy servers. Windows Live Messenger's does not detect any connection problem. However, it just does not sign on!

Today I looked into this problem again, and fortunately after Googling for a while, I found a viable solution from Fanatic Live website:
Stretch suggested that NetGear users go to the WAN Setup page and change the MTU size to 1400 bytes.

I followed his suggestion and it worked like charm!


Thanks, Stretch. I appreciate it!

Keywords: , , , , , , ,

Update: August 17, 06:

A friend of mine suggested that the MTU value of 1400 maybe too low as it will increase too much overhead during large file transfers. The MTU size is like the maximum size of packet transmitted over the network. Small MTU size increases the number of transmitted packets. Here's an information on MTU from NetGear Router WAN Setup page:
The normal MTU (Maximum Transmit Unit) value for most Ethernet networks is 1500 Bytes, 1492 Bytes for PPPoE connections, or 1436 for PPTP connections. For some ISPs you may need to reduce the MTU. But this is rarely required, and should not be done unless you are sure it is necessary for your ISP connection.

I set the MTU to 1492 and error 80048820 (80048439) still occurred. I reduced the value one step further to 1436 and the problem disappeared. Therefore, my current MTU setting is at 1436 bytes.

Comments

Post a Comment

Popular posts from this blog

iTunes: Error 261 while Burning Data CDs/DVDs

Apple Discussions: 261 error while burning MP3 CD. I usually put an aphostrophe (') in the name of playlists and was having error 261 burning CD/DVD data discs since iTunes 5.1. Upgrading to iTunes 6.0 for Windows doesn't help. I was burning a music DVD this morning and had Error 261 again. So I went to Apple iTunes Discussions site and look for a thread on this. Viola! There are many people having the same problem as mine. The thread ends at a point where someone removing ampersands, the '&' symbols, from their playlists and could avoid this error. I tried removing aphostrophes from the name of my playlist because aphostrophe falls into the kind of non-alphabet characters that needs escaping in some programming languages. It works!! Keywords: itunes , windows
17 comments
Read more

Microsoft Office Outlook Connector 12.1 Beta 2 Crashes Thai Language Input in Outlook 2007

It's been more than a year since I last blogged. I've been busy with work and also don't know what to blog. Here comes my new findings: Microsoft Office Outlook Connector 12.1 Beta 2 + Outlook 2007 + Thai Language Input = CRASH This has also been proven here . I downloaded the Outlook Connector the other night for improved supports to Windows Live Hotmail -- only to find that whenever I start typing e-mails in Thai, i.e., hit the "language switch" key Outlook simply crashes! I googled for " outlook 2007 crash language switch " this morning and find someone having the same Outlook Connector insta.led and the same problem as mine. So, Outlook Connector is most likely the cause of trouble. I uninstalled Outlook Connector this morning and, yes, typing in Thai doesn't crash Outlook 2007 anymore! Keywords: Outlook , Thailand , Troubleshooting
5 comments
Read more

MPICH2: mpdboot failure due to conflicting /etc/hosts entry

One single line in the /etc/hosts file on my Ubuntu Linux machine wasted my precious whole afternoon. I had some assumptions about the cause of this problem but I don't want to spend too much time investigating on what really caused the trouble. Anyway, here are the listings of what worked and what didn't: /etc/hostname ubuntu mpd.hosts.cluster master worker-01 Bad /etc/hosts 127.0.0.1 localhost localhost.localdomain ubuntu 192.168.200.128 master 192.168.200.129 worker-01 Result thitiv@ubuntu:~$ mpdboot -n 2 -f mpd.hosts.cluster thitiv@master's password: mpdboot_ubuntu (handle_mpd_output 359): failed to ping mpd on master; recvd output={} Good /etc/hosts 127.0.0.1 localhost localhost.localdomain 192.168.200.128 ubuntu master 192.168.200.129 worker-01 Result thitiv@ubuntu:~$ mpdboot -n 2 -f mpd.hosts.cluster thitiv@worker-01's password: thitiv@ubuntu:~$ At this point, with the /etc/hosts now fixed, the MPICH2 cluster could be booted up successfully. I don't want t...
8 comments
Read more