Note: I wrote this page a few years ago when I worked as a tech for an ISP. Although I'm still in the IT field (network support) I'm not as up on this issue as I used to be when I dealt with it eeryday. The page has not been updated in a long time - however I'm sure most of the information is applicable to issues that people are dealing with today, if they are getting the error.

It does seem that most of the ISP's who had equipment that would help generate this error have either upgraded it or gone out of business. And Windows native dial-up networking has improved with Win98 and the later service packs of NT.

Likewise with modems, they have improved and are more reliable today - even a whole lot cheaper. The one part of the equation that hasn't changed much are the phone companys and of course the lines - both in your home and out. Keep this in mind when trying to pin this problem down, and good luck.

If you've gotten this message and are stuck, you've come to the right place.  I've got a fix that will work for most people and if that doesn't do it,  read through some of the associated pages.  This has been one of the more frustrating problems that I've encountered as a support tech.  After going through a user's
settings again and again,  uninstalling and re-installing DUN,   removing and adding modems,   double-checking all the network protocols;  it still prevails.  Often it's an intermittent problem,  in a few cases a re-boot will cure it, sometimes a format and re-install will get rid of it,  and in other cases nothing will.  And from my research it appears to be pervasive,  affecting a small percentage of people net wide. 


Having scoured newsgroups, web sites,  and tech support manuals I've seen no definitive answer on the cause or a possible solution.  Is it a modem incompatibility problem? Wrong modem defined issue?  DUN bug? 

Corrupt Registry?  ISP problem? Network protocol issue?  Win95 bug?.........

Try the solution below.  It's what I've found will work most of the time - although I'll be the first to admit it won't work for all.  If it doesn't do it for you, check the solutions pages below;  if you have anything to add, Email me.  I'll try to keep these pages updated every few weeks. I know how frustrating this problem
can be and hope you find something here that works for you.

Try this 
I've found that this will work for the majority of people who get this error message.  If it doesn't work for you,  check the solutions pages below for many other possible fixes.      Get the Kernel32 Update to Windows 95 and install it. 

This update resolves a memory leak which occurs when opening and closing a Socket
using the Windows Sockets API.

>2)     First we need to get rid of everything associated with your current DUN connection. This includes any shortcuts on the desktop, any password list files and the DUN connectoid itself.If you have a shortcut for your dial-up connection on the desktop, right-click on it and delete it.  Then go to My computer
Dial-up Networking and remove the connectoid itself by right-clicking on it and deleting it.

Next go to Start -> Find -> Files or folders,  and do a search for any password list files by typing in pwl in the "named" box and clicking on Find now.  

We're looking for files with the extension .pwl.   You mayhave one named username.
pwl.  Username being your login name for your ISP. If so delete it by right-
clciking on it and deleting it.

3)     Now we need to remove all network protocols currently installed.  Go to
the Control Panel -> Network and remove all network protocols installed by
highlighting them one by one and clicking on remove.  If you are networked to
other computers you may want to remove only dial-up adapter here.  Then
click on OK and you'll be prompted to reboot.  Do it.

4)     The next step is to add back the Network protocols needed and the re-
built DUN connectoid. The easiest way to do this is to use the Internet Set-up
Wizard. You may be prompted for your Windows 95 CD,  so have it handy. 
Go to Start->Programs-> Accessories->Internet Tools and click on  Internet setup
Wizard.  Yours may be called "Get on the Internet".  Press "next" at the first
screen that comes up.  If it asks if you want automatic, manual or current; choose
"manual" and follow the instructions below.

A series of screens will come up - the answers are below.

How to Connect-                    Check "connect using my phone line" if this
question is asked.

Internet Mail -                        Check yes if want MS Exchange - otherwise "no".

Service Provider Info -            type in your ISP's name in the box.

Phone Number -                     type in the appropriate phone number from your list.
                                             Remember to put *70 at the beginning of the number if you
                                              have call waiting. This will prevent you from getting
                                              bumped off-line if you receive a call while connected.

User Name & Password -       type in your user ID & password (not your real
                                              name unless its also your user ID.  These may be
case-sensitive so
                                              check with your provider on this.
 

IP Address -                           Check "My Internet service provider automatically
                                              assigns me one".

DNS Server Address - Type in your ISP's DNS numbers, primary and secondary
if any. 

Then click Finish after this screen.   Reboot if you're prompted.  Give the dialer
a try (while keeping your fingers crossed) and you'll hopefully get connected.
  If you don't read thru some of the solutions below.  These were obtained by
posting requests in various usenet newsgroups during the past few months,
so they are the best ideas on this subject available to date.  If you find anything
else that works, please Email me and let me know.  Good luck.

Basic Setup   -  These potential fixes have to do with configuring your
basic Dial-up Networking settings.  You won't find anything too unusal or daring
in here, but then again, something you overlooked might be just the answer you've
been looking for.

Comments Page  -   General comments from around the net concerning
the error message and these pages...

Innovative   -  These potential fixes are unorthodox in their approach.  They
may or may not work for you; but they are certainly worth looking at and trying...

Phone line/ISP   -  This page deals with the possibilty that the problem may
be coming from either the phone lines or your Internet service provider.