We had the same prob with a IBM server.
The problem was a service of IBM that was running, we just had to disable it and the problem was resolved.
The service begun with something like "IBM service reboot..." or something like that.
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.