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

"Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine" Error on Windows 7 (64-bit) + Office 2010 (64-bit) + Visual Studio 2010

If you use (1) Windows 7 (64-bit), and (2) Office 2010 (64-bit), and  (3) Visual Studio 2010 to write an ASP.NET code to connect to Access or Excel database using the Microsoft.ACE.OLEDB.12.0 provider and consistently get the "Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine" error, try installing the 2007 Office System Driver: Data Connectivity Components , which is basically a Microsoft Access Database Engine 2007 Redistributable for Windows (32-bit) from http://www.microsoft.com/download/en/details.aspx?id=23734 Many forums suggested by Google Search suggest installing the Microsoft Access Database Engine 2010 Redistributable for Windows (32-bit, 64-bit) downloadable from http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=13255 but it wouldn't help because Visual Studio 2010 is a 32-bit application; what you need is a 32-bit Data Connectivity component. The 2010 download will not allow you to install i...
Post a Comment
Read more

Tips: Mac OS X: Full ANSI Color Support in Terminal.app

I'm trying to switch my Java development platform from Windows XP to Mac OS X Tiger. Wondering how to colorize the Terminal screen, I spent some time googling. From the discussions at the end of this page: macosxhints.com - Add full ANSI color support to Terminal.app Here's a summary of how to enable it: With bash shell as default, simply add export TERM=xterm-color [I prefer this for Linux compatibility] or export TERM=dtterm in the ~/.profile (single-user) or /etc/profile (system-wide) Color terminal is enabled. Use ' ls -G ' (the -G enables color output) to test. Add alias ls='ls -G' in the profile file for convenience. Keywords: mac-os-x , unix , terminal , shell , tips
1 comment
Read more

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