Port Forwarding for FTP / Mail server

anybodii

Prominent
May 7, 2017
1
0
510
Have a DVR for security cameras that are being setup to upload to a server off site ( not local ), and also setup to send email alerts. I have my own modem ( just a modem ) connected to a router, then the router is wirelessly bridged to another router that only provides Ethernet to the cameras. Now I previously setup remote viewing from computer/mobile for the cameras and had to allow the port, this worked. Now that I'm trying to allow FTP and mail server, its not working *To clarify, the mobile viewing still works, but the FTP and mail server do not*. At my previous house I did this and there was no issue ( though there was no bridged router before ) All settings on the DVR are correct to upload/send mail. I've allowed ports on both routers ( Port 21 and 465 ), I've confirmed the usernames/passwords/etc I'm able to access the website through FTP client on my computer. At this point I'm assuming it has to be some issue with the DVR as I'm not sure what more I could do to ensure all setup is correct.

Main router is 192.168.1.1 and camera router is 192.168.2.1 to ensure no conflicts. Static IP was assigned to ensure no changes in IP. Confirmed IP from camera router to primary router because going to local IP of cameras will bring up remote viewing. Camera router is using Shibby Tomato firmware as Asus firmware wouldn't allow bridging. Linksys is primary router with Linksys firmware. Website is just a VPS with cPanel, so nothing crazy there.

Just hoping I overlooked something simple, or for people to tell me yeah it has to be the DVR, though that brings up questions as to why mobile viewing works, but not FTP or mail.
 
Solution
FTP can be run in a number of ways. You likely should port forward 20 and 21. Mail servers normally use port 25 although 465 is a non standard SMTP port so it may be correct.

Because so many people are idiots most ISP block any form of mail server to avoid them being taken over as spam bots. FTP server is also blocked by many ISP because of hackers taking them over and using them to share illegal files.

Maybe take a PC and run wireshark on it. Port forward the mail and ftp ports to this pc. It will not actually work but what you are looking for is to see if you see SYNC packets coming in from the internet. This will tell you if the ISP is blocking you. If you see the SYN packets coming in then the problem is likely a...
FTP can be run in a number of ways. You likely should port forward 20 and 21. Mail servers normally use port 25 although 465 is a non standard SMTP port so it may be correct.

Because so many people are idiots most ISP block any form of mail server to avoid them being taken over as spam bots. FTP server is also blocked by many ISP because of hackers taking them over and using them to share illegal files.

Maybe take a PC and run wireshark on it. Port forward the mail and ftp ports to this pc. It will not actually work but what you are looking for is to see if you see SYNC packets coming in from the internet. This will tell you if the ISP is blocking you. If you see the SYN packets coming in then the problem is likely a configuration issue on the DVR it should also get the incoming packets but does not respond correctly.
 
Solution

BuddhaSkoota

Admirable


While port forwarding would be required for remote viewing, it would not be required for FTP and email since your DVR is trying to connect to those servers outside of your network (i.e. it would only be required if you were running your own FTP and email servers).

Is there a specific reason why you need the cameras on a different subnet? Have you tried doing the client FTP test from a PC connected to this second router? You may want to try configuring the camera router as an AP/switch, and allow only the main router to perform DHCP. Then if you still have problems, focus your troubleshooting on a possible DVR configuration issue.
 

TRENDING THREADS