HTTP error 12031

  • Thread starter Thread starter Sailing_Nut
  • Start date Start date
S

Sailing_Nut

Hi,

I'm having problems with an XP install. I have found that I can't get to web
pages. When I run the "Diagnose Connection Problems" it shows that FTP and
HTTPS are OK, but HTTP traffic gets two errors, 12030 and 12031.

I have verified that I can resolve names using DNS and that I can reach
sites using ping and tracert.

I beileve that the problem might have to do with a failed firewall unistall,
but I don't know how to go abour reparing the TCP/IP stack to wipe out any
previous firewall installs. I have already cleaned out a failed Norton
install, but there is a black ice install that I can find out how to kill. In
an attempt to get black ice out of the equation I disabled the service but
I'm still seeing my problem with HTTP traffic.

Any help is greatly appreciated.

Thanks in advance!
 
Sailing_Nut said:
Hi,

I'm having problems with an XP install. I have found that I can't get to web
pages. When I run the "Diagnose Connection Problems" it shows that FTP and
HTTPS are OK, but HTTP traffic gets two errors, 12030 and 12031.

I have verified that I can resolve names using DNS and that I can reach
sites using ping and tracert.

I beileve that the problem might have to do with a failed firewall unistall,
but I don't know how to go abour reparing the TCP/IP stack to wipe out any
previous firewall installs. I have already cleaned out a failed Norton
install, but there is a black ice install that I can find out how to kill. In
an attempt to get black ice out of the equation I disabled the service but
I'm still seeing my problem with HTTP traffic.

Any help is greatly appreciated.

Thanks in advance!
Click to expand...
 
In Windows XP, a reset command is available in the IP context of the NetShell
utility. Follow these steps to use the reset command to reset TCP/IP manually:
1. To open a command prompt, click Start and then click Run. Copy and paste
(or type) the following command in the Open box and then press ENTER:
cmd
2. At the command prompt, copy and paste (or type) the following command and
then press ENTER:
netsh int ip reset c:\resetlog.txt
Note If you do not want to specify a directory path for the log file, use
the following command:
netsh int ip reset resetlog.txt
When you run the reset command, it rewrites two registry keys that are used
by TCP/IP. This has the same result as removing and reinstalling the
protocol. The reset command rewrites the following two registry keys:

SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
SYSTEM\CurrentControlSet\Services\DHCP\Parameters\


To run the manual command successfully, you must specify a file name for the
log, in which the actions that netsh takes will be recorded. When you run the
manual command, TCP/IP is reset and the actions that were taken are recorded
in the log file, known as resetlog.txt in this article.

The first example, c:\resetlog.txt, creates a path where the log will
reside. The second example, resetlog.txt, creates the log file in the current
directory. In either case, if the specified log file already exists, the new
log will be appended to the end of the existing file.
 
Unfortunately that did not resolve my problem. It would appear that I still
have some junk leftover from a irewall that the reset command did not knock
out.

Do you have any other suggestions or advice on how to further troubleshoot
this?
 
The LSPfix did not find anything wrong, but WinsockXPFix did make some changes.

After running both I rebooted and still had the same problem. I then ran the
diagnostic in WIndows and it stated that Winsock was damaged and needed to be
repaired. After doing that and rebooting, I now have more errors.

I still have the problem with not being able to make an HTTP connection but
I also have the following:

Error attempting to validate the Winsock base providers: 2

Not all base service provider entries could be found in the Winsock catalog.
A reset is needed
 
Back
Top