-- deleting some previous BS guesses (told you I'm not a network engineer) about how this might work, and appended a correction post based on a test I did locally --So this "switch" who is distributing DHCP addresses
Last edited:
-- deleting some previous BS guesses (told you I'm not a network engineer) about how this might work, and appended a correction post based on a test I did locally --So this "switch" who is distributing DHCP addresses
I feel like his switch is not assigning IP addresses, and his "router" is still on 192.168.178.X. So his manually assigned 192.168.1.X devices can't talk to each other, because they are sending packets to the switch, and the switch is forwarding them to the router and the router is sending them out to the internet.
The switch would have to be a smart switch set up for IP routing for that (unlikely) to be the problem, as opposed to just a a layer-2 switch where it's all about the MAC addresses.So his manually assigned 192.168.1.X devices can't talk to each other, because they are sending packets to the switch, and the switch is forwarding them to the router and the router is sending them out to the internet.
-- deleting some previous BS guesses (told you I'm not a network engineer) about how this might work, and appended a correction post based on a test I did locally --The switch would have to be a smart switch set up for IP routing for that (unlikely) to be the problem, as opposed to just a a layer-2 switch where it's all about the MAC addresses.
But I suppose stranger things have happened.
The modem/router assigns ip adresses (as far as I know). The switch settings are set like in the image below (current ip = 192.168.178.158).
![]()
I've set the range on the modem to 192.168.1.x. Then it assings IP adresses to PC and switch. But this still did not work.
On windows 10 (I dont know what you are using):Also, where can I find the advacned TCP/IP settings? Thanks!
Only says 'Port 6'. Not listed in the mac adresses either.Hover over the port six on the top of the screen, the lighting bolt.
I did exactly this, but still get 'Host destination unreachable' when pinging to 192.168.1.108.On windows 10 (I dont know what you are using):
- enter: ncpa.cpl in Windows search, click the one it finds that's a "Control Panel Item"
- Select the network adapter that is wired to the switch (you might just have one, or you might have a wired and a wifi)
- Right-Click, Select "Properties"
- Find: "Internet Protocol Version 4 (TCP/IP)" in the list of items on the connection
- Click "Internet Protocol Version 4 (TCP/IP)" to select
- click "Properties"
- Find "Advanced" button, click that.
- Under the box titled "IP Addresses", you hopefully already see your manually configured IP address 192.168.1.X , or if you reverted all your prior changes you might see "DHCP Enabled"
- (if your PC is using DHCP, you might have to go back a screen and change it to a MANUAL IP
- use something like 192.168.178.250 or even the address it is currently assigned by the DHCP server
- just don't overlap any other potential DHCP devices, or you'll have an IP conflict and ton of stuff wont work
- subnet: 255.255.255.0 to continue
- Click the "Add" button
- Enter the suspected IP network of the camera, probably 192.168.1.1
- Enter subnet mask: 255.255.255.0
- Click "Add", it should pop into the list
- Click "OK" like 4 times
- You can always come in and delete this later after you get the camera fixed, or just leave it so next camera will be easier.