Windows 98/Internet Explorer Problems - Urgent!! Please Help!!!!

[Helly Hansen]

Hello,

I am a technician and I'm normally giving support but now I need some myself. I've never run into this before. Everything was working fine on a family members Pentium 200MMX system (Windows 98, Internet Explorer 5 Beta & Netscape Communicator 4.5 using JPS.net as the ISP)

There is also an MTU program on the system.



After installing AOL 4.0 Gold so I can get my email, the system will not access any URL's (www.xxxx.com) whatsoever on Netscape or AOL. In AOL I can get my email and type in AOL keywords such as "AOL Press" and even download though it won't go to AOL.com. The modem is a Lucent 56K V.90 that is functioning fine, it's pretty quick, never had any problems, even able to dial up OK and dial up to other systems using Hyper Terminal. In Netscape 4.5 you can IM but can't access any email or any URL's. "Unable To Create A Network Socket Connection" The error in AOL 4.0 is "Page Cannot Be Displayed".



I have tried adjusting port settings, ports speeds, the modem is set for software flow controll (XON/XOFF) like it should be. I have installed the latest Lucent V.90 drivers (5.44), uninstalled and installed the drivers several times. I have removed the settings from the MTU program, I have also tried changing the settings to reccommended and tweaked with them. The max MTU is currently 576.



I have tried flushing the cache and history. I have removed AOL 4.0, (Netscape is still the same) I have tried removing and reinstalling the dial up adapters. I have changed dial up numbers. I have uninstalled and reinstalled Netscape. I have unistalled and reinstalled Internet Explorer 5.0 Beta. I have removed it and just tried 4.01 and still the same problem but with a different error message in AOl "An Internal Error Occurred In Windows Internet Extensions". I have turned all the security settings off. I have tried adjusting all browser settings. It's really strange in AOL because every URL I enter defaults to (res://C:\windows\system\shdoc.dll/dnserror.htm#http://www.xxxxxx) the xxx's stand for whatever website or URL is entered. I have even tried repairing the Internet Explorer under Control Panels-Add/Remove Programs-Add/Remove. I have even checked for viruses and have run Scandisk. Still nothing is a solution. I am using another computer system right now.



I am running out of solutions. This is not my computer and I am very obligated to take care of this problem.



Can Anyone Please Help Me With Some Real Solutions?? Any Similar Problems??



Please Email Me At HellyH72@AOL.com



Thank You!!

Brandon Sandifer

[StarWatcher]

Well Helly, there are a couple of things you can check:

1. Check for multiple copies of Wsock32.dll in your system-You should only have 1 in Windows\System-Rename any others at DOS.
The W95 Wsock32.dll should be 65K in size with a date stamp of 7-11-95-W98-40K in size and 5-11-98. For good measure you should extract a fresh copy from your Windows CD.

2. Aol is very Flaky-Go into your network Icon and and check your settings-Highlight TCP\IP AOL Adapter-click properties
DNS and WINS should be disabled-IP address should be set automatically-You should have Windows logon.

3. In Network Icon-try removing ALL adapters-empty the sucker out-Reboot click AOL-They will all rebuild except Microsoft dial-up adapter-ADD that-reboot.Then try to sign on to AOL and see if your flaky AOL browser works.

[joe]

Your Winsock is corrupted. You need to reinstall it.

[Jin Vitas]

I told you the FIX on the other POST in general.. If you do not want to do it.. that is fine..

[evans]

This may give you some added information on your problem. I am working on one specifically mentioned on this website:
http://members.aol.com/ojatex/showdoc.htm

[xanatos451]

Kudos to the last guy who posted. Went to the site and sure enough. Exact problem, exact fix. Nice job on hunting that one down.

[xanatos451]

Actually I was wrong, didn't fix it however the next thing I did, did the trick.
I had the exact issue recently with a customers' machine. The problem did have to do with a winsock issue however it was not resultant from a corrupt file but a corrupt registry entry. If you search the regsitry for winsock and delete every entry found, and then remove and reinstall networking components, the problem will be resolved.