Forum Home
Press F1
Thread ID: 8601	2001-04-06 13:12:00	Internet connections not responding after DUN	Guest (0)	Press F1

Post ID	Timestamp	Content	User
10947	2001-04-06 13:12:00	PCWorld - Press F1, My internet connection stopped working from one day to the next. I am using Win98 (1st Ed) on a PII/450MHz machine, with 128MB of Ram. My 56K modem works fine and I am able to dial in and make a connection with the ISP using the standard Win98 DUN icon . The user name and password verification works and I get connected without fail at say 44kbps. When I start up any application such as Eudora or Netscape I get an error message and no connection. For example the Eudora error message reads: 'Error getting Network address for pop3.paradise net.nz, Cause: Host not found (11001)'. For Netscape it is: 'Netscape was unable to create a network socket connection. There may be insufficient system resources or the network may be down'. For Copernic the message is: 'You must be connected to the Internet to perform this operation'. Other applications give similar messages, and the effect is similar to my trying to start up an application, without first making a DUN connection. I am able to ping (from a DOS prompt) any URL domain, from my own ISP or others and get reasonable turn-around response times. I have run the WinIPcfg.exe program and checked all settings. I have tied various diagnostic programs such as Norton System Works, Nuts&Bolts, First Aid etc. without any beneficial results what so ever. I have checked with the ISP helpdesk and they have taken me step by step through the config, no change. Frankly I've run out of ideas and don't know where to go next. It seems as if there is one critical Windows file which is corrupted, but after re-installing Win98 several times this doesn't offer a solution either. Where is the problem and how can I tackle it? I've had to set up an alternative computer just to handle my email but it is not a viable solution in the long run. Could someone help me please with advise or point me in the right direction. Lost in Cyberspace!	Guest (0)
10948	2001-04-07 00:01:00	Remove and reistall TCP/IP Dial up adaptor. Go to www.zfree.co.nz/help. It gives you full instructions. Make sure you have your original Win CD though.	Guest (0)
10949	2001-04-07 23:07:00	Hello Peter It seems to me to be another case of just to much software accessing your internet connection, what happens is the system overloads and it just stops transfering information, but usually remaining connected Till your ISP detects an idle line and cuts you off. I would suggest you troubleshoot the problem by removing all the programmes that access the net Browsers,e-mail clients,instant messengers, etc disable the auto update feature in any programmes that are running it. Then start by reloading Netscape see if it now performs OK if it does, you just have to be more selective in how you install multi utilities that perform similar functions ( have them starting when you require not auto )also if your not using Internet explorer you may as well get rid of it, type in Ieradicator in a search engine and download this free utility, it will completely and safely remove Internet explorer from your system. Alan	Guest (0)
10950	2001-04-12 18:41:00	I had a similar problem and I've no idea how it happened but you have probably checked this one out. Are you connecting through a proxy server, you don't need this with Paradise. Mine got ticked and caused the same symptoms. I have had this box ticked a couple of times, how, I don't know but unchecking it fixes it.	Guest (0)
10951	2001-04-24 10:57:00	Hi Peter, Thanks for your comments. I've checked them out. You were on the right track but it wasn't the whole answer. With some invaluable help I finally found the fix via an MS website knowledge base article # Q188952. This described the exact symptoms. In short I removed all the dial up network items in <Control Panel>, <Network>, <Configuration tab>, 'Microsoft family logon', 'Dialup adapter' and 'TCP/IP'. After that I deleted the 'Winsock2' key in the Windows 98 registry, using 'Regedit', under the heading: HKEY_Local_Machine\System\CurrentControlSet\Servic es\Winsock2. I then had to reinstall Windows Dialup networking from the CDrom. That fixed the problem and I enjoying the net once more. Thanks again for your thoughts.	Guest (0)
10952	2001-04-24 11:09:00	Hello Alan, Thanks for responding to my query. Unfortunately my problem was not in any way connected with a prolif-iration of SW trying to dial into the network, rather it was a plain old corrupt file. With some invaluable help I finally found the fix via an MS website knowledge base article # Q188952. This described the exact symptoms. In short I removed all the dial up network items in <Control Panel>, <Network>, <Configuration tab>, 'Microsoft family logon', 'Dialup adapter' and 'TCP/IP'. After that I deleted the 'Winsock2' key in the Windows 98 registry, using 'Regedit', under the heading: HKEY_Local_Machine\System\CurrentControlSet\Servic es\Winsock2. I then had to reinstall Windows Dialup networking from the CDrom. That fixed the problem and I enjoying the net once more. Thanks again for your time and thoughts. Peter	Guest (0)
1