We were able to setup NetWatch on our head end router just fine, but when we tried to set up another NetWatch on a router further in on the system it won’t work.
The only error I get in the log is: Error sending e-mail: error talking to server
I can open a telnet session though and create and send an e-mail successfully from the router just fine.
All MT routers on our system are using a public IP and the mail server is also on a public IP.
~Sean
Several things can be wrong,
If you are on a routed network, does it all work? Best way to test is to see if you can reach that ´further down the line router´ with winbox, and vice versa. This way you know IP configuration with routing is setup properly and TCP/IP and smtp traffic should work fine.
Secondly, are any firewall filters enabled that can block smtp (port 25) traffic? (Also on the main router)
Why netwatch fm. router further down the line? Actually you should make your main router netwach that distant router. If that distant router has to netwatch itself and it goes down it can’t send an mail! (But you can test send one, for instance initiated with telnet!) If it goes down while beeing monitored from the main router that main router can send that e-mail.
I have my main router netwatching 5 other routers that way! (My main router is also a PC based system and only does do the routing while all my other units are rb’s. The rb’s take care of the wireless clients which takes CPU power while the routing on the main one hardly consumes any CPU power. Let that main router do all extra tasks! It has plenty power left for these kind of things.)