Configured depotId 'localhost.opsi.org' for host 'None' not

[c.kampka]

Hi Koenraad,

first of all, you don't have a global.ini because this thread was started in 2009 and is related to opsi of at least 3.x, maybe even 2.x, and any information in this thread is pretty much not relevant for the current stable version.
That beeing said, please feel free to open new threads rather than reopen old descussions, it is much easier to understand your problems that way.

Now, from what I understand from your posting, you adjusted the server address correctly, but you did not touch the client.
The client stores the ip of the server it was installed from localy so it can reconnect to it the next time it boots up. If the client cannot find the server, it obviously cannot fetch a new ip address from it
What you need to do is either fix the problem manually by adjusting the clients configuration files, redeploy the client-agent from the new server (manually), or simply reinstall the client with a fresh operating system.
All three ways should be covered by the manual.

Cheers,
Christian Kampka

[j.schneider]

Please edit /etc/hosts and replace 127.0.1.1 with the ip address of eth0.

[Koenraad]

Hi,

Thanks for the reply.
I see I was not clear enough. At the moment, I don't have installed clients (well, actually one, but that's a problem for later). The problem I have is with a client (a test machine, on virtual hardware) I installed from scratch, after I corrected the server, i.e. opsi provided the OS, everything went fine, drivers and all. But then, when the client tries to contact opsi for updates, it tries 127.0.1.1, so that does not work.
Somehow there is a configuration that has old information, and I can't find it.

I see that I have another reply. My hosts file :
127.0.0.1 localhost
192.168.1.100 opsi.ace-electronics.be opsi

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

There is no 127.0.1.1. AFAIK all is OK.

Regards,

Koenraad Lelong.

[d.oertel]

Hi,

this may happen if the /etc/hosts was not correct at opsi install time.
Just reinstall the opsi-client-agent product with the opsi-package-manager at the server

and then reinstall your client or reinstall the opsi-client-agent using the service_setup.cmd

come back if this did not work

regards

d.oertel