Why bother obfuscating? It's not like it matters!I've set up the network address to 192.168.1.xxx
Yeah, well... IIRC Win10/11 don't take kindly to connecting by HTTP to anything, let alone on the local network. You might have to force it.Windows 11 AMD PC.
My Windows 11 connects by HTTP on the local network to two of my Humaxes without a problem. The browser just reports the connection as "not secure".Yeah, well... IIRC Win10/11 don't take kindly to connecting by HTTP to anything, let alone on the local network. You might have to force it.
My bet is you don't have the other fields set up correctly.I've set up the network address to 192.168.1.xxx and hit the enter button, It takes a few seconds and I get no errors, but I don't see it on the network.
I've been through all the settings but not found anything that looks like it might help.
Windows 11 AMD PC.
TIA
Pete
One possibility is different devices on different subnets. I have to set the IPv4 mask to 255.255.0.0 on my configuration because of a rogue device.My bet is you don't have the other fields set up correctly.
Thanks for the quick reply.Define "see".
Set up how? With DHCP or static?
Do a DHCP, and only then alter the IP address to what you want (last octet only).I think I'm missing a setting somewhere.
I put "xxx" as I've tried a few in there. I do get the warning but I proceed anyhow and after a few seconds I get the "This site cannot be reached". As someone suggested I tried using DHCP to configure it but after a few seconds all I get is blanks for device address, the subnet mask & gateway.Why bother obfuscating? It's not like it matters!
Yeah, well... IIRC Win10/11 don't take kindly to connecting by HTTP to anything, let alone on the local network. You might have to force it.
I tried using DHCP but all the fields are blank, which suggest it's not connected.My bet is you don't have the other fields set up correctly.
Start by setting it up with DHCP, so the other fields get set correctly, then change to manual IP address setting. That is how I do it with my HDR-Fox T2.
Either that or you're not using DHCP or faulty cable?I tried using DHCP but all the fields are blank, which suggest it's not connected.
You aren't giving much information (you still didn't define what "see" means). There are 4 items needed to make a network work successfully:It has a static IP, and I cannot see it on my local network when I enter 192.168.1.123.
It probably won't if you're setting things statically. It's probably just a list of devices which its DHCP server has assigned. But I have no knowledge of the device.It also doesn't show up in the client list on my TP-Link Archer router
Oh God. If you're setting things statically it doesn't even matter.but that maybe down to the router as it is rather flaky.
Change the cable for one that works.I tried using DHCP but all the fields are blank, which suggest it's not connected.
Define "not connected".I tried using DHCP but all the fields are blank, which suggest it's not connected.
See above.It also doesn't show up in the client list on my TP-Link Archer router, but that maybe down to the router as it is rather flaky.
I've not had time to work on the box for a few days. I had the latest "wimp variant" of Covid, which took me to my bed for just over twelve hours. Since then I've been catching up and I've changed my router. I did delegate changing the Ethernet cable, but I'm going to check it now. Smoke if you got 'em.You aren't giving much information (you still didn't define what "see" means). There are 4 items needed to make a network work successfully:
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.
It is utterly pointless quoting odd bits of information and expecting somebody else to solve your problem.
It probably won't if you're setting things statically. It's probably just a list of devices which its DHCP server has assigned. But I have no knowledge of the device.
Oh God. If you're setting things statically it doesn't even matter.
Change the cable for one that works.
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.248Define "not connected".
DHCP is the process of obtaining a "connection" by negotiation with the router. If DHCP is timing out, there is something wrong with the link between your Foxsat and the router. At the physical level, you only have to look at the lights on the Ethernet port to know whether there is activity (any activity at all).
See above.
It isn't very likely the router isn't working, presuming you are using it for this conversation (particularly if using a mobile or tablet, which are not very amenable to having manual network settings and use DHCP each time)!
That should tell you there's something wrong external to the Foxsat. Are there HomePlugs involved?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
The T2's and the Foxsat are in the same location as the modem router, and are connected directly. No HomePlugs involved. There is CAT6 from the router in the lounge to a switch where the PC is.That should tell you there's something wrong external to the Foxsat. Are there HomePlugs involved?
I thought I had understood and my replies were helpful. Maybe I gave all the right responses, but not necessarily in the right order.Maybe you being unwell is affecting your ability to understand.
Your last 2 responses are just not helpful.
Most people wishing to help require more details, as per @prpr's last post #12
You can try buying more expensive routers but I don't think that'll help.
Try hiring a professional that you trust.
You don't seem to know what you're doing and not giving detail makes it difficult for me to help.