Can't get past router to access the internet

[#1]

For a good 18- 24 months I have had some Edimax power plugs. I have the main one, one on the Sky box and one on the PC in the conservatory. They were pretty much plug and play and worked faultlessly until recently. I find now that my connection to the 'net from my desktop pc (Win 8.1) effectively seems to go to sleep. If I restart the pc, I get a connection for a few minutes, then it stops. If I turn off the power plug and back on, it allows me online for a few minutes. if I reboot the router, it allows me on for a few minutes. I can access the router interface from this pc, but cannot get any further. Traceroutes show as timed out.  If I turn off Comodo, it has no effect, so it seems the router is stopping the pc from accessing the web, but why?
I even disconnected the ethernet and installed a usb wireless stick , which I thought had cured the issue, but today is suffering the same as if it was wired. I have a spare power plug and tried that, but that has the same problem.
I haven't changed any settings recently. The only thing that has changed since it last worked is that I removed the standalone TG589v3 and replaced with the Openreach modem and TG582n again. It seems somehow that the pc is blacklisted somewhere, but the 582 is a basic router and I don't think it has the ability to block equipment does it?
Thanks for any insight.
Mark

[#2]

Quote

I can access the router interface from this pc, but cannot get any further.

Next time it happens run ipconfig from a cmd window and note the default gateway setting. Post the details here and hopefully we will be able to sort out what's happening...

[#3]

Returns this:
C:\Users\Mark>ipconfig
Windows IP Configuration

Ethernet adapter Ethernet:
  Connection-specific DNS Suffix  . : lan
  Link-local IPv6 Address . . . . . : fe80::e933:9196:34e5:9275%3
  IPv4 Address. . . . . . . . . . . : 192.168.1.84
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : 192.168.1.254
Tunnel adapter Local Area Connection* 11:
  Connection-specific DNS Suffix  . :
  IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:18ea:32bb:6d37:e792
  Link-local IPv6 Address . . . . . : fe80::18ea:32bb:6d37:e792%4
  Default Gateway . . . . . . . . . : ::
Tunnel adapter isatap.lan:
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . : lan

[#4]

Now I have access, it looks the same to me.
C:\Users\Mark>ipconfig
Windows IP Configuration

Ethernet adapter Ethernet:
  Connection-specific DNS Suffix  . : lan
  Link-local IPv6 Address . . . . . : fe80::e933:9196:34e5:9275%3
  IPv4 Address. . . . . . . . . . . : 192.168.1.84
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : 192.168.1.254
Tunnel adapter Local Area Connection* 11:
  Connection-specific DNS Suffix  . :
  IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:18ea:32bb:6d37:e792
  Link-local IPv6 Address . . . . . : fe80::18ea:32bb:6d37:e792%4
  Default Gateway . . . . . . . . . : ::
Tunnel adapter isatap.lan:
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . : lan

[#5]

A traceroute from the affected pc to PN and Facebook shows:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Mark>tracert www.plus.net
Tracing route to www.plus.net [198.18.1.47]
over a maximum of 30 hops:
  1    6 ms    3 ms    3 ms  dsldevice.lan [192.168.1.254]
  2    29 ms    28 ms    29 ms  lo0.10.central10.ptw-bng01.plus.net [195.166.128
.170]
  3    *        *        *    Request timed out.
  4    *        *        *    Request timed out.
  5    *        *        *    Request timed out.
  6    *        *        *    Request timed out.
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11    *        *        *    Request timed out.
12    *        *        *    Request timed out.
13    *        *        *    Request timed out.
14    *        *        *    Request timed out.
15    *        *        *    Request timed out.
16    *        *        *    Request timed out.
17    *        *        *    Request timed out.
18    *        *        *    Request timed out.
19    *        *        *    Request timed out.
20    *        *        *    Request timed out.
21    *        *        *    Request timed out.
22    *        *        *    Request timed out.
23    *        *        *    Request timed out.
24    *        *        *    Request timed out.
25    *        *        *    Request timed out.
26    *        *        *    Request timed out.
27    *        *        *    Request timed out.
28    *        *        *    Request timed out.
29    *        *        *    Request timed out.
30    *        *        *    Request timed out.
Trace complete.
C:\Users\Mark>tracert www.facebook.com
Tracing route to www.facebook.com [198.18.1.48]
over a maximum of 30 hops:
  1    4 ms    4 ms    6 ms  dsldevice.lan [192.168.1.254]
  2    30 ms    31 ms    30 ms  lo0.10.central10.ptw-bng01.plus.net [195.166.128
.170]
  3    *        *        *    Request timed out.
  4    *        *        *    Request timed out.
  5    *        *        *    Request timed out.
  6    *        *        *    Request timed out.
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11    *        *        *    Request timed out.
12    *        *        *    Request timed out.
13    *        *        *    Request timed out.
14    *        *        *    Request timed out.
15    *        *        *    Request timed out.
16    *        *        *    Request timed out.
17    *        *        *    Request timed out.
18    *        *        *    Request timed out.
19    *        *        *    Request timed out.
20    *        *        *    Request timed out.
21    *        *        *    Request timed out.
22    *        *        *    Request timed out.
23    *        *        *    Request timed out.
24    *        *        *    Request timed out.
25    *        *        *    Request timed out.
26    *        *        *    Request timed out.
27    *        *        *    Request timed out.
28    *        *        *    Request timed out.
29    *        *        *    Request timed out.
30    *        *        *    Request timed out.
Trace complete.
So it appears to be getting to PN, but no further!!
A similar traceroute from the unaffected laptop:
C:\Users\Mark>tracert www.plus.net
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
  1    1 ms    1 ms    1 ms  dsldevice.lan [192.168.1.254]
  2    27 ms    28 ms    27 ms  lo0.10.central10.ptw-bng01.plus.net [195.166.128
.170]
  3    27 ms    27 ms    27 ms  irb.10.PTW-CR01.plus.net [84.93.249.1]
  4    27 ms    27 ms    27 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
  5    33 ms    33 ms    34 ms  gi5-1.peh-cr02.plus.net [84.93.232.61]
  6    34 ms    35 ms    35 ms  po5.peh-cr01.plus.net [84.93.232.16]
  7    40 ms    37 ms    34 ms  vlan2657.peh-elb01.plus.net [84.93.232.44]
  8    34 ms    35 ms    36 ms  portal.plus.net [212.159.8.2]
Trace complete.
C:\Users\Mark>tracert www.facebook.com
Tracing route to star.c10r.facebook.com [31.13.90.2]
over a maximum of 30 hops:
  1    1 ms    1 ms    1 ms  dsldevice.lan [192.168.1.254]
  2    27 ms    26 ms    27 ms  lo0.10.central10.ptw-bng01.plus.net [195.166.128
.170]
  3    27 ms    26 ms    27 ms  irb.10.PTW-CR02.plus.net [84.93.249.2]
  4    *        *        *    Request timed out.
  5    *        *        *    Request timed out.
  6    *        *        *    Request timed out.
  7    27 ms    27 ms    27 ms  edge-star-shv-01-lhr3.facebook.com [31.13.90.2]

[#6]

Quote

Now I have access, it looks the same to me

It does to me as well
I had hoped that we'd see something change in the gateway and theat might give a clue. Given that you say you still have access to the router then the IP/subnet must be ok and the most likely culprit was the gateway. Although... you might try disabling IPV6 on the router to see if that might the problem see this thread http://community.plus.net/forum/index.php/topic,130654.0.html

[#7]

It says IPV6 is disabled on the router connection page.
Mark

[#8]

I've just relooked at those tracert's and your getting different DNS lookup's when it's working and when it's not
Failing

Quote

Tracing route to www.plus.net [198.18.1.47]

Working

Quote

Tracing route to portal.plus.net [212.159.8.2]

[#9]

One is done on the wired desktop and the other on the laptop. Wonder why there is a difference and how that configuration came into being?
Mark

[#10]

Different IP addresses return could indicate a difference in the DNS settings,  if you do 'ipconfig /all' you'll get more information about the respective settings

[#11]

This is getting very confusing. All of the following were done on the offending PC.
C:\Users\Mark>ipconfig/all
Windows IP Configuration
  Host Name . . . . . . . . . . . . : TowerPC
  Primary Dns Suffix  . . . . . . . :
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : lan
Ethernet adapter Ethernet:
  Connection-specific DNS Suffix  . : lan
  Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
  Physical Address. . . . . . . . . : D8-50-E6-C4-6C-09
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  IPv4 Address. . . . . . . . . . . : 192.168.1.84(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Lease Obtained. . . . . . . . . . : 27 January 2015 14:12:59
  Lease Expires . . . . . . . . . . : 28 January 2015 14:12:58
  Default Gateway . . . . . . . . . : 192.168.1.254
  DHCP Server . . . . . . . . . . . : 192.168.1.254
  DNS Servers . . . . . . . . . . . : 192.168.1.254
  NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 11:
  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:9d38:6ab8:18ea:32bb:6d37:e792(Pref
erred)
  Link-local IPv6 Address . . . . . : fe80::18ea:32bb:6d37:e792%4(Preferred)
  Default Gateway . . . . . . . . . : ::
  DHCPv6 IAID . . . . . . . . . . . : 83886080
  DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-92-F3-49-D8-50-E6-C4-6C-09
  NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.lan:
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . : lan
  Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

While the connection wasn't working, I did the traceroute again, with the previous result.
C:\Users\Mark>tracert www.plus.net
Tracing route to www.plus.net [198.18.1.145]
over a maximum of 30 hops:
 1     3 ms     4 ms     5 ms  dsldevice.lan [192.168.1.254]
 2    30 ms    33 ms    29 ms  lo0.10.central10.ptw-bng01.plus.net [195.166.128
.170]
 3     *        *        *     Request timed out.
 4     *        *        *     Request timed out.
 5     *        *        *     Request timed out.
 6     *        *        *     Request timed out.
 7     *        *        *     Request timed out.
 8     *        *        *     Request timed out.
 9     *        *        *     Request timed out.
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.
Trace complete.
I then turned off the home plug and back on, then ran a traceroute and it is as normal.

C:\Users\Mark>tracert www.plus.net
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
 1     4 ms     3 ms     3 ms  dsldevice.lan [192.168.1.254]
 2    29 ms    31 ms    32 ms  lo0.10.central10.ptw-bng01.plus.net [195.166.128
.170]
 3    65 ms    29 ms    30 ms  irb.10.PTW-CR01.plus.net [84.93.249.1]
 4    29 ms    29 ms    29 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
 5     *       39 ms    35 ms  gi5-1.peh-cr02.plus.net [84.93.232.61]
 6    37 ms    35 ms    38 ms  po5.peh-cr01.plus.net [84.93.232.16]
 7    57 ms    37 ms    37 ms  vlan2657.peh-elb01.plus.net [84.93.232.44]
 8    36 ms    37 ms    39 ms  portal.plus.net [212.159.8.2]
Trace complete.
3 minutes later however, it is reverting back to the strange ip address previously referred to and no access again  

[#12]

It's the TG582n spooflist http://community.plus.net/forum/index.php?topic=134916.30

[#13]

Certainly seems to be the same sort of thing I am experiencing. I can't pretend to know what it is that is being said in that thread though... I have tried to flush the dns several times, but that doesn't work and I know nothing about telnet to access this spoof list. Am I right in thinking a return to factory settings will clear this?  I also can't understand from the thread why it only affects Win 8 machines?
Mark

[#14]

Simplest option would be to set the DNS servers directly on the affected laptop. Either to google DNS or to the PN ones.

[#15]

You beat me to it 
I changed to Google dns about an hour ago and have been randomly going back to check. All seems fine for now.
Thanks for your help and for pointing me in the right direction.
Mark