NICE TIP THERE
"ImhoTech" <> wrote in message
news:...
>
> Probably not. It might cover reinstalling Dial-up networking, but the key
to
> that fix is the registry edit. Reinstalling Dialup networking without the
> deleting the registry entries, doesn't update the registry entry. Is some
> cases there may be problems that can be fixed by reinstalling DUN and not
> using the registry edit, but it only takes a second to delete the entries
> and it can't hurt anything, and may save you from going through the
process
> twice. I really don't recall where I first learned of that particular fix,
I
> think it was on MS Technet.
>
>
> "David K" <> wrote in message
> news:...
> > On Mon, 28 Jul 2003 14:20:58 -0400, "ImhoTech" <>
> > wrote:
> >
> > >First navigate to network properties, verify what is installed. You
> should
> > >only have Client for Microsoft Networks, Dialup Adapter and TCP/IP,
> Primary
> > >Network Logon should be set to Windows Logon. Remove anything else
> listed.
> > >
> > >Next navigate to Dialup Networking, remove any current DUN connections.
> > >
> > >Go to Add/remove programs, click the Windows Setup tab. Double click on
> > >Communications and remove the check by Dialup Networking. Close up
> > >Add/Remove programs, but Don't Restart.
> > >
> > >Run regedit, navigate to
> > >HKEY_Local_Machine\system\currentcontrolset\servi ces and delete the
> entries
> > >for Winsock and Winsock2.
> > >
> > >Now reboot.
> > >
> > >Run the Internet connection to rebuild the DUN connection. (You may get
> an
> > >error msg at the end, but its unimportant) Reboot.
> > >
> > >Everything should begin working.
> >
> > Interesting. I see it fixed his problem. Would a Network+ book cover
> > troubleshooting these sort of connection problems?
> >
> > David
>
>
|