ip address fails !!!!!!!!!!

[Juddski]

hi i have a log of faults why would a 10. ip add fail what is a 10 ip add thanks :t

[BipolarBill]

A 10.36.xxx.xxx IP is a private address. You cannot access a private address from the internet.

[Juddski]

Topic: BROADBAND FAULT!!!! NEED ANWSERS PLEASE!, NTL NO HELP WHAT SO EVER !!!PLEASE HELP


Hi all i realy need some help ive got N T L BROADBAND UK, had it 4 4 weeks now ringing them up!!! every day i like gaming, and when ever i host a game it bombs out throwing my tv pictures,and interativge service i have spoken to tec suport and they say it sould not drop a 10 ip address what does this meen ? please as im getting no help from them ive down a test using corect conect the software that comes with install disk and these are the rusults what do these faults meen please im not a tec but something is not right any help would be better than what ntl have done 4 me thanks juddski

ive done tracert 10.36.224.1 and all i get is time out how can this be when in TEST (atachment) it has conected is it somthing to do with settop box ive had 3, I HAVE A 512 CONNECTION.

Trace route result: Hop: 7, IP: 62.253.162.50, Time = 9ms, Status = HOP_SUCCESS.
Ping failure: Count: 0, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 1, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 2, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 3, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 4, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 5, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 6, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 7, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 8, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 9, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping result: Count: 0, IP: 80.1.170.161, Time = 33ms.
Ping result: Count: 9, IP: 62.253.162.50, Time = 13ms.
Analysis: IP: 10.36.224.1, Avg Ping: 0, Packet Loss: 100%.
Analysis: IP: 80.1.170.161, Avg Ping: 15, Packet Loss: 0%.
Analysis: IP: 62.255.81.141, Avg Ping: 20, Packet Loss: 0%.
Ping result: Count: 9, IP: 62.253.162.50, Time = 13ms.
Test Performed
Results
Diagnosis Recommendation Connectivity Target Host Slow response from gateway server. Try again later.
Connectivity Target Host Trace route result: Hop: 0, IP: 10.36.224.1, Time = 88ms, Status = HOP_NEXT_HOP.
Trace route result: Hop: 7, IP: 62.253.162.50, Time = 131ms, Status = HOP_SUCCESS.
Ping result: Count: 0, IP: 10.36.224.1, Time = 75ms.
Ping result: Count: 1, IP: 10.36.224.1, Time = 70ms.
Ping result: Count: 2, IP: 10.36.224.1, Time = 91ms.
Ping result: Count: 3, IP: 10.36.224.1, Time = 106ms.
Ping result: Count: 4, IP: 10.36.224.1, Time = 97ms.
Ping result: Count: 5, IP: 10.36.224.1, Time = 105ms.
Ping result: Count: 6, IP: 10.36.224.1, Time = 127ms.
Ping result: Count: 7, IP: 10.36.224.1, Time = 137ms.
Ping result: Count: 8, IP: 10.36.224.1, Time = 131m


COME ON U TECS U LOVE A CHALANGE!!!!!!

REPLEY
A 10.36.xxx.xxx IP is a private address. You cannot access a private address from the internet

[BipolarBill]

Please stop spamming the board and just tell us the problem in English and without all the fireworks.

[bushmaster]

Want's ya ta help him get someplace he shouldnt be

[DVNT1]

Originally posted by BipolarBill
A 10.36.xxx.xxx IP is a private address. You cannot access a private address from the internet. More specifically, most Internet routers are (should be) setup so they do not service the private IP address ranges...

Class A private network range: 10.0.0.0 - 10.255.255.255
Class B Private network range: 172.16.0.0 - 172.31.255.255
Class C private network range: 192.168.0.0 - 192.168.255.255

[BipolarBill]

Thanks and welcome back, DVNT1. :t

[Juddski]

thanks DVNT1

im getting this fault all the time! its a 10 ip this is why its failing?

Trace route result: Hop: 7, IP: 62.253.162.50, Time = 9ms, Status = HOP_SUCCESS.
Ping failure: Count: 0, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 1, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 2, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 3, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 4, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 5, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 6, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 7, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 8, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 9, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping result: Count: 0, IP: 80.1.170.161, Time = 33ms.
Ping result: Count: 9, IP: 62.253.162.50, Time = 13ms.
Analysis: IP: 10.36.224.1, Avg Ping: 0, Packet Loss: 100%.
Analysis: IP: 80.1.170.161, Avg Ping: 15, Packet Loss: 0%.
Analysis: IP: 62.255.81.141, Avg Ping: 20, Packet Loss: 0%.
says i have good internet connection

[BipolarBill]

Who's PC is that? Is it a printer? Unless it's on your LAN, you won't be able to reach it. If it's a PC on your LAN and it's using a firewall program, the same applies.

[Juddski]

im using no firewall this is the problem ive been getting since day 1 im using a program called correct connect! it comes with ntls install disk monitors conection if i go in to a test it says good connection but all the time its logging 100% packet loss and ip time out as u can see from above i keep loosing a stable connection i sopke to ntl tec and she said ( it should not be failing on a 10 ip) and this is a tv interative fault! please i need something to tell them as it sounds like they have got a book in front of them.

[BipolarBill]

I'll say it again...if that 10.xxx.xxx.xxx IP is not on your LAN, you can't ping it. Since you can't ping it, you're wasting your time.

What PC or node are you trying to ping? Who is 10.36.224.1?

I would dump that software and use Windows networking.

[DVNT1]

Originally posted by BipolarBill
I'll say it again...if that 10.xxx.xxx.xxx IP is not on your LAN, you can't ping it. Since you can't ping it, you're wasting your time... yes, by continually trying the IP when it isn't a subnet on your network you're basically just doing just like BipolarBill's avatar. :)

[Juddski]

I DONT KNOW WHOS IP THIS IS MUST BE NTL AS IT LOGGING IT ALL THE TIME AS SOON AS I CONNECT THE USB!!!! WHY IS IT LOGGING THIS IP THIS IS TODAYS TEST AT 16:26 UK TIME 14/7/



Connection Test: Advanced


Test Performed Results Log
Connectivity Target Host Trace route result: Hop: 0, IP: 10.36.224.1, Time = 116ms, Status = HOP_NEXT_HOP.
Trace route result: Hop: 1, IP: 80.1.170.161, Time = 128ms, Status = HOP_NEXT_HOP.
Trace route result: Hop: 2, IP: 62.255.81.141, Time = 52ms, Status = HOP_NEXT_HOP.
Trace route result: Hop: 3, IP: 62.253.185.69, Time = 127ms, Status = HOP_NEXT_HOP.
Trace route result: Hop: 4, IP: 213.105.172.78, Time = 122ms, Status = HOP_NEXT_HOP.
Trace route result: Hop: 5, IP: 62.253.185.202, Time = 66ms, Status = HOP_NEXT_HOP.
Trace route result: Hop: 6, IP: 62.253.188.166, Time = 47ms, Status = HOP_NEXT_HOP.
Trace route result: Hop: 7, IP: 62.253.162.50, Time = 93ms, Status = HOP_SUCCESS.
Ping failure: Count: 0, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 1, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 2, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 3, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 4, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 5, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 6, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 7, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 8, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping failure: Count: 9, IP: 10.36.224.1, ERROR = ICMP_TIMEOUT.
Ping result: Count: 0, IP: 80.1.170.161, Time = 59ms.
Ping result: Count: 1, IP: 80.1.170.161, Time = 46ms.
Ping result: Count: 2, IP: 80.1.170.161, Time = 77ms.
Ping result: Count: 3, IP: 80.1.170.161, Time = 91ms.
Ping result: Count: 4, IP: 80.1.170.161, Time = 66ms.
Ping result: Count: 5, IP: 80.1.170.161, Time = 27ms.
Ping result: Count: 6, IP: 80.1.170.161, Time = 46ms.
Ping result: Count: 7, IP: 80.1.170.161, Time = 23ms.
Ping result: Count: 8, IP: 80.1.170.161, Time = 132ms.
Ping result: Count: 9, IP: 80.1.170.161, Time = 162ms.
Ping result: Count: 0, IP: 62.255.81.141, Time = 79ms.
Ping result: Count: 1, IP: 62.255.81.141, Time = 43ms.
Ping result: Count: 2, IP: 62.255.81.141, Time = 96ms.
Ping result: Count: 3, IP: 62.255.81.141, Time = 45ms.
Ping result: Count: 4, IP: 62.255.81.141, Time = 78ms.
Ping result: Count: 5, IP: 62.255.81.141, Time = 120ms.
Ping result: Count: 6, IP: 62.255.81.141, Time = 96ms.
Ping result: Count: 7, IP: 62.255.81.141, Time = 112ms.
Ping result: Count: 8, IP: 62.255.81.141, Time = 128ms.
Ping result: Count: 9, IP: 62.255.81.141, Time = 74ms.
Ping result: Count: 0, IP: 62.253.185.69, Time = 117ms.
Ping result: Count: 1, IP: 62.253.185.69, Time = 96ms.
Ping result: Count: 2, IP: 62.253.185.69, Time = 132ms.
Ping result: Count: 3, IP: 62.253.185.69, Time = 93ms.
Ping result: Count: 4, IP: 62.253.185.69, Time = 79ms.
Ping result: Count: 5, IP: 62.253.185.69, Time = 87ms.
Ping result: Count: 6, IP: 62.253.185.69, Time = 119ms.
Ping result: Count: 7, IP: 62.253.185.69, Time = 129ms.
Ping result: Count: 8, IP: 62.253.185.69, Time = 56ms.
Ping result: Count: 9, IP: 62.253.185.69, Time = 49ms.
Ping result: Count: 0, IP: 213.105.172.78, Time = 57ms.
Ping result: Count: 1, IP: 213.105.172.78, Time = 66ms.
Ping result: Count: 2, IP: 213.105.172.78, Time = 47ms.
Ping result: Count: 3, IP: 213.105.172.78, Time = 72ms.
Ping result: Count: 4, IP: 213.105.172.78, Time = 64ms.
Ping result: Count: 5, IP: 213.105.172.78, Time = 108ms.
Ping result: Count: 6, IP: 213.105.172.78, Time = 14ms.
Ping result: Count: 7, IP: 213.105.172.78, Time = 61ms.
Ping result: Count: 8, IP: 213.105.172.78, Time = 131ms.
Ping failure: Count: 9, IP: 213.105.172.78, ERROR = ICMP_TIMEOUT.
Ping result: Count: 0, IP: 62.253.185.202, Time = 116ms.
Ping result: Count: 1, IP: 62.253.185.202, Time = 126ms.
Ping result: Count: 2, IP: 62.253.185.202, Time = 84ms.
Ping result: Count: 3, IP: 62.253.185.202, Time = 112ms.
Ping result: Count: 4, IP: 62.253.185.202, Time = 120ms.
Ping result: Count: 5, IP: 62.253.185.202, Time = 21ms.
Ping result: Count: 6, IP: 62.253.185.202, Time = 35ms.
Ping result: Count: 7, IP: 62.253.185.202, Time = 111ms.
Ping result: Count: 8, IP: 62.253.185.202, Time = 122ms.
Ping result: Count: 9, IP: 62.253.185.202, Time = 120ms.
Ping result: Count: 0, IP: 62.253.188.166, Time = 102ms.
Ping result: Count: 1, IP: 62.253.188.166, Time = 61ms.
Ping result: Count: 2, IP: 62.253.188.166, Time = 95ms.
Ping result: Count: 3, IP: 62.253.188.166, Time = 83ms.
Ping result: Count: 4, IP: 62.253.188.166, Time = 70ms.
Ping result: Count: 5, IP: 62.253.188.166, Time = 117ms.
Ping result: Count: 6, IP: 62.253.188.166, Time = 109ms.
Ping result: Count: 7, IP: 62.253.188.166, Time = 94ms.
Ping result: Count: 8, IP: 62.253.188.166, Time = 125ms.
Ping result: Count: 9, IP: 62.253.188.166, Time = 75ms.
Ping result: Count: 0, IP: 62.253.162.50, Time = 67ms.
Ping result: Count: 1, IP: 62.253.162.50, Time = 128ms.
Ping result: Count: 2, IP: 62.253.162.50, Time = 73ms.
Ping result: Count: 3, IP: 62.253.162.50, Time = 69ms.
Ping result: Count: 4, IP: 62.253.162.50, Time = 39ms.
Ping result: Count: 5, IP: 62.253.162.50, Time = 21ms.
Ping result: Count: 6, IP: 62.253.162.50, Time = 27ms.
Ping result: Count: 7, IP: 62.253.162.50, Time = 147ms.
Ping result: Count: 8, IP: 62.253.162.50, Time = 94ms.
Ping result: Count: 9, IP: 62.253.162.50, Time = 120ms.
Analysis: IP: 10.36.224.1, Avg Ping: 0, Packet Loss: 100%.
Analysis: IP: 80.1.170.161, Avg Ping: 72, Packet Loss: 0%.
Analysis: IP: 62.255.81.141, Avg Ping: 87, Packet Loss: 0%.
Analysis: IP: 62.253.185.69, Avg Ping: 95, Packet Loss: 0%.
Analysis: IP: 213.105.172.78, Avg Ping: 68, Packet Loss: 10%.
Analysis: IP: 62.253.185.202, Avg Ping: 96, Packet Loss: 0%.
Analysis: IP: 62.253.188.166, Avg Ping: 93, Packet Loss: 0%.
Analysis: IP: 62.253.162.50, Avg Ping: 78, Packet Loss: 0%.
Analysis: your ISP: 96, Border Gateway: 0, Internet: 0.


IM NOT TRYING TO CONNECT TO THIS BUT MY PC MUST BE TRYING TO??????????

[BipolarBill]

I'm closing this thread after this post, Juddski. You love your capital letters, but you don't tell us where that log is from or why you consider this to be a problem.

If that log is from your ISP's software, it's just a test ping to known nodes. If the ping software or batch file was created on a LAN, they probably used a node on their LAN to test, but never removed that ping from the script. It's a non-issue. So is this entire thread.