This is very strange.
About two weeks ago I reinstalled Windows 7 Pro x64 from scratch in order to properly support my new Ceton TV tuner card. All of my application software is now just about fully reinstalled as well, and everything's working fine. The new Windows 7 is very much "cleaner, leaner, and meaner" than the previous installed version which I'd used kind of like a "training bicycle" over the past 11 months. Much closer to "pure Microsoft" with no "foreign codec packs".
Ok, my current problem seems to be totally related to Windows 7's Windows Firewall. For some reason 4 out of 5 boots on this machine do NOT establish a network connection (the desktop PC is "wired" connected to the router). And then, almost randomly, maybe 1 time out of 5 I will get a network successfully established. No way of really predicting success or failure, but each failure causes me to re-boot and try again.
Obviously there are several programs that start up with Windows and that need to get out to the Internet, including my Sophos anti-virus (looking for updates), DynDNS (to maintain my hostname/IP address on the DynDNS site), and in particular a program named CLOCKWISE (which goes out to the Navy's web site to get an accurate time-of-day to set my PC's clock).
Now CLOCKWISE also puts out a "Big Ben" chime sound when it sets the clock, so I know if this program is working by whether or not I hear Big Ben. And of course, on those 4 out of 5 boots where network access is not established I hear no Big Ben, and know something is wrong. I then am forced to shut down and try it again... and eventually, usually, it finally works. Of course the next boot may again fail, but I try not to re-boot if I can.
Ok, yesterday I decided to look closer at Windows Firewall and its settings. I noticed that there was no entry defined for the CLOCKWISE program. I experimented by disabling Windows Firewall (both home/private and public) and shut down and re-booted, and this time CLOCKWISE had no problem getting out to the Internet at boot time and my machine had its network connection established flawlessly.
So, I added the CLOCKWISE program to Windows Firewall, and close examination revealed that it only set up an INBOUND rule. Didn't make a lot of sense to me, since I was really trying to let CLOCKWISE get out to the Internet and I thought that's what "add program" to Windows Firewall was for.
Anyway, I then also created a new OUTBOUND rule, allowing CLOCKWISE to get out. Shut down and re-boot, and magically CLOCKWISE starts perfectly and I have a network. So I thought I'd solved the problem.
Then, a while later when I had to re-boot again because of some other software I'd just installed, this time the re-boot hung again with no network established and no Big Ben from CLOCKWISE. On just the previous re-boot it worked just fine, but now on the second re-boot it failed again.
So I again turned off Windows Firewall, shut down and re-booted, and once again network comes up and Big Ben sounds from CLOCKWISE. I then turned on Windows Firewall, because I feel better with it on than off (even though I have an external router to also "protect me").
I've been playing with this, including turning Firewall off and then on again before shutting down, and then re-booting, and startup then works. But if I then just shut down and re-boot, almost always it will fail again.
I don't think this is tied to CLOCKWISE, but rather this program's audible indication that it worked or not just tips me off that Windows 7 and Windows Firewall itself has somehow prevented network access from starting correctly.
And, if I have Windows Firewall turned off at shutdown, then the re-boot will always work fine and network is established. This points directly at Windows Firewall as the likely culprit here.
Now, what makes this machine unusual, from the way Windows 7 and Windows Firewall previously worked? Well, there's lots more of TV tuner stuff now with the Ceton card, and there are lots of entries for TV stuff in Windows Firewall. I don't know that this is relevant, but it's certainly different than the way things were two weeks ago... when I NEVER had this boot/network problem.
Any thoughts or suggestions? Anything I should look at or change, or investigate as another likely culprit?
I really do want to fix this. I should be able to have Windows Firewall active and still be compatible with all of my application programs. And I don't want to always have to remember to first turn off Windows Firewall at shutdown/re-boot time, and then turn back on Windows Firewall after startup with the network already established.