This occurs when someone tries to access your Networker server usingn the GUI from an unauthorized console such as a workstation. You should try ping -a 10.1.1.15 to find out who is attempting to access the server and proceed from there.
You need to identify which machine that is and find out why it is trying to access your server. The -a switch in ping will return the machine name if it exists. You may be able to use that to identify it.
You are getting this message because of an illegal access attempt via Networker. It is no different than someone trying to access your domain illegally. You should respond based upon whatyou find. It may be an innocent attempt to access the server, or something else. What that is, only you can determine.
Ping -a don't give me the hostname because this IP isn't specified in the hosts file.
10.1.1.15 is a UNIX machine of our computer park, but we never install networker! This machine isn't specified in the DNS server
Is it possible to find out when this error appears?
What client is started when this error appears?
There is one possibility
-one of your clients reports back with primary NIC IP (which is 10.1.1.5).
-10.1.1.15 is not defined in local hosts (nor in DNS);
-10.1.1.15 cannot be resolved;
-error is reported.
What you can do is:
start every single backup group in verbose, probe mode.
Do it from the command line, like this:
savegrp -vvv -p <group name>
Output should contain info about every single client in the group (it will include client's IP addreses).
In fact, it do it every 5 seconds... All groups are backup (and stop) but this error continue to occure......
It happen when we upgrade the server to 6.1.1... after the reboot....
Strange no???
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.