Standard from someone like axa with failure to operate is £90 plus £2500 excess for failure, I just had a peak the other day what the usual mob would say
Can you not bury the cable where it is maybe carefully unclip it
Although your better off ripping whole system out , if your renovotaing completely replace cables while your at it , if not try and save the cables , system equipment probably might work but better having something upto date
Ok I saw a bit more
You have set dhcp on DVR which is giving it IP 192.168.1.8
Then you dmz 192.168.1.200 which won't do anything
You must set the DVR same as dmz IP , dmz will help you make it work without worry about port forwarding , once you have it working you can look to change that after
Set DVR STATIC 192.168.1.200 SAME AS DMZ
I like title "epic"
I didn't watch all that but you back to first problem
Set to static not dhcp
You have also changed the port number I think to a different range ie 4528 which also has to be put into the app
Point is don't keep changing things on the ports otherwise you will go in circles
Ok so direct is good another WiFi not , tell me all settings on DNS screen shot will do and which password are you using for the app
Also do you still have dmz currently for the DVR as that will rule out the router further
I assume IP on DVR 192.168.1.200 and dmz is the same (although) remove dmz later
Router is not problem , because Samsung can see the DVR
Have you tried connecting outside of WiFi with DNS or inside WiFi with direct IP on app?
As said before this is common with some of there machines to playup when trying to connect internally using the DNS route