Default gateway not available?

[harshbarj]

Ok, bit of an odd problem I hope someone here can suggest a fix.

2 days ago my primary gaming rig started having network issues. It will show a yellow triangle over the network icon in the system tray. I pull up the network and sharing center and it indicates the problem is between my computer and the network. I click the yellow triangle over the line between the two and it automatically tries to fix the problem, and does. It says the "Default gateway not available" So far disabling and re-enabling the network adapter has been the only thing that has fixed the issue. No other computer on the network is having an issue and runs fine. I have tried unplugging the network cable and plunging it back in to no avail.

I updated the driver to the latest realtek driver. nothing.
I tried reverting to the default ms driver, nothing.


My system.
Core I5 750
Gigabyte p55a-ud3 motherboard.
8gb pc3-12800 patriot memory (2x4gb)
ATI HD5770
Windows 7 home premium 64-bit

Dhcp is enabled and the gateway should be 192.168.0.1 and is when the problem occurs. Nothing I see says there is a problem. I have scanned the computer for malware and it was clean.

Connection-specific DNS Suffix: om.cox.net
Description: Realtek PCIe GBE Family Controller
Physical Address: XXXXXXXXXXXXXXXXX
DHCP Enabled: Yes
IPv4 Address: 192.168.0.100
IPv4 Subnet Mask: 255.255.255.0
Lease Obtained: Tuesday, March 11, 2014 10:28:02 PM
Lease Expires: Wednesday, March 12, 2014 10:28:02 PM
IPv4 Default Gateway: 192.168.0.1
IPv4 DHCP Server: 192.168.0.1
IPv4 DNS Server: 192.168.0.1
IPv4 WINS Server:
NetBIOS over Tcpip Enabled: Yes
Link-local IPv6 Address: fe80::e468:7094:4293:eea0%15
IPv6 Default Gateway:
IPv6 DNS Server:


hope this helps.

 

[kevnich2]

Try doing this:
1. Click start, in search box type in "cmd" then right click on the command prompt and choose run as administrator.
2. When the black box appears, type this in: netsh int ip reset and hit enter
3. Restart your computer and see if that fixes it.

 

[harshbarj]

Try doing this:
1. Click start, in search box type in "cmd" then right click on the command prompt and choose run as administrator.
2. When the black box appears, type this in: netsh int ip reset and hit enter
3. Restart your computer and see if that fixes it.

I'm at work now, but will try that when I get home tonight.

Googleing your command I got this list of things to do to nuke your network settings. So I may give this a go too.


Go to the Start Menu, type cmd and right click, and select "Run As Administrator"
Type the following commands, each followed by pressing enter.

ipconfig /flushdns
nbtstat -R
nbtstat -RR
netsh int reset all
netsh int ipv4 reset
netsh int ipv6 reset
netsh winsock reset

Pasting everything just to help others in case this works.

 

[harshbarj]

OK, I tried the all out network nuke and had one issue. The "netsh int reset all" you originally asked me to run will not work. It simply says "the following command was not found: int reset all.

I am running the command prompt as admin and I tried this multiple times to rule out a typo. I even copied and pasted. Same results. I'll have to see if perhaps one of the other commands might have fixed it.

 

[azazel1024]

Win 7 removed the command. Try "netsh int ip reset" along with the winsock reset.

 

[kevnich2]

OK, I tried the all out network nuke and had one issue. The "netsh int reset all" you originally asked me to run will not work. It simply says "the following command was not found: int reset all.

I am running the command prompt as admin and I tried this multiple times to rule out a typo. I even copied and pasted. Same results. I'll have to see if perhaps one of the other commands might have fixed it.

Well I didn't say to type in "netsh int reset all". If you look at my post, the command was to run: "netsh int ip reset" You left out the ip portion of the command

 

[harshbarj]

Interestingly the commands that worked seemed to fix the problem. Day 2 with no network problems.

And yes, I did overlook the differences between the two commands. Easy to do with two similar commands.

Thanks though, without that I would have never found that page.