Oddly enough, if I try to browse Google via one of their IP addresses while using a Google DNS address, the domain name comes up in the address bar, but still fails to do much of anything. Browsing my own site's IP address throws an error, but it does the same on my main system, so that's just the host. I can ping domains from DOS without issue, but in IE3, no go, even on HTML 1.0 sites. I had similar problems about 14 years ago, but at least back then, sites would actually load.

Linksys LNE2000T
PING works in DOS without issue.
Error in a DOS prompt within Windows, when attempting to ping any domain, is as follows:
DGN0209: Internal software error (NMDRV Tcp Driver Error)
(Pressing the print screen key, even when the prompt is windowed, causes the keyboard driver and Windows to crash)
Only changed the primary DNS to my router's IP right before taking this screenshot, as a test. No better results than using any other DNS addresses.

Goes without saying that research has returned nothing. Using Microsoft's TCP/IP pack from their own FTP server from forever ago. Network file transfers work, and as domain resolution works in pure DOS, I suspect something else is going on after Windows loads, but it's the middle of the night, and I have a day in hades awaiting me at work in the morning. Thanks in advance if anyone besides the poor bastiches in the nineties (who never got a response for their requests) has found the solution. I've probably just been up too long and am missing something obvious.