HTTP 500 - Internal Server Error

[Paul W]

Just recently, (ie: I have never had this happen before)
when I attempt to contact my Router server at 192.168.1.1
I get the error ; http 500 - internal server error. This
does not occur on any of my other of my LAN clients (4)
running ie6.0SP1, windows 98, Netscape or Linux.
I turned off all security measures, including ICS and
Norton Antivirus on the machine and I still get the same
error. Finally, to eliminate the possiblilty of a virus or
rogue script, I did a complete reformatting and reinstall
of Windows XP Pro and retried prior to, and after
downloading SP1 update, and still get same error. It only
seems to affect http access (port 80) because I can ping
the adress successully. Everything else seems to work
fine, ie: I have full access to the Internet. I also
installed IIS on the machine and tried to contact the home
page - same error. (Again, I was able to connect from my
other machines on the LAN)In desperation, I installed
Nescape 7.0 on the machine and lo and behold, I was able
to connect immediately. It definetly appears to be a
problem with Internet Explorer and its handling of
internal server communication with port 80. Is there a
possibility that the internal bios has been compromised? I
am at a loss!! Any suggestions would be appreciated.

 

[H Leboeuf]

To everyone that have had this problem, I finally found
the answer, please follow this link:

http://www.experts-exchange.com/Operating_Systems/Win98/Q_11595778.html

--------------

Thanks Henri and others.

I ran WINIPCFG.EXE (which for anyone else reading this, create a shortcut to
this and place it in your System Tools folder in your start menu)

Indeed my wireless card had an IP address beginning with 192. I released
that card then rebooted and viola!!!!! HP.com is now accessable!

If anyone else reads the page Henri pointed me to, they may notice they can
reach some of the pages that individual reported he couldn't access,
nevertheless, the tip still works.... simply release the IP address for
your network card and reboot, this should fix it.

Many thanks again Henri,

Dave