Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

SMTP and FTP server setting for Router, NAS and IPcamera

Options
  • 21-11-2010 2:29am
    #1
    Closed Accounts Posts: 131 ✭✭


    I have a Netgear WNDR3700 router which runs on Magnet broadband. I have a NAS drive and an IP Camera connected to the router. But I am facing problems with SMTP server setting. I tried to send emails using the gmail, gmx and aol (with correct smtp server and port settings) but emails are not send by either router or NAS drive or ip camera. Since magnet doesnt offer an ISP email what is my option? I dont want to run an smtp server all the time on my laptop and keep it working 24x7. Any free or anonymous smtp servers?

    The same is the case with the IPcamera FTP setting. I have given 192.168.1.1 as the ftp server ip, router login and password as the ftp user and ftp password and the ftp folder on the usb stick connected as the ftp upload folder. But it wont work. Again dont want to run a home ftp server all the time. Any clue?


    th_02975_IPCameraEmailsettings_122_377lo.jpgth_02981_IPCameraFTPsettings_NETGEAR_122_218lo.jpgth_02985_RouterEmailConfSetting_122_216lo.jpg


    th_02235_IPCameraFTPsettings_NETGEAR_122_579lo.jpg


Comments

  • Registered Users Posts: 194 ✭✭daffy_duc


    Have you tried smtp.magnet.ie ?


  • Closed Accounts Posts: 131 ✭✭net4hack


    I doesnt have an email id with magnet. I dont think they provide any for home customers. So could i use smtp.magnet.ie


  • Registered Users Posts: 1,340 ✭✭✭bhickey


    net4hack wrote: »
    I doesnt have an email id with magnet. I dont think they provide any for home customers. So could i use smtp.magnet.ie

    Yes if you want to use port 25 for SMTP (i.e. outbound e-mail) ona Magnet broadband connection then use smtp.magnet.ie


  • Closed Accounts Posts: 131 ✭✭net4hack


    bhickey wrote: »
    Yes if you want to use port 25 for SMTP (i.e. outbound e-mail) ona Magnet broadband connection then use smtp.magnet.ie
    Yes, smtp.magnet.ie worked. Thanks a mil. Now email alerts from Router, NAS and IP Camera are working...

    Any suggestion with the FTP setting on the ip camera?


  • Registered Users Posts: 1,064 ✭✭✭Snowbat


    If the NAS box has an ftp interface, you could configure the camera to upload pictures to it - find the LAN IP address of the NAS (192.168.x.x) and enter that as the FTP Server address along with a valid username and password. Otherwise you'll need an account on an ftp server somewhere.


  • Advertisement
  • Registered Users Posts: 1,340 ✭✭✭bhickey


    net4hack wrote: »
    Any suggestion with the FTP setting on the ip camera?

    Do you have any more info than "But it wont work"? Have you tried connecting to the FTP server from an FTP program (e.g. Filezilla) on your computer so that you can verify first that everything is setup properly before you try to get it working with the IP camera?


  • Closed Accounts Posts: 131 ✭✭net4hack


    bhickey wrote: »
    Do you have any more info than "But it wont work"? Have you tried connecting to the FTP server from an FTP program (e.g. Filezilla) on your computer so that you can verify first that everything is setup properly before you try to get it working with the IP camera?

    I tried the filezilla initially but it didn work and I havent tried it with new settings. I actually don't want to use it because it requires a computer to be running all the time along with filezilla. I just want to use the inbuilt ftp upload capability that would upload the files to either the usb storage or to the nas drive connected to the router.
    bhickey wrote: »
    Do you have any more info than "But it wont work"? Have you tried connecting to the FTP server from an FTP program (e.g. Filezilla) on your computer so that you can verify first that everything is setup properly before you try to get it working with the IP camera?

    I gave 192.168.1.1 as the ftp server address and the full ftp path as the folder location to upload the images like ftp://networkspace2/USBShare/ipcam/. But it didnt work! Is the naming convention correct?


  • Registered Users Posts: 1,340 ✭✭✭bhickey


    You don't need a computer running all the time to try Filezilla. Try the Filezilla CLIENT (i.e. NOT the server) from your computer to check that your FTP server on 192.168.1.1 is running as expected. You should be able to transfer files via FTP from your computer to your FTP server. If that works then the rest might follow.


  • Closed Accounts Posts: 131 ✭✭net4hack


    The filezilla client is working fine with the settings. But unfortunately I cant test it with ip camera now as it has gone back to the company for replacement. So I have to wait till i get a new one.

    Now I have a new problem with the DoS Attacks and remote access, I am getting from remote. I could only think of the ip cam software I installed and the DDNS hostname I setup with DynDNS.org. I just wonder what is happening? Log follows.

    [LAN access from remote] from 216.108.231.184:53700 to 192.168.1.20:21, Thursday, November 25,2010 03:42:01
    [LAN access from remote] from 74.118.193.22:3895 to 192.168.1.20:21, Thursday, November 25,2010 03:36:02


    [DoS Attack: RST Scan] from source: 83.240.162.82, port 51336, Thursday, November 25,2010 20:57:09
    [DoS Attack: IMAP Scan] from source: 86.16.19.78, port 53871, Thursday, November 25,2010 20:49:16
    [DoS Attack: IMAP Scan] from source: 86.16.19.78, port 53869, Thursday, November 25,2010 20:49:15
    [DoS Attack: IMAP Scan] from source: 86.16.19.78, port 53868, Thursday, November 25,2010 20:49:15
    [DoS Attack: IMAP Scan] from source: 86.16.19.78, port 53870, Thursday, November 25,2010 20:49:15
    [DoS Attack: IMAP Scan] from source: 86.16.19.78, port 53871, Thursday, November 25,2010 20:49:15
    [DoS Attack: IMAP Scan] from source: 86.16.19.78, port 53869, Thursday, November 25,2010 20:49:14
    [DoS Attack: FIN Scan] from source: 86.16.19.78, port 53871, Thursday, November 25,2010 20:49:14
    [DoS Attack: FIN Scan] from source: 86.16.19.78, port 53870, Thursday, November 25,2010 20:49:14
    [DoS Attack: FIN Scan] from source: 86.16.19.78, port 53869, Thursday, November 25,2010 20:49:14
    [DoS Attack: FIN Scan] from source: 86.16.19.78, port 53868, Thursday, November 25,2010 20:49:14


  • Registered Users Posts: 1,340 ✭✭✭bhickey


    Are you forwarding any inbound connections from the Internet to your computer or to a DMZ? Nothing should ever get directly from the Internet to your PC or anything else on the LAN unless you specifically allow it. That's why we all have firewalls.


  • Advertisement
  • Closed Accounts Posts: 131 ✭✭net4hack


    No, I am not forwarding any connections from internet to my computer.

    Automatic Port Forwarding was enabled on the NAS drive. I have now disabled it along with DynDNS hostname support on both Router and NAS drive. I also installed Comodo Firewall (Free Version) on my computer. So just watching the router logs now.


  • Registered Users Posts: 1,064 ✭✭✭Snowbat


    See Internet background noise and GWF

    Botnets and worms are continuously probing for new targets to attack. If you expose services on well-known ports or start logging everything that arrives at your router, you will see this kind of traffic.

    The connections from 216.108.231.184 and 74.118.193.22 are interesting but if you have a strong ftp password and are not seeing a password-guessing attack, are of no concern. You could move your ftp port to a non-standard port number to reduce the visibility.

    Traffic from 83.240.162.82 is just probing some standard ports. It wouldn't count as a DoS attack unless you're seeing thousands of connections per minute.

    Feel free to report the unwanted traffic to the ISPs concerned but they may not follow it up unless it was a password guessing attack or an actual DoS attack.

    DynDNS is not a factor as the list of DynDNS hostnames is not published. This traffic comes from systematic scanning of IP address blocks.


Advertisement