Unable to connect to internet
This problem relates to a fairly old toshiba laptop that works terrific except suddenly about 3 months ago would no longer connect to the internet although it would to it's host/aol allowing me toe sen/receive email only. The error message is from iex 4.0 and it says "unable to connect, an internal error has occured in the windows extensions"....i've done all the obvious things, modem-properties/internet-options-connections/scandisk/defrag/protocol/none worked. Even reinstalling aol software and upgrading, even another isp/juno, nothing changed except the error message with juno. Also doing the repair on iex 4.0, it fixed something in that but no connect.
If someone has a brainstrom let me know otherwise, I think I should re-install win95 if all else fails. I'm in no hurry, and can experiment with any ideas. Below is the end result of a lot of work on the part of some very helpful, very knowledgeable people, it should help with this diagnosis.......
system is win95/oem/4.00.950.B
super thanks
>>Rollin' Rog
Moderator
I can't really answer your latter questions, but see if either of these apply:
http://support.microsoft.com/defaul...b;EN-US;q241344
http://support.microsoft.com/defaul...b;EN-US;q188952
http://support.microsoft.com/defaul...b;EN-US;q222909
It rather sounds like a breakdown between AOL and IE
ME>thanks....
i read the microsoft web page and found something interesting,
for iex 4.0
they imply that multiple copies of winsock.dll are one of the problems that bring up that error message....."windows extensions"
This behavior can occur in any of the following circumstances:
>>There are multiple copies of the Winsock.dll, Wsock32.dll, or Wsock.vxd file, or one of these files is in the wrong folder. Rollin' Rog
Moderator
This is a bit tricky since there are different version and size winsock.dlls.
The proper one for Win95 is approximately 42k bytes; the others about 22k
I would ensure that the one in C:\windows is the one for Win95 and rename all others to winsock.old
ME> Ok, renamed the extra winsock files, leaving one in windows, still unable to connect. Going back to the read more about the error message "an internal error occured in the windows extensions"
be back later.........
just did a little research, following microsofts advice, renamed winsock32.dll to old, and am supposed to reinstall a correct version from the cd, ugh, don't have it. I know I can find this on the net but how do I know the correct version, by its size??
hot on this trail..
> Rollin' Rog
Moderator
You may also need to delete the winsock2 registry keys as indicated in the article, and then remove and reinstall DialUp Networking. BUT, you will need the CD for that (or c:\windows\options\cabs). Don't delete the registry keys unless you can update. You can do a Registry>Export to save them first, if doubtful.
Also, I don't know how big this is, but if you can get it on a floppy to copy and install, it might help:
http://www.microsoft.com/windows95/...ts2/Default.asp
I believe the wsock32.dll should be a part of the update. (there is no winsock32.dll)
You can also find most of your needed Win95 dlls on this site:
http://www.drd.dyndns.org/index2.html
ME>> OK, downloaded the wnsock update, 1MB, installed and ran into an error installing wsock32: that message was "please install TCP/IP or if it's installed, reboot, and return this setup something or another \WS2BAKUP\WS2BAKUP.BAT
AND this is from the windows log,
WS2SETUP begin: 03/25/2002 04:51:44
RegQueryValueEx(VendorInstallDll) failed
VendorWantsMSTCP=1, WantsMSIPX=2, WantsSetupUI=1
WantsMSDNS=1, WantsMSSAP=0
New wsock32.dll file version: 0004000a.00000678
Detected existing backup files - not backing up
Couldn't locate WSOCK32.DLL, error=1157
Winsock2/INET key found
Winsock2/INET/ProviderName='Microsoft TCP'
Attempted to upgrade to Microsoft TCP 2.0, but Microsoft TCP 1.1 is not installed
WS2SETUP end: failure
PLEASE ADVISE:
i'm gonna check on the TCP stuff
> Rollin' Rog
Moderator
sounds like it is looking for the other wsock32.dll before it installs the new one. Strange; but try renaming what you had back to the original name, or download a new one. TCP/IP has to reinstalled through the Control Panel Network applet. Check to see whether it is listed. I believe it too, reinstalls wsock32.dll so that may be why that suggestion is included in the error message. Again you would need your CD or cab files on the hard drive (c:\windows\options\cabs) to add or remove and reinstall it.
ME> I followed this procedure:
TCP/IP Is Not Installed
Install TCP/IP:
Click Start , point to Settings , and then click Control Panel .
Double-click Network .
Click Add , click Protocol , and then click Add .
In the Manufacturers box, click Microsoft . In the Network Protocols box, click TCP/IP , and then click OK .
Click OK , and then click Yes when you are prompted to restart your computer.
Followed that, saw windows build that driver, but did not see a box for restart pc, did the whole thing again, but the windows driver didn't do its think, so I restarted, tried the wsock update, same error
>Rollin' Rog
Moderator
Do you now have a wsock32.dll in c:\windows\system? If not download one and copy it there.
And is TCP/IP showing as an installed protocol in Network now?
ME> WSOCK32.DLL IS showing in windows/system now, I ALSO SEE these components installed in NETWORK;
TCP......AOL ADAPTOR
TCP.....dial up adaptor
TCP.....aol dial up adaptor
TCP......dial up adaptor #2 vpn support
but trying the wsocksetup.exe update, failed.
after wsock was installed to windows/system
SINCE I have wsock installed, I don't need to try and work the update??
I think this is the problem with this whole connecting thing, we'll see......
Mosaic1
Senior Member
Do you have the AOL installation software? For the heck of it if you do, try this. Go to Device Manager>Network Adapters and uninstall both the AOl Adapter and AOl dialup adapters. Reboot and restart AOL. Let is reinstall the adapters. I am not sure if in your case you'll need the Software. I unintsll the aol adapters when I have problems and don't need the CD. I use Compuserve which uses the AOL adapters.
ME>ME> YES,,
I have aol 5.0 installed, I upgraded to it hoping it would increase my chances of connecting, but before that I just re-installed aol 4.0. Neither worked.
I have just removed both aol adaptors. Rebuilt them but still not connecting, just to let you know.
>Rollin' Rog
Moderator
This is rather a long shot, but I think it would be worth trying. It is a fix for damage to the winsock2 registry key which causes symptoms such as you have, resulting from the installation and incorrect removal of certain programs such as Webhancer and New.net.
It's small, just unzip it and copy it over to the 95 machine and give it a run.
http://www.lavasoft.de/aaw/binary/whndnfix.zip
ME> Ran the socketfix,
after checking winsock2 intergity it responds with "no problems found", click to continue, then program closed.
Is the TCP/IP installed?
I posted that TCP aol data but am not sure if that is what to be satisfied with. I'll double check something on that, and maybe should try the registry fix that was also talked about on the microsoft website>>>>
"The Winsock2 Key in the Registry Is Damaged
Uninstall Dial-Up Networking.
Using Regedit, remove the following key:
HKEY_Local_Machine\System\CurrentControlSet\Servic
es\Winsock2"
I really appreciate all this one on one advice, from everyone in this forum, it is really narrowing this down. This problem has eluded everyone in all my former posts in different forums and this is the first time where feel I'm on the right track after really attacking it so methodically. So thank all of you for being so interested. I hope I can reward everyone's efforts by putting SOLVED on this post......... .....so that brings me back to the registry.....and the microsoft suggestion
>Rollin' Rog
Moderator
If it's not too late, export that key to the desktop before deleting it. If you are unable to reinstall DUN or TCP/IP, I don't think it will be restored. You might want to compare it with your Win98 machine, although I don't know what differences there should be, if any, with a Win95 installation. If you can't reinstall it and want to be really bold, you can export your Win98 winsock2 key to the desktop, copy it to the desktop of the Win95 machine and double click it to merge (after exporting and deleting the Win95 version)
I'm not sure whether what you are seeing in th Network Applet is TCP/IP protocol either; I don't have Win95, or AOL but here is what mine looks like (see attachment)
Attachment: network.jpg
This has been downloaded 3 time(s).
ME> CHECKING MY CONFIGURATION:
all of the below appear in the window for network, I clicked on them to display the explanation which I have included for each below...l.haven't touched the registry yet......also in your screen shot I noticed that where you have the TCP/IP highlighted, "windows logon" appears in the window......when my TCP/IP IS highlighted, "client for microsoft network" appears in the window, the "windows logon" having not been chosen.....
Client for microsft networks
AOL adapter.....the aol adapter connects aol to the internet
AOL dial up adapter....connects aol to the internet
Dial up adaptoer.......lets your computer connet to PPP, RAS and Newareconnect dial up servers using a modem.
Dial up adapter #2 VPN support.........lets your computer connect to PPP, RAS and Neware conect dial up severs using a modem or ISDN
Microsoft virtual Private Networking adaptor....enables your computer to extablish private network connections across the internet
IPX/SPX- compatible Protocol > Dial up Adapter #2 VPN.......is a protocol Netware and Windows NT severs and win95 computers to communicate
NDISWAN Microsoft virtual Private Networking adaptor.....is used by the DIAL UP ADAPTOR to access ISDN
TCP/IP Aol Adapter.....is the protocol you use to connect to the internet and wide area networks
TCP/IP AOL dial up Adapter.....same as above
TCP/IP..AOL dial up adapter....same as above
TCP/IP..Dial up adapter #2 vpn support.....connect to internet and wide area networks...
Looks like way too much installed and some of it appears redundant.......
>Rollin' Rog
Moderator
Posts: 4961
I agree, if you are not networking I would remove all except the
AOL adapter
Dial up adapter
TCP/IP Aol adapter
I don't think you need Client for Microsoft Networks either; and you can select "Windows" logon for simplicity. No need for passwords.
But what I don't know is whether you need a separate TCP/IP protocol for the windows Dial-up adapter; someone else will have to inform there. That may be what this is:
TCP/IP..Dial up adapter #2 vpn support
Perhaps further clues here:
http://support.microsoft.com/defaul...b;EN-US;q238550
http://support.microsoft.com/defaul...b;EN-US;q165474
>Mosaic1
Senior Member
Posts: 1322
If you had access to the correct files, you could manually uninstall and reinstall DUN. Here's the link in the event you may find the correct files to use.
http://support.microsoft.com/defaul...b;EN-US;q181599
SUMMARY
This article describes how to remove and reinstall Dial-Up Networking and Transport Control Protocol/Internet Protocol (TCP/IP). These steps may be necessary under the following conditions:
You are unable to connect to a remote computer, remote network, or the Internet using TCP/IP bound to a dial-up adapter.
You have verified the accuracy of your TCP/IP settings.
You have verified your modem is functioning correctly.
ME>> I removed all the extra installations from network leaving the ones that were obviously needed. "Window logon" just enabled itself, in iex/connections, changed "dial up using a modem" to "access through local are network", that info came from the microsoft page on this error, nothing changed.. . .I followed their procedure to the letter. I don't know about DUN, leaving that alone for now. . . BTY, all of those links are excellent resources that I saved and followed all of them so far.
The thing about this problem is that it just happened, started the pc and it didn't connect to the internet anymore, but modifications have been made in all these areas in the past. . . if that's a clue. To bring this up to date, I have done everything posted out here so far except deleting the registry key and the DUN. . . but I'm tempted to do the registry key now.
It would be cool to run a system check somehow, that would pinpoint the problem, some kind of diagnostics... . .
