Messages

1

Everything Else / Re: Unable to reach my router

« on: July 21, 2017, 01:04:16 pm »

OK Boggin I will contact Sky when I have an hour or so to spare.  I phone them every year or so to renegotiate my contract and they are nice people to deal with but I find with waiting to get through in the first place and then being moved around a few times I need lots of time and patience, but I usually cut a mutually agreeable deal.  I hope their techies are as good!

Thanks for all your help and while it is not a show stopper it would be nice to get it sorted out sometime.

Cheers mate

2

Everything Else / Re: Unable to reach my router

« on: July 21, 2017, 09:32:49 am »

Sorry mate, iexplore -extoff didn't work either, see attached file

3

Everything Else / Re: Unable to reach my router

« on: July 20, 2017, 02:31:18 pm »

Sorry Boggin, still here, but I forgot to mention I tried the safe mode bit with networking but got similar error message.  I really am going to bed this time, i'll check in tomorrow. night night!

4

Everything Else / Re: Unable to reach my router

« on: July 20, 2017, 02:16:06 pm »

You reset factory defaults using a paper clip into the little hole at the back for 10 seconds.  But the problem existed on my old router and is still there on the new one so I doubt this will help.

Anyway thanks for all your help Boggin, I'm off to bed now.

5

Everything Else / Re: Unable to reach my router

« on: July 20, 2017, 01:56:16 pm »

No

6

Everything Else / Re: Unable to reach my router

« on: July 20, 2017, 01:46:57 pm »

 No idea what Kaspersky Security Data Escort Adapter is but probably part of their extra internet security which I don't subscribe to - it costs!  Looking at the ipconfig it is disconnected anyway

7

Everything Else / Re: Unable to reach my router

« on: July 20, 2017, 01:32:58 pm »

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>

8

Everything Else / Re: Unable to reach my router

« on: July 20, 2017, 01:13:00 pm »

Thanks for your help on using Command Prompt edits and here is the proof - my current IPconfig:-

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>Ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : BigBeastie
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : Home

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : Home
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 34-97-F6-D9-A8-77
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.6(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 20 July 2017 20:34:44
   Lease Expires . . . . . . . . . . : 21 July 2017 20:37:36
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 8.8.8.8
                                       8.8.4.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Kaspersky Security Data Escort Adapter
   Physical Address. . . . . . . . . : 00-FF-F7-D3-0E-5C
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6abd:2842:9a9:a13c:e2e9(Preferred)
   Link-local IPv6 Address . . . . . : fe80::2842:9a9:a13c:e2e9%6(Preferred)
   Default Gateway . . . . . . . . . : ::
   DHCPv6 IAID . . . . . . . . . . . : 100663296
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-07-45-78-34-97-F6-D9-A8-77
   NetBIOS over Tcpip. . . . . . . . : Disabled

C:\WINDOWS\system32>

I've attached a pdf file of the error message.  I also get the same message from my wife's laptop.

Also a second file which shows the drop down when I click the little circle at the left of the URL bar, I believe this is Googles Privacy and Security section.

Will get back to you when I have tried Safe mode. 

9

Everything Else / Re: Unable to reach my router

« on: July 19, 2017, 03:13:38 pm »

I used the IP address 94.195.xx.xx which is the new one after re-booting the router.

I don't know why I thought of it and why I hadn't thought of it before but tonight I keyed 192.168.0.1 into Safari on my iPad and bingo straight into my router's settings.   I may never know why I can't use my desktop machine to access the router settings but at least I can access them from my iPad.  I'll try my wife's laptop when I get a minute.

Thanks for all your help and support, maybe one day I'll solve the mystery. 

10

Everything Else / Re: Unable to reach my router

« on: July 19, 2017, 09:22:40 am »

OK I have now powered up the router successfully and although the IP address has changed my original problem still exists and I can only get to the router settings by keying in the new IP address into the URL bar.  Whether this is safe to do I don't know, but at least I can get to my router's settings this way.

Btw when I right click in the text area of the command prompt window nothing happens - nothing is displayed.  I can highlight the text but right clicking turns the highlight off!

11

Everything Else / Re: Unable to reach my router

« on: July 19, 2017, 06:53:38 am »

I've compared my IPconfig with yours and apart from the Default Gateway being slightly different (mine is 192.168.0.1, yours is 192.168.1.1) everything seems fine.  Don't understand your comment re 151.xxx.etc as my current IP address begins 153.xxx.etc.

This problem has only occurred since I bought a new machine with Windows 10 already installed. My previous machine had Windows 7 and everything worked fine.  Is there a window 10 setting I have missed?

Anyway many thanks for all your time and help, I am now going to power off my router and disconnect all cables, and will be back on-line later.  Incidentally the router is also new(fibre FDDC) from my ISP (Sky UK) but the problem existed with the previous router as well.

12

Everything Else / Re: Unable to reach my router

« on: July 18, 2017, 03:19:27 pm »

Many thanks for response.  I've done as you asked and attached a copy of the command prompt file as a pdf file this time.  hope you can get it as I can't paste direct into here.  Btw i notice in the first section there is a line "IP Routing Enabled........No" could this have a bearing on my problem and if so how do i change it to yes.

I get the 153.etc address from a web site "Thinkbroadband.com.  I use it to run speed tests and the results are saved in my user profile on that site and the IP address is 153.etc at the moment. 

13

Everything Else / Unable to reach my router

« on: July 18, 2017, 11:53:43 am »

I run Windows 10 (Creative Update) with Kaspersky Internet Security 2017.  I use Chrome and IE for browsers.  My problem is I cannot reach my router with the usual 192.168.0.1 no matter which browser I use, and I've used them all.  Please see the attachment for the type of response I get (varies by browser but the message is always the same).  The funny thing is if I type in the IP address of the router as my ISP sees it (153.25x.xxx.xxx) I can get to my router and log in no problem.  I am fairly computer literate but not a techy and I have exhausted all the things I can think of.

Should you have any ideas I could try I would be very grateful, thanks.