newuser30

New Member
Joined
Oct 13, 2014
Messages
1
hello, I have been having this issue for few days already that I noticed..
I have called my isp and everything no one can provide me resolve this I feel hopeless... I am using windows 8.1 64 bit pro, and the problem is also when I run Tracert to any Ip I get always this 0.0.0.0 address first!

example : tracert google.xxx

1 7 ms 9 ms 8 ms primeval [0.0.0.0]
2 11 ms 11 ms 11 ms 172.18.1.222
3 11 ms 11 ms 11 ms



Link Removed
Other Networking Configuration and Logs
File Name:
Collection information
Computer Name: PRIMEVAL
Windows Version:
6.3
Architecture:
x64
Time:
Tuesday, October 14, 2014 12:40:14 AM



here is the diagnostics report I get from my network adapter.
Details about network adapter diagnosis:
Network adapter Ethernet driver information:
Description . . . . . . . . . . : Intel(R) 82567V-2 Gigabit Network Connection
Manufacturer . . . . . . . . . : Intel
Provider . . . . . . . . . . . : Microsoft
Version . . . . . . . . . . . : 10.1.10.1
Inf File Name . . . . . . . . . : C:\Windows\INF\net1yx64.inf
Inf File Date . . . . . . . . . :
Section Name . . . . . . . . . : E10CD
Hardware ID . . . . . . . . . . : pci\ven_8086&dev_10ce
Instance Status Flags . . . . . : 0x180200a
Device Manager Status Code . . : 0
IfType . . . . . . . . . . . . : 6
Physical Media Type . . . . . . : 0

Network Diagnostics Log


Other Networking Configuration and Logs
File Name:
Collection information

Windows IP Configuration
Host Name . . . . . . . . . . . . : primeval
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82567V-2 Gigabit Network Connection
Physical Address. . . . . . . . . : 20-CF-30-2E-08-8B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 149.78.113.74(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Lease Obtained. . . . . . . . . . : ‰…™‰ 13 €…—ˆ…˜ 2014 23:45:16
Lease Expires . . . . . . . . . . : ‰…˜‰’‰ 15 €…—ˆ…˜ 2014 00:26:04
Default Gateway . . . . . . . . . : 149.78.112.1
DHCP Server . . . . . . . . . . . : 172.18.178.195
DNS Servers . . . . . . . . . . . : 213.57.22.5
213.57.2.5
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{06565549-6FBF-46AF-B14B-69C081EB053C}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter 6TO4 Adapter:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:954e:714a::954e:714a(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 134217728
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-CD-55-7F-20-CF-30-2E-08-8B
DNS Servers . . . . . . . . . . . : 213.57.22.5
213.57.2.5
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:186b:f7ff:2ac6:ecd5(Preferred)
Link-local IPv6 Address . . . . . : fe80::186b:f7ff:2ac6:ecd5%6(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 150994944
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-CD-55-7F-20-CF-30-2E-08-8B
NetBIOS over Tcpip. . . . . . . . : Disabled
 

Solution
It looks like you're encountering an unusual issue with your network configuration on Windows 8.1 where the first hop in your traceroute (tracert) command shows an IP address of 0.0.0.0. This can indicate that your computer isn't properly routing the initial packets, which leads to a few different possibilities. Let's investigate and troubleshoot step by step.

Troubleshooting Steps​

Here are several steps you can try to resolve the issue:

1. Check Network Connections

Ensure that your network cable is properly connected, or if you're using Wi-Fi, confirm that you're connected to the correct network.

2. Release and Renew IP Address

You can reset your IP configuration using the Command Prompt...
It looks like you're encountering an unusual issue with your network configuration on Windows 8.1 where the first hop in your traceroute (tracert) command shows an IP address of 0.0.0.0. This can indicate that your computer isn't properly routing the initial packets, which leads to a few different possibilities. Let's investigate and troubleshoot step by step.

Troubleshooting Steps​

Here are several steps you can try to resolve the issue:

1. Check Network Connections

Ensure that your network cable is properly connected, or if you're using Wi-Fi, confirm that you're connected to the correct network.

2. Release and Renew IP Address

You can reset your IP configuration using the Command Prompt:
  1. Open Command Prompt with admin rights. (Search for "cmd" in the start menu, right-click and select "Run as administrator")
  2. Execute the following commands one by one:
    Code:
     ipconfig /release ipconfig /renew

    3. Reset TCP/IP Stack

    You may want to reset your TCP/IP stack to its default settings:
  3. In the Command Prompt (admin), run:
    Code:
     netsh int ip reset
  4. Restart your computer.

    4. Check for Software Conflicts

    Sometimes, third-party software (especially firewall or VPN applications) can interfere with your network configuration. Temporarily disable these applications to see if the issue persists.

    5. Update Network Drivers

    Make sure your network driver is up to date. Here’s how:
  5. Open Device Manager (right-click on the start menu and select it).
  6. Expand the Network adapters section.
  7. Right-click on your adapter (Intel(R) 82567V-2 Gigabit Network Connection) and select Update driver.

    6. Check Default Gateway

    From your diagnostics report, the default gateway is 149.78.112.1. Ensure this is reachable by pinging it:
    Code:
    ping 149.78.112.1
    If there’s no response, check if the gateway itself is configured correctly.

    7. Modify the MTU Size

    Sometimes, the Maximum Transmission Unit (MTU) setting can influence your connection. You can adjust the MTU size using:
  8. In Command Prompt (admin), type:
    Code:
     netsh interface ipv4 set subinterface "Ethernet" mtu=1472 store=persistent
    (Replace “Ethernet” with the appropriate name of your connection if it’s different)

    8. Firewall/Antivirus Settings

    Check your Windows Firewall or third-party antivirus settings to ensure they're not blocking your connection.

    Conclusion​

    If you've followed these steps and your problem persists, it may indicate a deeper issue related to your ISP or network hardware (like a faulty router). If possible, try connecting a different device to your network to see if the problem replicates. You can also contact your ISP again, providing them with the specific information about your traceroute outputs and troubleshooting steps you've taken. Sometimes, even if they can't see a problem on their end, additional diagnostics on their part might be required. If you continue to experience issues or receive messages like 0.0.0.0, feel free to update, and we can explore further. Keep your spirits up! Computers can sometimes be cranky, but with a bit of sleuthing we can typically get them back on track!
 

Solution
Back
Top