cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot get to home PC (which is on Plusnet)

N/A

Cannot get to home PC (which is on Plusnet)

Hi there

I usually connect to my home PC which is on Plusnet but I can't today since around 8-9am.

The router doesn't respond to ping so couldn't test that. Tracert from our leased line here (Onyx) results as follows:

traceroute to murton.plus.com (84.92.100.135), 64 hops max, 40 byte packets
1 195.97.249.29 (195.97.249.29) 0.759 ms 0.768 ms 0.628 ms
2 195.97.199.29 (195.97.199.29) 1.978 ms 1.813 ms 2.083 ms
3 s3-1.cr01.thlon.onyx.net (194.176.70.213) 20.124 ms 21.107 ms 31.430 ms
4 ge0-3.pbr01.thlon.onyx.net (194.176.73.119) 20.328 ms 21.909 ms 21.111 ms

and dies there.

Traceroute from Demon connection as follows:

Tracing route to murton.plus.com [84.92.100.135]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms demon-gw.ncfe.org.uk [62.49.171.217]
2 31 ms 31 ms 47 ms anchor-hg-1-l100.router.demon.net [194.159.161.32]
3 32 ms 31 ms 47 ms anchor-access-4-v155.router.demon.net [194.159.161.161]
4 31 ms 47 ms 31 ms anchor-inside-2-g7-0-0.router.demon.net [194.159.161.90]
5 31 ms 47 ms 31 ms tele-border-1-g1-0-0.router.demon.net [194.70.98.174]

and it dies there

Traceroute from BT Business SDSL connection as follows:

Tracing route to murton.plus.com [84.92.100.135]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms deadsea.citygate.local [192.168.128.254]
2 <1 ms <1 ms <1 ms host217-36-38-14.in-addr.btopenworld.com [217.36.38.14]
3 14 ms 16 ms 16 ms btdhg516-hg3.ealing.broadband.bt.net [217.47.49.202]
4 15 ms 14 ms 14 ms 217.47.49.129
5 15 ms 17 ms 15 ms 217.47.49.234
6 15 ms 15 ms 15 ms 217.47.219.98
7 53 ms 58 ms 66 ms 217.41.168.25
8 17 ms 16 ms 17 ms 217.41.168.66
9 16 ms 16 ms 16 ms 217.41.168.118
10 15 ms 14 ms 16 ms 217.41.168.38
11 15 ms 17 ms 15 ms 213.120.192.50
12 16 ms 16 ms 15 ms core1-pos6-1.ealing.ukcore.bt.net [194.72.9.205]
13 16 ms 15 ms 16 ms core1-pos4-0.telehouse.ukcore.bt.net [194.74.65.113]

and it times out there.

Does anyone know why this might be happening? Should I be raising a ticket?

Also if any of you guys could try from within PN's network and see what results you get that would be great.
7 REPLIES
N/A

Cannot get to home PC (which is on Plusnet)

Hi,

I can connect back to my Home PC ( which is on Plusnet ) from work no problems.

When I tracert I get as far as before it dies

gi9-0-403.pte-ag1.plus.net [84.92.4.3]

but that is probably because my router does not respond to pings.

Cheers

Neil
N/A

Cannot get to home PC (which is on Plusnet)

Trace below. I also did a trace to another account and whilst that router does not respond to pings, it shows what the route should be.

Yours isnt getting that far.


C:\Documents and Settings\mark.PCSNI>tracert murton.plus.com

Tracing route to murton.plus.com [84.92.100.135]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms gc._msdcs.pcsni.local [192.168.0.1]
2 1 ms <1 ms <1 ms 10.0.0.2
3 29 ms 28 ms 26 ms lo0-plusnet.pte-ag1.plus.net [195.166.128.64]
4 * * * Request timed out.
5 * * * Request timed out.
6 * ^C
C:\Documents and Settings\mark.PCSNI>tracert murton.plus.com

Tracing route to murton.plus.com [84.92.100.135]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms gc._msdcs.pcsni.local [192.168.0.1]
2 <1 ms <1 ms <1 ms 10.0.0.2
3 31 ms 30 ms 28 ms lo0-plusnet.pte-ag1.plus.net [195.166.128.64]
4 * ^C
C:\Documents and Settings\mark.PCSNI>tracert embarkell.plus.com

Tracing route to embarkell.plus.com [84.92.105.129]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms gc._msdcs.pcsni.local [192.168.0.1]
2 1 ms <1 ms <1 ms 10.0.0.2
3 35 ms 32 ms 28 ms lo0-plusnet.pte-ag1.plus.net [195.166.128.64]
4 27 ms 27 ms 27 ms ge0-0-0-403.pte-gw1.plus.net [84.92.4.1]
5 28 ms 28 ms 28 ms ge0-0-0-22.ptn-gw1.plus.net [212.159.4.1]
6 30 ms 29 ms 30 ms gi13-0-113.ptn-ag1.plus.net [84.92.5.195]
7 * * * Request timed out.
8 ^C
C:\Documents and Settings\mark.PCSNI>
N/A

Cannot get to home PC (which is on Plusnet)

Other results:

DNS Lookup: murton.plus.com NS record
Generated by www.DNSstuff.com
How I am searching:
Searching for murton.plus.com NS record at e.root-servers.net [192.203.230.10]: Got referral to C.GTLD-SERVERS.NET. [took 113 ms]
Searching for murton.plus.com NS record at C.GTLD-SERVERS.NET. [192.26.92.30]: Got referral to ns1.plusnet.co.uk. [took 7 ms]
Searching for murton.plus.com NS record at ns1.plusnet.co.uk. [195.166.128.17]: Reports that no NS records exist. [took 83 ms]

Answer:
No NS records exist for murton.plus.com. [Neg TTL=8640 seconds]

Details:
ns1.plusnet.co.uk. (an authoritative nameserver for plus.com.) says that there are no NS records for murton.plus.com.
The E-mail address in charge of the plus.com. zone is: hostmaster@force9.net.

So should I be raising a ticket?
N/A

Cannot get to home PC (which is on Plusnet)

$ traceroute murton.plus.com
traceroute to murton.plus.com (84.92.100.135), 64 hops max, 44 byte packets
1 mttjocy.plus.com (212.159.54.242) 1.038 ms 0.526 ms 0.502 ms
2 lo0-plusnet.ptn-ag1.plus.net (195.166.128.123) 24.413 ms 25.461 ms 23.262 ms
3 * * *

Have you tried it using just the IP (84.92.100.135) just see what happerns there, does seam though that your traffic is being dropped before you even enter the plus.net network.
N/A

Cannot get to home PC (which is on Plusnet)

Yip. It seems to be stopping at one of the Junipers and not getting any further? Weird.
JonathanW
Grafter
Posts: 2,648
Registered: 02-10-2007

Cannot get to home PC (which is on Plusnet)

Looking at the traceroute output, it would appear that the connection isn't up right now. This is why its timing out at that particular hop.

So its possible that something has happened to your connection at home, though it might just be your router/modem that needs rebooting.
N/A

Cannot get to home PC (which is on Plusnet)

Thanks for that. I guess I'll have to wait until I get home. If there was a problem I was hoping to resolve it early so I can get an insane amount of WoW battlegrounds time.

Hopefully its just my router, and the house hasn't burned down or something.

EDIT: hmmm, since I wrote this reply, my router 'automagically' responds now.

Very strange. Maybe I had a power cut?