11 replies
by blackcurrant
Hi Robin
Have you tried installing SP1 for IE6, or tried uninstalling then reinstalling IE6?
Good luck
by robinarm
Sorry tried all that. Still your answer didn't help but i'll give you the points anyway.
The problem was that DNS or TCP/IP had became corrupt during the first NIC installation. Simply choosing to add remove TCP/IP then reinstall it didn't work because 1) It was corrupt at a level lower than where it binds on to interfaces and 2) windoze didn't realise it was corrupt. Ive had simmilar probs before but resolved it by corrupting it further by deleting ping and tracert etc then reinstalling it.That approach didn't work this time so I found some HKLM\System\CurrentControlSet\Services and Control values in the registry and by deleting them I could corrupt the whole TCP/IP stack enough that when I reinstalled it the reinstallation over wrotethe earlier installation properly. IE6 DNS and the rest are now fine.
by awais000
This error happened alot on windows 98 and on windows ME.
This error can be resumed only by reinstalling windows. or You can use netscape 6.
by robinarm
by robinarm
like I told answer 3 repair / reinstall/ upgrade / downgrade IE didn't work.
The problem was that DNS or TCP/IP had became corrupt during the first NIC installation. Simply choosing to add remove TCP/IP then reinstall it didn't work because 1) Itwas corrupt at a level lower than where it binds on to interfaces and 2) windoze didn't realise it was corrupt. Ive had simmilar probs before but solved it by corrupting it further by deleting ping and tracert etc then reinstalling it. That approachdidn't work this time so I found some HKLM\System\CurrentControlSet\Services and Control values in the registry and by deleting them I could corrupt the whole TCP/IP stack enough that I could reinstall it so the reinstall over wrote the earlier installation properly. IE6 DNS and the rest are now fine.
by ccsbz
by robinarm
Gateway wasn't the problem since my machine could ping internet IP's on different subnets!
The problem was that DNS or TCP/IP had became corrupt during the first NIC installation. Simply choosing to add remove TCP/IP then reinstall it didn't workbecause 1) It was corrupt at a level lower than where it binds on to interfaces and 2) windoze didn't realise it was corrupt. Ive had simmilar probs before but solved it by corrupting it further by deleting ping and tracert etc then reinstalling it.That approach didn't work this time so I found some HKLM\System\CurrentControlSet\Services and Control values in the registry and by deleting them I could corrupt the whole TCP/IP stack enough that I could reinstall it so the reinstall over wrote the earlier installation properly. IE6 DNS and the rest are now fine.
by rob
hi ,
IE6 ONLY EVER SEEMS TO WORK PROPERLY ON WINDOWS XP FROM MY EXPERIANCE AND MOST ISP'S IN THE UK DON'T SUPPORT IT ON ANYTHING BUT XP.
YOU NEED TO GOTO ADD REMOVE PROGRAMS AND RETURN WINDOWS TO IE TO ITS PREVIOUSE VERSION.
RGDS
ROB HUGHES
by robinarm
In my limited experience IE6 seems to work fine on anything you install it on. ISP's don't support it because their lazy cunts fresh out of college and can't think for themselves. I didn't need to reinstall it because IE wasn't the problem.
The problem was that DNS or TCP/IP had became corrupt during the first NIC installation. Simply choosing to add remove TCP/IP then reinstall it didn't work because 1) It was corrupt at a level lower than where it binds on to interfaces and 2) windoze didn't realise it was corrupt. Ive had simmilar probs before but solved it by corrupting it further by deleting ping and tracert etc then reinstalling it. That approach didn't work this time so I found some HKLM\System\CurrentControlSet\Services and Control values in the registry and by deleting them I could corrupt the whole TCP/IP stack enough that I could reinstall it so the reinstall over wrote the earlier installation properly. IE6 DNS and the rest are now fine.
by robinarm
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending