About Dial-Up Networking Monitor
Dial-Up Networking Monitor (DUNMon) shows the throughput on Windows Dial-Up connections.  The throughput is shown in the form of a graph and as detailed statistics.

Dial-Up Networking Monitor works on Windows 95/98/Me and 2000/XP, although it has not been thoroughly tested on 2000/XP.  Most people are reporting that DUNMon works fine on XP, however some have experienced the symptoms described in the relevant FAQ section below, and have used the notes to solve the problem.

Another important factor is your hardware, specifically whether you use a dial-up modem to connect to the Internet, or whether you have a broadband connection, using a DSL "Modem", Cable Modem or Router.  Monitoring the more traditional type of dial-up connection - using a modem or ISDN line - was the original purpose of DUNMon, however some broadband connections use a similar approach and can be monitored.  USB or PCI broadband devices are most likely to emulate the behaviour of a modem, and are most likely to work.  If you connect to your broadband hardware or router using Ethernet, it is highly unlikely DUNMon will work.  That said, if you use PPPoE to connect to your ISP, sometimes DUNMon can monitor that subsequent part of the broadband connection.

The views available in Dial-Up Networking Monitor can be highly customised.  The images below give an example of some of the default settings, however, colours, window sizes & appearances and numerous other customisations can be configured.

Dial-Up Networking Monitor running in the system
tray with the Graph window.

(165k Zip file)

See the enclosed ReadMe file for installation notes, or check the notes on the Install tab.

Users of Windows 95/98 may need to get additional downloads, as detailed in the FAQ.


Dial-Up Networking Monitor does not have a setup program, which keeps the download small.  Installation is not automatic, however it is pretty simple by following the steps below which detail how to install Dial-Up Networking Monitor on your system.

  • Once downloaded, you will need to extract the Dial-Up Networking Monitor files and copy them to your hard disk.  If you have Windows XP, you can simply drag and drop the files. If you have an earlier version of Windows (i.e. 95/98/Me/2000), you will need to install a third-party utility to open the Zip file, such as WinZip.

  • Once you have extracted the files, you may load Dial-Up Networking Monitor by double-clicking the file DUNMon.exe (with the yellow telephone icon).

    You may wish to create a Shorcut to it and place that Shortcut on your Desktop.

  • If you want to have DUNMon load automatically when you start Windows, there is an option to do this in the DUNMon Preferences window (r/click the Dial-Up Networking Monitor icon in the system tray, next to the clock, and select the Preferences... option).


Below are the questions I'm asked the most.  Hopefully, you'll find an answer that will help you.
General Windows 95/98/ME Windows NT/2000/XP


Q: When will you have a new release (if ever!), and what new features can I expect?
A: For speculation on what may be coming, see the News page.
Q: I just installed 'XYZ' update from Microsoft, and Dial-Up Networking Monitor no longer works.  Will you fix it?
A: Microsoft have a nasty habit of doing this.  See the News page for the latest "ABC fixes XYZ" news...
Q: Will DNM work with xDSL connections?
A: It depends...

Here's some feedback I recently got from a user:
'Just wanted to let you know that for people who do have a PPPoE connection and Windows XP, DUNMon 3 will show their connection. XP treats any PPPoE connection (either from a network card or a USB modem) as a dialup connection. Nothing special is needed to do it, it just works normally.'

Chris Eaton

Some xDSL connections use a USB device connected to the P.C.  Generally, this type of connection will appear to Windows as if you had a modem attached, in which case DNM will behave as normal.
The screenshot below was captured from a USB xDSL connection and clearly shows a suitably fast download speed.
ADSL Screenshot 1
However, most xDSL connections are implemented using a network card in the P.C.  This type of connection is generally termed "always-on", therefore Windows does not dial the connection and DNM does not monitor the adapter.  Having said that, some DNM users have reported that it is possible to fool Windows into thinking an always-on connection is dialed like a modem using a utility called PPPOE (PPP Over Ethernet) by Robert Schlabbach.  See the PPPOE Homepage By clicking this link, you will leave the site for more information.  Please note, I haven't used this software and therefore can't offer any advice on how to configure it, etc.  If you have questions (or problems) please direct them to the author of PPPOE.
The screenshot below was captured from an always-on connection, showing a very fast download speed.
ADSL Screenshot 1
Q: I don't understand the information Dial-Up Networking Monitor is showing me.
A: Dial-Up Networking Monitor shows the amount of traffic moving through your modem in both directions, i.e. from your machine to the Internet and visa-versa.  The most common place where you would want to know how fast data is moving through the link is probably when doing a download of either your E-mail or a file from a Web (or FTP) site.  There are many factors that determine how fast the data will be transferred, including:
  • Modem speed
  • The speed at which your modem has connected with your ISP (Internet Service Provider)
  • The speed of the connection between your ISP and the remote site
  • The speed of the machine hosting the remote site
Dial-Up Networking Monitor shows you how fast the download is going; not why it is slow (other products, such as NetMedic can attempt to show that).  The importance of this is, if you start a big download, you want to get it downloaded and off the phone as quickly as possible.  If the download is going really slowly, it may be worth stopping it and trying again at a time when the connection is faster.
Q: I have a {whatever} speed modem, but the graph goes higher than this value.  Why?.
A: In a word, compression.  Data is compressed as it is sent to you, so you can get more data through the modem that the physical connection speed.
Q: I'm getting loads of CRC errors.  Why?.
A: CRC errors usually mean a problem with the speed of your COM port and/or your connect speed being too high.  Try going into Control Panel | System | Device Manager | Ports, selecting the port that your modem is on, Port Settings, and lower the Bits per second speed.  If that doesn't solve it, try dropping down the connect speed (in Dial-Up Networking, select the Connection you use and go into Modem).  If the COM port speed solved the problem, you may need to replace the COM ports in your machine (probably an old machine) with 16550 UARTs.  This would usually mean changing your Motherboard or your I/O controller.  Not for the feint-hearted...
Q: My connect speed is always indicated as 115,200.  Why?.
A: The speed being reported is in fact the speed of the COM port.  You can verify this by changing the speed of the port (in Control Panel | System | Device Manager | Ports).  To correct the problem, try contacting the modem vendor to see if there is an updated driver for your modem.  Also, some people have reported that adding "W2" to the "Extra Settings" in Control Panel | Modems | Properties | Connection | Advanced will force the modem to report a proper connect speed.
Q: Why does DNM show a different figure to that indicated my Internet Explorer and Netscape downloads?.
A: As far as I can tell, the Internet Explorer and Netscape download speeds are the total throughput for the whole download (or, what has been downloaded so far).  DNM shows the current throughput.

For example, if you start a download, both should show similar figures.  However, if there is a pause in the download, DNM will show the zero throughput whereas the browsers show the throughput gradually decreasing.  In fact, because the browsers only seem to update their figure when new data arrives, they will not change until the data starts to 'flow' again.

See also: What's the difference between bytes-per-second and bits-per-second?.
Q: Why doesn't DNM work with AOL?
A: AOL uses non-standard software to dial and connect to their service.  DNM watches only the standard Dial-Up Networking components that ship as part of Windows.  If you load DNM on your machine, it will appear to functioning correctly and sit in the System Tray awaiting a connection.  When you dial AOL and start surfing, etc., DNM will continue to sit there watching the standard components - which are not being used - and are therefore not indicating that a connection has been made or any data is being monitored.  Currently, there are no plans to add AOL support.  If that changes, you'll hear all about it on the News page.
Q: What's the difference between bytes-per-second and bits-per-second?
A: The reason I added the Scale option to choose between bytes and bits is that most modems quote their maximum speed in bits-per-second; for example, 33,600 or 56,000.  Most users will want to see whether their modem and ISP are achieving the claimed speed, so the default is to show bits-per-second.

However, please note, many other utilities and applications (for example, Internet Explorer & Netscape) show their download speeds in bytes-per-second which can be confusing.


Additional Downloads
Users of Windows 95 or 98 may need to download some of the following files.  Unless specified, the files should be installed in your System directory (Normally, c:\windows\system or c:\winnt\system32).
  Filename Download
MSVBVM50.DLL (682k Zip file)

Q: Even with the files listed in Additional Downloads installed, Dial-Up Networking Monitor will not load, and displays a message stating that Dial-Up Networking is not installed.
A: Make sure Dial-Up Networking is installed and configured correctly (i.e. you can dial your ISP) and that you have downloaded and installed the Dial-Up Networking v1.3 update, as detailed below.

Dial-Up Networking Update
Dial-Up Networking Monitor requires that the latest version of Winsock and Dial-Up Networking are installed.  Even if you are running the latest version of Windows 95 (Win95 B/OSR2), you will still need to download and install this update.  Windows 98 includes the latest versions, so no additional downloads are required.
The easiest way to determine if you have the correct version of Dial-Up Networking installed is to check the icon that is added to your system tray (next to the clock) when you establish a connection to your Internet Service Provider (ISP), as shown below:
 or  You need to download the updates
You already have Dial-Up Networking v1.3 or above installed.

The updated versions are available from the Microsoft Web site.  You can find the update by following these steps:
  • Go to the Microsoft site ( By clicking this link, you will leave the site).
  • Follow the links to Products, Windows, Windows 95, System updates.
  • Download the Dial-Up Networking v1.3 update.
    Note: If you are offered the option to download two parts to the update - a Winsock update and an update to Dial-Up Networking - you will need to download both.

Q: Dial-Up Networking Monitor will not run, and complains the file 'MSVBVM50.DLL' is missing.
A: Download this file from the additional downloads FAQ topic (above).
Q: Dial-Up Networking Monitor will not run, and gives the following message: 'Newer runtime required'.
A: Download MSVBVM50.DLL from the Downloads page.
Q: Dial-Up Networking Monitor will not run, and gives the following message: 'Error 52 - Bad Filename or Number'.
A: This error occurs when Dial-Up Networking Monitor is installed in the root folder (e.g. C:\).  Move Dial-Up Networking Monitor into any sub-folder.
Q: Dial-Up Networking Monitor will not run, and gives the following message: 'DNM cannot start because your Windows configuration is not recognised'.
A: This message has been reported on Windows Me systems where the Registry has become corrupt.  One fix reported is to try running "SCANREG /fix" from the command line.  Thanks to Dominique Andlauer for this information.
Q: When attempting to install the Dial-Up Networking v1.3 update, the following message appears:
"Setup has detected that you are running a version of Window which includes the Dial-Up Networking 1.3 support..."

A: This is normally seen when attempting to install the v1.3 update over OSR2 (aka Win95 B).  Apparently, this situation does not occur when using the v1.3b update.  If you get this problem, it is probably worth re-downloading the update from Microsoft.  If this isn't an option, it is possible to force the installation.  To do this some manual steps are required, as detailed below:
  1. Create a temporary folder called MSDUN under your Windows directory (i.e. c:\windows\msdun)
  2. Open an MS-DOS window, and change to the folder where you downloaded the MSDUN13.EXE file to
  3. Enter the following command: MSDUN13 /T:c:\windows\msdun /C
  4. After agreeing the license information, the contents of the update are extracted
  5. Load the Control Panel and open the Add/Remove Programs icon
  6. Change to the Windows Setup tab and hit 'Have Disk...'
  7. When prompted for a location, enter c:\windows\msdun
  8. You are then given the option of installing Dial-Up Networking, Direct Cable Connection and Virtual Private Networking
  9. Check all three options and hit Install
  10. Windows will then start to copy the necessary files
  11. You may be prompted for the location of the following files: msshrui.dll, nwserver.vxd, vnetsup.vxd, vserver.vxd.  If you are, insert your Windows 95 CD and allow them to be re-installed from the CD
  12. Restart the computer when prompted
  13. The Dial-Up Networking update should now be installed, and Dial-Up Networking Monitor should load correctly


Windows NT/2000/XP

Q: Will DNM work with Windows 2000/XP?
A: Most people have reported that it works fine; others haven't had as much joy.  One thing that is clear when running DNM on Windows NT/2000/XP is that you should load DNM before you dial a connection.  If you load DNM while a connection is active, DNM will terminate with no error message.  This is on the "bug list".
See also: When I load DNM on NT, it tells me I must have RAS installed.  This is installed, so why doesn't DNM load? below.
Q: When I load DNM on NT, it tells me I must have RAS installed.  This is installed, so why doesn't DNM load?
A: DNM requires the "RAS Total" Performance object to function on NT.  Load the Performance Monitor (normally found in Start | Programs | Administrative Tools) and hit the Add (+) button.  In the Object: list, you should find "RAS Total".  If you do not, this is why DNM will not start.  If RAS is installed, but that Performance Object is not found, contact Microsoft to find out why..?
Others have also reported getting this error if they attempt to load DNM while Windows is still starting up - i.e. you can logon to the Desktop under NT while Services are still being started.  Waiting until Windows was fully initialised cured the problem.  This has gone on the "wish list" to see if it's possible to detect whether Windows is not yet fully initialised.  In the meantime, you can handle this situation manually - wait for the disk to stop thrashing before you load DNM.

Alternatively, use the following script (submitted by Richard Pratt) in your Windows NT/2000/XP Startup folder:
					Dim WSH
					Set WSH = CreateObject("WScript.Shell")
					Wscript.Sleep 10000
					WSH.Run """C:\Program Files\DialUpMonitor\DUNMon.exe"""
The script is pretty self-explanitory; it performs a long "Sleep" request in order to wait for the necessary services to finish loading before running DNM.  The amount of time that the Sleep operation lasts for will vary between systems, as will the location of DNM obviously.  To use this script, copy the lines above into Notepad and save the file as DNM.VBS.  Next, place a shortcut to that script in your Startup group.
One final tip sent to me Brian Vlaar & Zeynin Juma involves editing the Registry.  Both have reported that the RAS performance counters were not available, however, the following Registry key was modified to re-instate them:
  • HKLM\SYSTEM\ControlSet001\Services\RemotAccess\Performance\Disable Performance
Change that DWORD value to 0.
Q: When I load DNM, the icon appears in the System Tray, but disappears when I move the cursor over it. Why?
A: There are a couple of known reasons for this...
The first is when you try and load DNM under NT when a connection is already active.  Always load DNM before you dial a connection.  This is on the "Known Bugs" list.
Another possibility is that the font used by DNM on the Graph window is not available for whatever reason.  By default, DNM uses "Small Fonts" for the text on the Graph window, but this can be changed in Preferences.  If the font isn't available when DNM is loaded, it'll simply die with no error message or warning.  Go figure..?  The workaround is to manually change the font setting in the Registry by editing the following key:
  • HKCU\Software\Jon Grieve\DUNMon\GraphFontface
If that key is not present, create it as a String value.  Set the value to any font you have installed, e.g. Arial.
Thanks to Ian Macdonald for helping resolve this one..!