Hi folks,
maybe someone stumbled over this problem and maybe my solution does help.
I configured a Zabbix agent on a Server 2008 box to monitor our SBS. It did start and you were able to connect from the server BUT no connection from agent to server:
The agent log showed the following error message:
failed to accept an incoming connection: connection from <ip> rejected, allowed hosts <testhostname>
I searched and searched but was unable to find any link to <testhostname> -
simply because I thought that I had changed all links to the new production Zabbix server. I was unable to find a trace that pointed to <testhostname>.
But the error messages continuously turned up!
After I opened a CMD shell to check the directory for some kind of double config file I decided to dump the contents of zabbix_agent.conf to the console. AND THERE IT WAS: the file still contained all the links to <testhostname>!!!
The reason for this was that my editor was started unter the domain admin account. To edit the config file you need to have elevated access rights -- which is not the same under Windows!
As Windows was unable to edit the configuration file it created a copy of the file in one of the domain admin directories and started to edit this copy! Without changing the filename/path in the editor!!! No change to detect this!!! (Sometimes Windows suxx so hard!)
Solution was to start the editor with elevated access rights, to do the changes to the config file and to restart the service. Finally everything worked as expected.
I hope this will help some Windows admins.
Regards,
Stefan Sperling
maybe someone stumbled over this problem and maybe my solution does help.
I configured a Zabbix agent on a Server 2008 box to monitor our SBS. It did start and you were able to connect from the server BUT no connection from agent to server:
The agent log showed the following error message:
failed to accept an incoming connection: connection from <ip> rejected, allowed hosts <testhostname>
I searched and searched but was unable to find any link to <testhostname> -
simply because I thought that I had changed all links to the new production Zabbix server. I was unable to find a trace that pointed to <testhostname>.
But the error messages continuously turned up!
After I opened a CMD shell to check the directory for some kind of double config file I decided to dump the contents of zabbix_agent.conf to the console. AND THERE IT WAS: the file still contained all the links to <testhostname>!!!
The reason for this was that my editor was started unter the domain admin account. To edit the config file you need to have elevated access rights -- which is not the same under Windows!
As Windows was unable to edit the configuration file it created a copy of the file in one of the domain admin directories and started to edit this copy! Without changing the filename/path in the editor!!! No change to detect this!!! (Sometimes Windows suxx so hard!)
Solution was to start the editor with elevated access rights, to do the changes to the config file and to restart the service. Finally everything worked as expected.
I hope this will help some Windows admins.
Regards,
Stefan Sperling