There are several machines running on ESXI. Older machines have static IP addresses, and hostnames like Agent1 / 2/3 / 4. All machines have the same set of software, including samba for organizing password-free network access to the balls from the Windows environment. In the Samba settings, the hostname (netbios name) is not specified, the hostname of the machine is tightened.

2 more virtual machines -agent5 / 6 were obtained from the Agent2 machine by copying method (renamed via the Ubuntu interface, the hostname and hosts files were checked for correctness of changes). They get ip addresses dynamically, but these dynamic addresses are tied to the mac addresses of the machines (we were clamped to a static pool).

The problem is that sometimes, for unexplained reasons, Agent6 also responds to the name Agent2. That is, when trying to look at the balls of the 2nd agent, we are actually looking at the balls of the 6th, and it is possible to reach agent2 only through ip. The installation in the samba settings on the 6th machine of the hard-core netbios name = Agent6 did not help, the machine still periodically responds to Agent2. In this case, the fact which agent we get to the balls depends on the observer’s computer, that is, at the same time this problem is not observed from all clients. Accordingly, 2 questions.

  1. Is this possible due to the fact that the new typewriter squeezed static ip address?

  2. Are there any solutions without installing static ip on machines? Or just any solution to the problem.

  • one
    Is the name exactly where it is not lying around? grep -ri Agent2 /etc doesn't give anything interesting? Is the search for hosts on the network using only netbios or is the DNS server also responding to queries with the same names? - Fat-Zer 2:42 pm

0