My Humax Forum » Freesat HD » HDR 1000, 1010, 1100S

hdr110s no wifi

(25 posts)
  1. REPASSAC

    REPASSAC

    special member
    Joined: Mar '11
    Posts: 4,100

    offline

    Interesting but not what I expected which was your router to be 192.168.0.1 not 192.168.0.3. - Do you have another router somewhere??
    Can you post the DHCP settings page, it will define start and end addresses etc. Also if there are any address reservations.

    If you have a PC can you enter
    ping 192.168.0.1
    in a command prompt.

    | Mon 19 Nov 2018 11:11:37 #11 |
  2. User has not uploaded an avatar

    norbellini

    member
    Joined: Nov '18
    Posts: 15

    offline

    "If you have a PC can you enter
    ping 192.168.0.1
    in a command prompt."
    Sorry but that is beyond me i would need a walk through

    | Mon 19 Nov 2018 15:13:45 #12 |
  3. REPASSAC

    REPASSAC

    special member
    Joined: Mar '11
    Posts: 4,100

    offline

    Windows 10:
    Right-click on Windows icon bottom left of screen.
    Click on run
    In the dialog box enter
    cmd.exe
    A new black windows will appear where you can enter:
    ping 192.168.0.1

    In my case the router Is on 192.168.1.1 the response is:

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

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

    This is in addition to the other requests in my last post.

    Does you router show a client with address 192.168.0.1?
    Can you also list the kit in your network.

    | Mon 19 Nov 2018 16:04:49 #13 |
  4. User has not uploaded an avatar

    norbellini

    member
    Joined: Nov '18
    Posts: 15

    offline

    C:\Users\nobyys>ping 192.168.0.1

    Pinging 192.168.0.1 with 32 bytes of data:
    Reply from 192.168.0.1: bytes=32 time=5ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255

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

    | Mon 19 Nov 2018 16:46:25 #14 |
  5. User has not uploaded an avatar

    norbellini

    member
    Joined: Nov '18
    Posts: 15

    offline

    one router netgear dg834g

    | Mon 19 Nov 2018 16:48:14 #15 |
  6. User has not uploaded an avatar

    Martin Liddle

    special member
    Joined: Feb '11
    Posts: 4,711

    online

    norbellini - 2 hours ago  » 
    one router netgear dg834g

    Any WiFi extenders or similar?

    | Mon 19 Nov 2018 19:00:40 #16 |
  7. User has not uploaded an avatar

    norbellini

    member
    Joined: Nov '18
    Posts: 15

    offline

    Aye,do you know there is one I will try that tomoro

    | Mon 19 Nov 2018 22:13:47 #17 |
  8. User has not uploaded an avatar

    norbellini

    member
    Joined: Nov '18
    Posts: 15

    offline

    not the wifi extender I reckon next step reset router thanks

    | Tue 20 Nov 2018 10:51:24 #18 |
  9. REPASSAC

    REPASSAC

    special member
    Joined: Mar '11
    Posts: 4,100

    offline

    Did you check the WiFi extender is configured correctly as an extender and not as a router.

    Something is active on 192.168.0.1 the 3ms response time does not seem like a cable connection see my <1ms response time.

    If you reset the router un-power the extender first until the router boot is finished and finally repower the Humax and post the Humax network info.

    | Tue 20 Nov 2018 12:27:55 #19 |
  10. User has not uploaded an avatar

    norbellini

    member
    Joined: Nov '18
    Posts: 15

    offline

    ok

    | Tue 20 Nov 2018 13:50:49 #20 |

RSS feed for this topic

Reply »

You must log in to post.