New member. First forum reply. Lots of rules to abide by.
I had this exact problem, although in my home environment. I realize this is not a forum for home users but this thread was found during a search for the identical symptom (i.e. 0.0.0.0 along with 192.168.1.1 as the gateway), although in my case the symptom always occurred at Windows boot time when networking was just getting started.
Until today, my own solution was to do a DISABLE and then and ENABLE for the ethernet LAN adapter in Network Connections. That always worked and the extraneous 0.0.0.0 network disappeared, and 100% normal Internet access resulted, but I had to do it every time I booted the laptop. Quite annoying.
So, although I'm not a systems administrator but simply a home user, I joined this forum today to be able to thank Jason Berg for his super-basic and super-simple "pull the plug, wait 30-seconds, plug it back in. Did the problem go away? Great. Case closed." suggestion posted earlier, which actually DID WORK for me to solve my own problem!!!
Reset winsock. Reset TCP/IP. Reboot computer.
netsh winsock reset c:\winsock.log
netsh int ip reset c:\ipreset.log
Sure enough, when my system was rebooted the symptom had completely disappeared. I only saw the one valid ethernet LAN network path to my router, and I immediately had Internet access. Since this had been failing for a year (yes, that's how long I've been booting followed by DISABLE/ENABLE) I couldn't believe that it could be fixed simply by deleting and recreating the TCP/IP stack.
So I retried the reboot three times. And each one was again successful... only the 192.168.1.1 gateway, and instant Internet access working perfectly.
Therefore, again my thanks go out to Jason Berg for his suggestion.
Worked for me.