ftp - multiple servers

[ohmbroo]

Hello All,
I need to send ftp images to two different servers for two different cameras.
My NVR is NV5208E
The ftp settings imply that I can add a unique ftp server, username and password by selected which channel.
Only on ftp setting persists and for only channel 1.
I am using the desktop application the comes up with the monitor hooked directly to the NVR.
Thank you,
Edward

[Revo2Maxx]

The NVR provides a single FTP setup, meaning all devices connected to the NVR will use the same FTP server configured on the NVR. However, if you want a camera to send data to a different FTP server, you can connect the camera directly to your IP network (outside of the NVR's PoE ports) and configure the camera itself via its web interface to send data to the second FTP server.

To clarify: the NVR has only one FTP configuration page, so all cameras connected to the NVR's PoE ports will use that FTP server. If you need a camera to send data to a different FTP server, it must be connected to the network independently and configured through the camera’s WebUI for the second server.

[ohmbroo]

Revo2Maxx,
Thanks for the reply on this. This is kinda limiting for the NVR that I was unaware of. I was trying the amcrest web interface which seems to store different ftp server addresses for each then the NVR GUI. So this was miss-leading me. I was playing with different methods of port forwarding the cam, but keeps getting the "server connection failed". Sound like a firmware update request for the NVR should happen.
I had been using blue iris and had no problems like this, except using my main desktop computer. This is why I got the NVR.
Any other thoughts or work around would be appreciated.
Cheer,
Edward

[Revo2Maxx]

Use the NVRs Bride feature if that one offers it like my 5232E-16P does..

Go to the WebUI or GUI of the NVR and then Network and Switch. In there might be an option for Bride Mode, Keep in mind that using this method will change the NVRs POE switch from using the NVR as a DHCP server to the Router on your network being used for the POE Ports on the NVR and this will let you access the cameras WebUi and use the camera to go to its own FTP server..

You can't forward ports normally from a POE NVR or access the camera without using the NVRs IP and going to the camera page, then clicking the e on the camera. Keep in mind that first one opens on 10080 and chrome and edge normal reject this use so make sure to click one you don't want to access first then click the one you do want to access and it will open on port 10081..

However with your NVR having the Bridge mode like my 52xx series NVR does then it won't act this way anymore and you can access all cameras by going to the WebUI directly.. Also if your NVR does offer this mode you can also connect non camera devices on your NVR if you needed to because it would act like a normal POE Network Switch rather then a NVR POE for IP cameras..

[ohmbroo]

Revo2Maxx,
Yes, I do have the Bridge option on my NV5208E!
I have not experimented with it yet, but will.
There is a enable check box, IP Address, Subnet mask and default Gateway.
Will the bridge mode effect any other NVR operations that you know of?
Thank you!
Edward

[Revo2Maxx]

No, Only thing that Bride Mode will do is turn off the NVRs DHCP server and will then use the local area networks DHCP server to hand out IPs to the cameras. Keep in mind that if your cameras are setup right now with DHCP disabled the camera might get stuck on the 10.1.1.xx Range that the NVR has forced it into.. So to cure this, Use IP Tools from Amcrest, input your password into the tool, This password will be removed after you close the tool, but will let you access the camera. When you bring up the IP tool, It will load your cameras even on the Wrong Ip range, then you click on the Modify icon and either change to a IP within your network or click on DHCP. Keep in mind that it is best to use Static Ip because if your router isn't setup for your camera to have a static IP in the router pool it might get a different IP later in time and be lost from the NVR.. So in some cases best to setup Static out the gate in the camera or just setup the Router this way the NVR will always have your right IP for that channel..

[ohmbroo]

Thank you for the elaboration Revo2Maxx. I do see the initial DHCPs from my router for the cams, interesting how the last octet matches what the NVR DHCP delivered for two of the cams. Just the luck of the draw how the enumeration was set up I guess. Will give this a try when I can reserve some time to tweak after the bridge is enabled. Will follow up.
Cheers,

[ohmbroo]

Got the bridge setting in. 3 cams with 10.1.1.x persisted and two cams adapted right away to 192.168.0.x.
I was able to set the 3 cams using the NVR GUI to change to a selected 192.168.0.x that I picked. Just had to make sure to credential in again. The after the cam was found, add to the cam list, then log in again via the cam settings.
I now have two cams providing ftp snapshots to two different ftp accounts. I use webcam.io and here is one of my cams: webcam.io/webcams/dzoG2z/ and the older cam: webcam.io/webcams/9RNNV9.
The IP tools was useless, useless in changing the IPs, but was useful for scanning the 10.1.1.x and 192.168.0.x.
Thanks very much! Lots of cred to you!
Edward

[Revo2Maxx]

Sorry I keep forgetting that I don't use the standard Amcrest Ip tools, I have the one from Dahua and use a couple others that I can make changes that are not offered with the Amcrest tool.. Only one is branded with a name that is different and the Dahua tool desktop link looks like the Amcrest one so I keep forgetting that I don't use that one.. This is 2 of the main ones I use, Also have some Hikvision ones that are not on here and other machines that are in different segment of my network.

Screenshot (2810).png (126.07 KiB) Viewed 3451 times

Screenshot (2811).png (69.07 KiB) Viewed 3451 times