Discussion Locked

Win 95 DUN Fails, Gives Red X Dialog Box

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm having a problem with dial-up networking on three different laptops, all running Windows 95. Occasionally when trying to start DUN (either by double-clicking on the connectiod or on a shortcut pointing to the connectiod) a dialog box with a redX and an OK button will come up. Clicking OK dismisses the dialog box, and then nothing else happens. Rebooting will sometimes fix the problem, but on one of the laptops even a series of reboots did not help. Also, one laptop was having the problem, I uninstalled/reinstalled all networking, and it worked fine for several months; the laptop redeveloped the problem about a week ago, even though nothing has changed on the laptop.

Microsoft's knowledgebase has nothing on this, and I'm desparate to find an answer. Anyone have any suggestions?

10 replies

by stillatit

If your modem is on a PCMIA card, make sure that the card is seated. If the cord was tugged at some point, the card may have been pulled just enough to not be seen by the OS.

In any case, you should look in the System control panel, Device Manager, and make sure that you have a serial port and a modem where you think you do. If Win95 does not see the port at boot time, it will mark it in device manager, but you get no other indication until you try to use it.

Before reinstalling all networking, try reinstalling just the modem drivers.

Good luck.

by crobinson

Thanks, but the modems on all three are fine. I was able to use HyperTerm to dial-out to other services. Everything in Device Manager appeared fine.

by chuck

Which version of DUN are you using? We had various problems ( not GPFs, but some Winsock and RAS server connection problems with 1.2 but since we switched to 1.3, they seem to have been resolved. I think you can still download 1.3 at the MS web site. Make sure you uninstall the old version first, power down and then restart and load the new version.

Good Luck!

Chuck

by kgosnell

As it builds up over a period of time I would suspect something is hogging the space for caching and not allowing Win to wipe it, if you can access the dialout , start it and stop it before it connects, partually clearing a major portion of the cacheing for the modem, empty the C:\Windows\Temp file, this is used for some caching, do a refresh on the Wondows screen before you attempt a dial out, make a tiny AVI file and select properties and preview, this clears the Video Cache and memory,Third party programs are notorious for causing Win not to refresh the caching, if you pinpoint it , ask the maker to provide the fix. Luck

by bucko77

I've found that reinstalling MSDUN1.3 can sometimes provide the answer to mysterious DUN problems.

Perhaps one of the components has been overwritten with an earlier version

good luck

by crobinson

Partial solution: We use Microsoft NetMeeting to help with technical support. Two out of the three laptops had NetMeeting set to start up when Windows starts. After NetMeeting was disabled, the laptops have not had ANY problems dialing in, or occurrences of the red X. I'll have to check the third laptop, but I think it will be the same thing. No idea why NetMeeting would cause this, but maybe this (or another program running in the background) would help other people with this same problem.

This discussion is closed to new replies.