Bad IP address

27 Sep 2006 7:03 PM

Vkihyone

This problem started all of a sudden on the 20th, I would be playing a game
on the internet and all of a sudden I'd get an R0 (Recieving: 0) signal
meaning I was not getting any information back from the main servers. I
called the company that provides my cable access and they said it was prolly
something on my computer. After wiping the ENTIRE drive and restoring the
factory settings the problem still exsists. so I ran a network diagnostics
check and found this
- IPAddress = 70.37.172.101 (FAILED)
Pinging 70.37.172.101 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 70.37.172.101:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
I'm assuming that this is the cause of my problems, the question I have is
how do I go about getting a new IP?

27 Sep 2006 7:23 PM

Steve Winograd [MVP]

In article <97E26D8E-4DC2-4D4D-A743-775757BA5***@microsoft.com>,
Vkihyone <Vkihy***@discussions.microsoft.com> wrote:
Show quoteHide quote

>This problem started all of a sudden on the 20th, I would be playing a game
>on the internet and all of a sudden I'd get an R0 (Recieving: 0) signal
>meaning I was not getting any information back from the main servers. I
>called the company that provides my cable access and they said it was prolly
>something on my computer. After wiping the ENTIRE drive and restoring the
>factory settings the problem still exsists. so I ran a network diagnostics
>check and found this
> - IPAddress = 70.37.172.101 (FAILED)
>Pinging 70.37.172.101 with 32 bytes of data:
>Request timed out.
>Request timed out.
>Request timed out.
>Request timed out.
>Ping statistics for 70.37.172.101:
>Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
>I'm assuming that this is the cause of my problems, the question I have is
>how do I go about getting a new IP?

I doubt that the ping failure is related to the game problem, and I
don't think that getting a new IP address would make any difference.
I think that something else is causing the problem, but I don't have
enough information to say what.

That IP address belongs to Adelphia. If you're an Adelphia
subscriber, they might have assigned it to you.

In a typical home setup with a broadband router, the router's WAN
(Internet) interface gets the IP address, and you can configure the
router to respond or not to respond to ping requests.

With no broadband router, the computer's LAN connection gets the IP
address, and you can configure the computer's firewall to respond or
not to respond to ping requests.

28 Sep 2006 1:48 AM

Vkihyone

ok I've talked to the company that owns the network (not adelphia, they got
replaced by Time warner cable) and apparently my system uses a DHCP system
which from what they told me means that I have a changing IP adress. I tried
running the network diagnostics system with both the windows firewall and
norton firewall disabled. the IP passed, however despite this the game still
continues to get R0, I'm just hoping that whatevers going can be easily fixed
cause I'm getting tired of all this, (talk about user unfriendly)

28 Sep 2006 6:46 PM

Vkihyone

ok here's what the self diagnostics reported immediatly (sp?) following my
disconnect from the game

[00000001] NVIDIA nForce MCP Networking Controller (FAILED)
Caption = [00000001] NVIDIA nForce MCP Networking Controller
DatabasePath = %SystemRoot%\System32\drivers\etc
- DefaultIPGateway = 70.37.172.1(Same Subnet) (FAILED)
Pinging 70.37.172.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 70.37.172.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Description = NVIDIA nForce MCP Networking Controller - Packet Scheduler
Miniport
DHCPEnabled = TRUE
DHCPLeaseExpires = 6:34:20 AM 9/28/2006
DHCPLeaseObtained = 6:34:20 PM 9/27/2006
- DHCPServer = 68.233.249.135 (FAILED)
Pinging 68.233.249.135 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 68.233.249.135:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
DNSDomain = lmdaca.adelphia.net
DNSEnabledForWINSResolution = FALSE
DNSHostName = Mine
- DNSServerSearchOrder (FAILED)
+ 67.21.15.6 (FAILED)
Pinging 67.21.15.6 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 67.21.15.6:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
+ 67.21.15.22 (FAILED)
Pinging 67.21.15.22 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 67.21.15.22:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
GatewayCostMetric = 20
Index = 1
+ IPAddress = 70.37.172.101 (PASSED)
Pinging 70.37.172.101 with 32 bytes of data:
Reply from 70.37.172.101: bytes=32 time<1ms TTL=0
Reply from 70.37.172.101: bytes=32 time<1ms TTL=0
Reply from 70.37.172.101: bytes=32 time<1ms TTL=0
Reply from 70.37.172.101: bytes=32 time<1ms TTL=0
Ping statistics for 70.37.172.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
IPConnectionMetric = 20
IPEnabled = TRUE
IPFilterSecurityEnabled = FALSE
IPSecPermitIPProtocols = 0
IPSecPermitTCPPorts = 0
IPSecPermitUDPPorts = 0
IPSubnet = 255.255.254.0

now I have no clue what all of this means but I'm guessing that the (FAILED)
is a bad thing, any ideas on if this is a problem with my computer or if it's
a problem with the ISP?

28 Sep 2006 11:05 PM

Chuck

On Thu, 28 Sep 2006 11:46:02 -0700, Vkihyone
<Vkihy***@discussions.microsoft.com> wrote:

Show quoteHide quote

>ok here's what the self diagnostics reported immediatly (sp?) following my
>disconnect from the game
>
>[00000001] NVIDIA nForce MCP Networking Controller (FAILED)
> Caption = [00000001] NVIDIA nForce MCP Networking Controller
> DatabasePath = %SystemRoot%\System32\drivers\etc
>- DefaultIPGateway = 70.37.172.1(Same Subnet) (FAILED)
>Pinging 70.37.172.1 with 32 bytes of data:
>Request timed out.
>Request timed out.
>Request timed out.
>Request timed out.
>Ping statistics for 70.37.172.1:
>Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
> Description = NVIDIA nForce MCP Networking Controller - Packet Scheduler
>Miniport
> DHCPEnabled = TRUE
> DHCPLeaseExpires = 6:34:20 AM 9/28/2006
> DHCPLeaseObtained = 6:34:20 PM 9/27/2006
>- DHCPServer = 68.233.249.135 (FAILED)
>Pinging 68.233.249.135 with 32 bytes of data:
>Request timed out.
>Request timed out.
>Request timed out.
>Request timed out.
>Ping statistics for 68.233.249.135:
>Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
> DNSDomain = lmdaca.adelphia.net
> DNSEnabledForWINSResolution = FALSE
> DNSHostName = Mine
>- DNSServerSearchOrder (FAILED)
>+ 67.21.15.6 (FAILED)
>Pinging 67.21.15.6 with 32 bytes of data:
>Request timed out.
>Request timed out.
>Request timed out.
>Request timed out.
>Ping statistics for 67.21.15.6:
>Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
>+ 67.21.15.22 (FAILED)
>Pinging 67.21.15.22 with 32 bytes of data:
>Request timed out.
>Request timed out.
>Request timed out.
>Request timed out.
>Ping statistics for 67.21.15.22:
>Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
> GatewayCostMetric = 20
> Index = 1
>+ IPAddress = 70.37.172.101 (PASSED)
>Pinging 70.37.172.101 with 32 bytes of data:
>Reply from 70.37.172.101: bytes=32 time<1ms TTL=0
>Reply from 70.37.172.101: bytes=32 time<1ms TTL=0
>Reply from 70.37.172.101: bytes=32 time<1ms TTL=0
>Reply from 70.37.172.101: bytes=32 time<1ms TTL=0
>Ping statistics for 70.37.172.101:
>Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
>Approximate round trip times in milli-seconds:
>Minimum = 0ms, Maximum = 0ms, Average = 0ms
> IPConnectionMetric = 20
> IPEnabled = TRUE
> IPFilterSecurityEnabled = FALSE
> IPSecPermitIPProtocols = 0
> IPSecPermitTCPPorts = 0
> IPSecPermitUDPPorts = 0
> IPSubnet = 255.255.254.0
>
>now I have no clue what all of this means but I'm guessing that the (FAILED)
>is a bad thing, any ideas on if this is a problem with my computer or if it's
>a problem with the ISP?

Read about the nVidia nForce please, in particular the nForce customers
discussions.
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.