Cannot access Foxsat on network

[Black Hole]

Ethernet cable changed. I hadn't checked for activity on the LAN port, but when I did it's a steady green and flashing amber.

That sounds OK.

DHCP not working is the symptom I would chase, because that's not dependent on inputting details. Any device you use that connects to the Internet via your home network, that you have not specifically entered manual credentials for, is necessarily applying to the router for DHCP, so the router not supplying DHCP to the Foxsat specifically is unlikley in the extreme. Have you set everything else up manually?

You could try an experiment with configuring an HDR-FOX by DHCP, see if you get the same result.

 

[prpr]

I thought I had understood and my replies were helpful. Maybe I gave all the right responses, but not necessarily in the right order.

You still haven't provided all the requested information. This:

the IP address, the subnet mask, the gateway address and the DNS address.
Try listing all of those for all the devices in question i.e. the PC, the two T2s, the Foxsat and the router.

Take it line by line, word by word. You've given us the information for the Foxsat so far.

I'm not being deliberately obtuse to wind you up.

But you seem unable to follow instructions which, yes, causes everyone else stress.
What we are trying to get to the bottom of is why one device works and another doesn't. To do that you need to post ALL of the information.
Are your T2s configured with DHCP or static? What about you laptop? Does anything on your network use DHCP and does it get an address? What does your router say about assigned addresses?

Have you tried pinging the Foxsat's IP address from your PC? What happens?
Using phrases like "same results" isn't helpful. Provide some output from commands.

(I don't know what DNS 72.248.140.248 is or how it got in to your Foxsat, but it seems an unlikely setting - whois says that address belongs to Windstream Comms in Littlerock, AR and seems unreachable. Which ISP are you using?)

 

[prpr]

Manual Setup. IP Address: 192.168.1.23, Subnet Mask: 225.225.225.0, Router Address: 192.168.1.254, DNS Address: 192.168.1.254

I've just spotted this on a re-read. Subnet mask should be 255 not 225 i.e. 255.255.255.0
Does your router provide a DNS service? If not you may need to set DNS Address to something like 1.1.1.1 or 8.8.8.8 instead. But that won't stop you being able to ping the Foxsat from your PC.

 

[peterpi]

I've just spotted this on a re-read. Subnet mask should be 255 not 225 i.e. 255.255.255.0
Does your router provide a DNS service? If not you may need to set DNS Address to something like 1.1.1.1 or 8.8.8.8 instead. But that won't stop you being able to ping the Foxsat from your PC.

Sorry typo should be 255. I had a problem with the TP link router I was using and changed it for the standard Plusnet router until I buy a decent one.

As per the photo below, this is what I see on the router GUI and what I have connected to it. Lan1: (Foxsat HDR), Lan2: (T2 HDR), Lan3: (CAT6 to home network switch (with PC, CCTV Cameras, VHF base station gateway, WAP ETC), Lan 4: (PTZ Camera)

To me and, my limited knowledge of such things, it seems the LAN bit of the Fox has a problem as everything else works. And yes, I have tried different Ethernet cable and both activity LEDs illuminate. I don't know what software/firmware does what. I assume that the LAN must use the standard firmware, so would a factory reset be worth a try? Would it repair any corrupted code? A basic LAN cable tester shows that the eight conductors are connected to something in the machine.

Thanks again

 

[peterpi]

That sounds OK.

DHCP not working is the symptom I would chase, because that's not dependent on inputting details. Any device you use that connects to the Internet via your home network, that you have not specifically entered manual credentials for, is necessarily applying to the router for DHCP, so the router not supplying DHCP to the Foxsat specifically is unlikely in the extreme. Have you set everything else up manually?

You could try an experiment with configuring an HDR-FOX by DHCP, see if you get the same result.

I'm still getting all zeros when I use the DHCP approach. When you say set everything else up manually, I have used the Foxsat (HDR) GUI to set up. IE System>Network>Configure Network>Manual: IP Address 192.168.1.123, Subnet Mask 255.255.255.0, Router Address 192.168.1.254, DNS Address 192.168.1.254 and the Ethernet HUmax Mac Address

Thanks

 

[peterpi]

Try updating/creating your network diagram.

Home Network Diagram - All Network Layouts Explained

All possible home network layouts explained. The pros and cons, plus stunning Home Network Diagram that you can use as an example

lazyadmin.nl

In doing so, you may find the cause. If nothing else it may help you describe your network.

Have a look at my latest posts. I think it's a hardware or software with the LAN bit of the Box or the code. But I'm guessing. Trust me, network map would confuse matter even more, but your comment has made me think it might be worth unplugging everything from the router except the Fox, accessing if from my laptop and seeing if I can see it then.

Thanks

 

[Black Hole]

When you say set everything else up manually,

What I actually said was

Have you set everything else up manually?

..."everything else" meaning the HDR-FOX etc, not the Foxsat. Were those set up manually, ie not by DHCP?

I'm trying to keep this at the user level, basic menu operations.

On the HDR-FOX go into Menu >> Settings >> System >> Internet Setting, configure it for DHCP and click "Apply". If that succeeds, report what the settings then say for IP Address etc. If it does not succeed, report failure.

Assuming that succeeds, move the Ethernet cable from the HDR-FOX to the Foxsat. This ensures the Foxsat is on a known working cable, and known working port on the router. Now configure the Foxsat for DHCP and click "Apply". Report.

NB: "T2" is not adequate to uniquely identify an HDR-FOX T2, there are other models with "T2" in the name.

 

[bottletop]

Have a look at my latest posts. I think it's a hardware or software with the LAN bit of the Box or the code. But I'm guessing. Trust me, network map would confuse matter even more, but your comment has made me think it might be worth unplugging everything from the router except the Fox, accessing if from my laptop and seeing if I can see it then.

Thanks

You can try connecting the suspect Foxsat (directly using ethernet) to a pc/laptop.
Compare the results with, say, the same test using a working HDR T2 to pc/laptop.

 

[peterpi]

You can try connecting the suspect Foxsat (directly using ethernet) to a pc/laptop.
Compare the results with, say, the same test using a working HDR T2 to pc/laptop.

I've installed a new DrayTek router (that was easier than I expected) and It's still the same, I think it's an issue with the Foxsat HDR. I'll try what you suggest but if I still cannot connect, I'll give all you guys a rest, do a physical check on the machine and move on. One last question, I'm going to reinstall the CF but I assume the Humax firmware looks after the LAN hardware. Could it be corrupted? If so would a full factory reset take care of it? TIA

Thanks to all who helped.
Pete

 

[Black Hole]

I'm going to reinstall the CF but I assume the Humax firmware looks after the LAN hardware.

Yes

Could it be corrupted?

Doesn't seem very likely, but obviously possible

If so would a full factory reset take care of it?

Factory reset won't affect the firmware, but a good thing to try never the less (in case it's a database corruption causing the problem).

I've installed a new DrayTek router (that was easier than I expected) and It's still the same,

That's significant. Nonetheless, try what I suggested (post 27) and report back.

 

[peterpi]

Yes

Doesn't seem very likely, but obviously possible

Factory reset won't affect the firmware, but a good thing to try never the less (in case it's a database corruption causing the problem).


That's significant. Nonetheless, try what I suggested (post 27) and report back.

I just did a DHCP setup and the results were all 0.0.0.0 except for the DNS address which was 212.159.13.49, although prior to that, on another attempt, it been 192.168.1.1, IE the Routers address.

I just restored it to manual and entered the address in Chrome, got the usual not HTTPS warning, and when I "continue to site" it times out. I'll try a factory reset this evening if there are no more suggestions.

Thanks again
Pete

 

[prpr]

There have been plenty of suggestions, most of which you haven't answered. Why would anybody bother further?

 

[Black Hole]

I just did a DHCP setup and the results were all 0.0.0.0 except for the DNS address which was 212.159.13.49

No doubt that was on the Foxsat. I asked you to try it on the HDR-FOX. Since you seem to ignore everything, there's little point proceeding further.

 

[bottletop]

As above. DHCP setup: IP Address: 0.0.0.0, Subnet Mask: 0.0.0.0, Router Address: 0.0.0.0, DNS Address: 72.248.140.248

Manual Setup. IP Address: 192.168.1.23, Subnet Mask: 225.225.225.0, Router Address: 192.168.1.254, DNS Address: 192.168.1.254

Ethernet cable changed. I hadn't checked for activity on the LAN port, but when I did it's a steady green and flashing amber.

I just did a DHCP setup and the results were all 0.0.0.0 except for the DNS address which was 212.159.13.49, although prior to that, on another attempt, it been 192.168.1.1, IE the Routers address.

I just restored it to manual and entered the address in Chrome, got the usual not HTTPS warning, and when I "continue to site" it times out. I'll try a factory reset this evening if there are no more suggestions.

Thanks again
Pete

So - what is the address for the router?

 

[prpr]

Presumably 192.168.1.1
Looking back at his posting history we see a mess of networking and related stuff involving changing routers and ISPs and such like (the above IP address is mentioned, as is Plusnet which fits with the some-time DNS he quoted).
He was claiming to be old in 2012 and grammar school in the 1950s, so must be very old by now, which possibly explains the apparent cognitive problems.
I wonder if he still hasn't got two DHCP servers and who knows what else of a shambles it all is.
Nobody will ever work this out without being there (SW Wales), so it is all pointless really.

 

[bottletop]

Not necessarily, because Plusnet routers default to 192.168.1.254.
However, op not confirming any device settings, what the router is set to, what the ISP is and not having a network diagram doesn't help matters.

 

[prpr]

Piecing it together from the various snippets of information...
I think he's got cascaded routers and he's trying to use the WAN interface of the downstream one to connect his Foxsat, whilst linking the rest of the network via one of the LAN interfaces (post #24). This is never going to work, in any configuration. There won't be a DHCP server at all on that interface which is why it doesn't work. Quite where the various DNS settings come from is a mystery though (but not one worth pursuing).
What's called a router is not a switch and can't be used as one, even though most (but not all) of the interfaces are indeed connected to a switch within it. He should replace this device with a proper switch and all the problems would go away (maybe!).
I claim my five pounds.

 

[Black Hole]

So basically if he tried DHCP on the HDR-FOX that would fail too. If it did, that would be a data point indicating the Foxsat may not be scrap.

 

[prpr]

Natürlich (well if he swapped the cables to match, otherwise no).

 

[EEPhil]

What's called a router is not a switch and can't be used as one, even though most (but not all) of the interfaces are indeed connected to a switch within it.

Interesting. When I moved house I found an old D-Link DIR 615. Classed by D-Link as a router, with 4 LAN sockets, 1 internet socket and WiFi. When my old network switch went on the fritz I tried the D-Link and it operated just like a switch- providing I didn't use the internet connector. Needless to say, all my network settings were manual at the individual devices. (Internet was a dongle connected to PC and shared through the LAN when required)