Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Ron on November 24, 2003, 03:00:39 AM
-
Hi
I have been using this contrib for 1 week:
http://mirror.contribs.org/smeserver/contribs/gzartman/Contribs/ez-ipupdate/e-smith-ez-ipupdate-3.0.14-1.noarch.rpm
on SME5.5. and when the cron.weekly file ran I get this output:
/etc/cron.weekly/refresh-ddns:
Bad Authorization String
Waiting for routing tables to update...
My settings are correct according to Easydns.com
Am I using the correct contrib or should be using the one from Darrell May's Contrib area:
http://mirror.contribs.org/smeserver/contribs/dmay/mitel/contrib/ez-ipupdate/dmc-mitel-ez-ipupdate-3.0.13-2.noarch.rpm
Any help would be appreciated
-
I have used EZ-IPUpdate for a number of years on E-Smith and SME without problem.
Try to run it manually first to ensure it works. Setting the config file with the executable bit should be enough to figure out if yout file is correctly identifying your own settings.
Note that if you are behind a router, you MUST specify the IP as 1.1.1.1 and NOT specify any interface (no eth0, eth1 or ppp0). Because the program will only run as a daemon if an interface is specified, you will have to run it using the scheduler.
If you do not have a router between your SME and the internet, then you should specify the interface only (try either eth0 on a cable modem or ppp0 if you use PPPoE) and run it as a daemon instead of using crond.
It should work fairly easily but, not knowing your exact configuration, it is not possible to tell you exactly how to do this. You will have to do some trial runs.
Good luck.
Serge
-
All I have is a Motorola SB5100 DOCSIS Cable modem between my
SME 5.5 server and gateway. I am sending and reciving mail on two
separate domains. The pages can be seen externally from the net.
My question was pretaining to the apparent error that was mailed to my
root@mydomain.com which said: when the cron.weekly file ran::
/etc/cron.weekly/refresh-ddns:
Bad Authorization String
Waiting for routing tables to update...
My concern is regarding the Bad Authorization String
Any ideas