Microsoft DUN Upgrade
Topic 344 · 14 responses · archived october 2000
~buzz
Tue, Jun 3, 1997 (04:03)
seed
The Microsoft Dial-up Networking (DUN) utility is perhaps the single most
important app included with Windows 95 -- other than Trumpet Winsock and a few
proprietary IP winsock clients, how else are you going to connect to the 'net?
Yet despite having numerous advantages over the competition, the standard 1.0
version of MS DUN is by no means perfect. RAS+ 95 is one client that attempts
to capitalize on MS DUN's deficiencies but does so only by adding an extra layer
to the DUN client and by using its own interface. Many users would prefer to
use the standard MS DUN interface but also want more features than the standard
client offers. Thankfully, Microsoft has responded to the demands of its users
by releasing an important upgrade to the DUN, version 1.2. Now in beta release,
the DUN Upgrade provides a number of additional features including those found
in the ISDN Accelerator Pack (actually version 1.1 of the MS DUN). These
include support for internal ISDN adapters, multilink support for dual ISDN
channels, connection-time scripting for automating non-standard login
connections, and several bug fixes to Dial-Up Networking components and to the
TCP/IP winsock stack. In fact, all the networking features and fixes included in the OSR2 OEM release of Windows 95 can be found in the new MS DUN release.
The latest release of the DUN also offers a new traybar connection icon (meaning
that the DUN no longer takes up space on the menu bar), built-in scripting (you
no longer need to use the companion DUN Scripting tool), and an option to bypass
the infamous 'Connect To' screen. The bypass option will allow you to
immediately connect to the net after double clicking on the DUN icon, whereas
before you had to first click through an intermediate (and often unnecessary)
step. Perhaps its most ambitious new feature, the new release also delivers
Point to Point Tunneling Protocol (PPTP) client capability for Windows 95. The
PPTP client allows a Windows 95 computer to establish a secure connection across
the Internet to a private network, creating a Virtual Private Network (VPN).
PPTP adds the ability to treat the Internet as point-to-point Dial-Up Networking
connection. One use for PPTP is that it can allow selective users to access a
private network that is separated from the general corporate LAN by a tunnel
server. All data sent over a PPTP connection can be encrypted and compressed,
and multiple network level protocols (TCP/IP, NetBEUI, IPX) can be run
concurrently. For more information on the Point to Point Tunneling Protocol,
check out Microsoft's PPTP FAQ. Overall, the
Microsoft DUN Upgrade is a must-have update for those who have been using
earlier versions of the client as well as for anyone who is looking for a quick
and efficient means for connecting to the 'net. Simply said, MS DUN delivers.
Pros: Handles every aspect of getting on and off the Internet, feature-replete and easy to use
Cons: Lacks some of RAS+'s advanced features, some bugs still exist in the beta release
New: PPTP client capability, enhanced ISDN support, usability improvements, bug fixes, more
For the latest information on the Microsoft DUN Upgrade, check out:
http://cws.internet.com/32crit.html#ms95dun
~terry
Tue, Jun 3, 1997 (09:43)
#1
I have to agree with Forrest that with with all of Microsoft's muscle
that they have not, until now, been able to come up with a decent stack.
I'm in the process of downloading Point to Point Tunneling Protocol as
well as the new winsock and I'll be testing this out on a dial up system
today.
You have to download the winsock first. Then you have to pick a password
and answer quite a few screens full of questions. Then be prepared to
tell them which protocol you use in your network: ip, ipx or net
eui.
You may have to check with your network administrator on this. I put ip.
The newsgroup for this is microsoft.public.pptp95.beta.discussion and
bug reports are sent to mailto://pptp95@microsoft.com
As I write this, I'm downloading the 1.16 mb dial-up networking upgrade beta.
The upload screen also has a note:
"The Windows 95 PPTP client is based on an implementation by USR." Does
this mean that Windows 95 will start actually seeing my US Robotics modems?
~ginger
Sun, Jun 8, 1997 (11:02)
#2
Forrest or Terry, is it easier to set up login scripts with this new stack?
~terry
Mon, Jun 9, 1997 (09:20)
#3
I haven't tried it yet, but I understand that you can set them up like a
recorder. I'll give it a look and see.
~ginger
Sat, Jun 14, 1997 (21:48)
#4
Let us know ok?
~terry
Sun, Jun 15, 1997 (02:28)
#5
I will when I figure it out.
~abrown
Sun, Aug 10, 1997 (19:21)
#6
I've downloaded and installed the new winsock and the new dun and got it working okay. But how do you bypass the infamous 'Connect To' screen?
~pthompso
Thu, Mar 12, 1998 (11:56)
#7
Caveat Emptor: This stack caused my Netscape 3.04 browser to no longer work; however, Netscape 4.04 and I.E. seemed to work.
As an indication that this update may have problems, Microsoft created a backup directory with all the files it replaced and a restore batch command file.
Of course, when I try to use it from within windows, several files failed to restore because of "Sharing violations." I then brought the system up in DOS and the batch file did restore the files but it couldn't run the Registry restore program executed at the end of the batch file.
It appears that if you run it first from Windows and skip each "sharing violation" file restore but allowing it to complete (i.e., let it execute the Registry restore program) and then go to DOS and run it again, then it does restore the system correctly.
IMHO, Microsoft needs to do more work on this before I will trust it. I have been using their last update successfully, though.
~kevdavis
Fri, Mar 13, 1998 (15:46)
#8
I have had big problems with the Winsock 2.2 update on my system. At first it would not operate at all, so I had to remove all traces of DUN, winsock and other networking protocols and start from scratch. It now works, but the remember password option doesn't-if selected (on my system at least) it causes a fault it mprexe.exe which in turn causes a fault in Explorer and I have to reboot to use DUN again - in fact, I have to hit reboot or turn the computer off just to exit windows since anything calling Ex
lorer (including Find) will cause a fault. However, if I type in the password myself each time, it now works normally.
Weird. I wouldn't recomend this update for the novice.
~Marak703
Thu, Mar 19, 1998 (10:10)
#9
I installed the Winsock update on my Pentium 60 (Communicator 4.04) and on my Pentium 300 (IE3.02). On the Pentium 60 (Communicator 4.04) Netscape crashed and I was unable to shut down Windows. Got back in and so far haven't had more problems. On the Pentium 300 (MSIE 3.02) IE crashed and I was unable to load IE. After $35 and two and one half hours on the telephone to MS support I would like to add this information. MS support is saying that this update is primarily for IE 4+. I definitely would suggest
eading Pat Thompson and Kevin Davis' posts before installing the Winsock update.
~kev
Thu, Mar 19, 1998 (18:06)
#10
I fixed my problem (above) by deleting and the password list DUN uses (the *.pwl file in your windows directory). For some reason it either became corrupted during the upgrade or was just incompatible. (??) After logging back into windows as for the first time and re-entering all my passwords, I have had no problems.
However this is not something you should probably bother with unless you are the tinkering kind. ;-)
~Deborama
Mon, Mar 23, 1998 (07:52)
#11
I had enormous problems after I installed this winsock upgrade, which I never should have done because I don't even use MSIE 4.0, and that seems to be what it's meant for. I can't even connect to my ISP anymore (I'm using a different one now), because I keep getting a dialogue box that demands I enter a password, which I haven't got (there are no *.pwl files on my system). I ended up having to reinstall Windows (complete nightmare as I have the "a" version which I had tweaked considerably). If anyone coul
advise me as to how I an disable that damn dialogue box that pops up just as dial-up networking is about to make its connection, I would be truly grateful. I really feel this is just another example of Microsoft's arrogance in providing an "upgrade" that is full of bugs and actually DAMAGES your computer system, perhaps even rendering it unable to connect to the Internet (as in my case).
~acura
Sat, Apr 25, 1998 (16:46)
#12
I have had similar problems to Kevin Davis and Deborah Hornstra with the Winsock 2 upgrade. First symptom was directly upon connection with ISP, RUNDLL32.EXE General Protection Fault (GPF). Looking at details there was a problem with MPR.EXE or MPR.DLL. Ultimately, EXPLORER.EXE crashed and locked windows, so I had to toggle power. I uninstalled winsock2, same problem. Uninstalled dial up networking and modem, reinstalled, same problem. I have not yet tried to uninstall TCP/IP, but I will when I get h
me. (Can only connect to the Internet from work now!). Would greatly appreciate to hear about it, if anyone comes up with the comprehensive solution. Also, who do I curse out at Microsoft. I've submitted numerous feedbacks to them in the past and it all seems to go into the ether.
~justin
Sun, Aug 9, 1998 (15:18)
#13
does anybody know how to make a connection to isp and then a connection to a pptp server a single step instead of two?
~pmcbryan
Fri, Jun 23, 2000 (22:37)
#14
I applied MSDUN13.EXE as required for free internet and my lan connections for TCPIP would nolonger support a full screen (> 1461-9) of data when using host OS/390 over TCPIP on local LAN. Both Ping and traceroute timed out at these high settings. I reinstalled windows and MSTCP.DLL got backed off which solved the problem. How do I use these big data packets with MSDUN13.EXE?