01304 827609 info@use-ip.co.uk Find us

DS-7608NI-K2/8P connection issue

@Amir_init hi Amir. Try this
Thanks David, not much can be done in the VM router whilst its in modem mode, there is nothing you can change in advance settings. You mentioned you have two routers setup are they both in router mode and connected together ?

"can you configure the VM router wifi network to be the same as the amazon router? saves a lot of hassle, its what I do. Just make a note on the VM router."
 
Thanks David, not much can be done in the VM router whilst its in modem mode, there is nothing you can change in advance settings. You mentioned you have two routers setup are they both in router mode and connected together ?

"can you configure the VM router wifi network to be the same as the amazon router? saves a lot of hassle, its what I do. Just make a note on the VM router."
Also I see these logs in VM modem mode:

Not sure if this means anything to you as I cannot make head or tails of it

Network Log​

TimePriorityDescription
20/08/2021 20:58:15​
notice​
LAN login Success;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
18/08/2021 08:08:43​
critical​
No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
17/08/2021 14:23:30​
notice​
DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
17/08/2021 14:23:30​
Error​
DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
14/08/2021 17:10:43​
critical​
No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
14/08/2021 06:12:11​
notice​
DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
14/08/2021 06:12:11​
Error​
DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
13/08/2021 12:17:9​
critical​
No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
11/08/2021 13:12:54​
notice​
LAN login Success;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
11/08/2021 06:40:57​
critical​
No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
10/08/2021 19:32:49​
Warning!​
RCS Partial Service;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
10/08/2021 09:34:47​
notice​
DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
10/08/2021 09:34:47​
Error​
DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
09/08/2021 17:18:1​
critical​
No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
07/08/2021 10:00:11​
notice​
DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
07/08/2021 10:00:11​
Error​
DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
07/08/2021 10:00:8​
Error​
DHCP RENEW sent - No response for IPv4;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
04/08/2021 22:12:2​
critical​
No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
03/08/2021 14:53:56​
notice​
DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0;​
03/08/2021 14:53:56​
Error​
DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=40:0d:10:54:46:6b;CMTS-MAC=00:eb:d5:21:bf:91;CM-QOS=1.1;CM-VER=3.0​
 
You mentioned you have two routers setup are they both in router mode and connected together ?
I only have 1 router setup, 2 routers together can lead to double natting and possible remote access problems. This is best avoided.

re the VM logs, can you tell if the DHCP errors are on the WAN or LAN side? Do the MAC addresses belong to any of your devices?

open a new text file and copy paste the amazon wifi network name and password.

switch off the amazon router and put the VM modem in router mode. Go to the VM router wifi setup page and paste the Amazon router wifi settings there, you may have to restart the VM router. All your wifi devices should automatically reconnect. See what IP address the NVR gets and wait to see if it loses connection.

What is the VM router LAN subnet IP addressing?
 
Hi David

just trying to see if other things will work before I switch VM into router mode

I have a synology disk station DS214play which can act as a dhcp server. now I am not very good with networking but would like to try switching off DHCP on the amazon router and make it point to the synolgy for it to give out IP leases via DHCP.

any ideas what IP address I set on the synology LAN port and DHCP , I have attached a screen shot from the synology station to make it a bit more clearer

I am aslo not sure what settings to put on the amazon router - again doc attached
 

Attachments

@Amir_init Hello Amir,
Personally I would not do this, there's a good chance you'll lose access to your router and disk station. That will mean a factory reset for both or setting up a fixed subnet to gain access. Is there any particular reason you don't want to put the VM modem into router mode, even temporarily for 3 days?

You should be able to replicate your existing wireless network on the VM router and maybe setup the same LAN subnet as the Amazon router.
 
Hi David

Found the issue in the end, the cat 6 cable coming from NVR NIC to router was faulty, the connector on the router end was not crimped correctly, this has now been replaced. I also had all cat 6 cables tested. Appreciate all the help :)
 
Hi David

Found the issue in the end, the cat 6 cable coming from NVR NIC to router was faulty, the connector on the router end was not crimped correctly, this has now been replaced. I also had all cat 6 cables tested. Appreciate all the help :)
Hi Amir, you’re welcome. It happens sometimes. After crimping I always check the end of the connector to make sure all 8 crimp connections are down.
 
Back
Top