I have this few-minutes-after-Windows-started-then-browsing-http-fails problem. Hope that long name summarises the problem: browsing works initially for a few minutes after Windows started, then fails. Afterwards, browsing to https still works, POP email works, Ping works on both www.xxx.com and numeric IP address forms. So it's a destination port 80 problem, and not a DNS problem. And no proxy - as far as I am aware. This problem occurred on two separate occasions, under different setups. Should offer some contrast to eliminate possible culprits: First setup (Oct 2005) - 1.1. Cable broadband, with cable modem and separate Belkin wireless router. Win98 desktop PC on wired Ethernet connection. 1.2. Zonealarm (free version) autostarted. No problem browsing. 1.3. Replaced ZA with other firewalls such as Kerio and Tiny. Got browsing problem. 1.4. Went back to using ZA. Second setup (recent) - 2.1. ADSL (UK) broadband, D-Link DSL wireless modem-router. Win98 desktop PC on wired Ethernet connection. 2.2. (same as 1.2, with latest ZA free version for Win98) 2.3. (same as 1.3, but with Kerio only) 2.4. Exited Kerio (so then no software firewall running), didn't help. 2.5. Tried IPCONFG Release/Renew, didn't work. Now, with no software firewall being auto-/manually run, browsing problem is as described. So it's not the software firewall (ZA or Kerio). Nor is it Cable/DSL, nor(?) the router. And nothing to do with wireless. I then started ZA manually. *** Browsing problem gone! *** Even after I exited ZA, and with or without starting Kerio, browsing still continues working. The question is, why should just briefly running ZA resolve the browsing problem (contrary to other people's problem with ZA)? Does ZA alter my networking config when it runs? Does it leave something running even after exiting - I couldn't find anything related using various process viewers.

This is definately an odd, and interesting, problem. Once resolved, I'd like to find out what the issue was and how it was resolved. Ping works on both www.xxx.com and numeric IP address forms. So it's a destination port 80 problem, and not a DNS problem. It's nice that you're sure but just because you can ping by hostname as well as IP isn't a guarantee it's not a DNS issue. As for it not being a port 80 destination problem, you're doing this in a command prompt window I assume? If so, keep in mind that the data is not going to port 80 in that case. To make sure, the next time this happens open a command prompt window. Do the following two commands and then try pinging a few different sites by their hostname: arp -d * ipconfig /flushdns If after doing those two commands you can't ping by hostname, then it's likely it's a DNS issue. If that makes no difference then check to see if you have the windows firewall on and set to block port 80. The only reason I can see for ZA to fix the problem is that it's properly forwarding port 80 traffic whereas something in your setup is blocking it. What is so odd is that it works for a while then stops. You might try uninstalling your TCP/IP stack and then reinstalling it (with a reboot in between). The problem may be in your TCP/IP stack itself. If it is, this would likely resolve the issue if that is indeed the case. Remember, get back to us and let us know if any of this helped or not.

Hi Curt, I based my conclusion that it's not a DNS problem on the fact that browsing https still works. Still, will try your suggestion with arp and flushdns and get back to you. Does uninstalling TCP/IP stack means deleting all TCP/IP entries in Networking?

You can't delete TCP/IP from Windows 2003. "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

Hi Curt, I have tried the DOS cmds you suggested in a cmd prompt window on my *Win98* PC - "arp -d *" wasn't accepted, it didn't like the "*", nor www.google.com or the numeric form. "ipconfig /flushdns" - /flushdns is not a valid argument to Win98 ipconfig. I have thought of using Ethereal to track down the problem, when I have oodles of time on hand.

Use winipcfg on Windows 9X machines instead. "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

Hi heropsycho2177, Winipcfg didn't like /flushdns either.