ping Proxmox hostname not working

[Interceptor]

Is there something special in Proxmox that prevents pinging the machine by hostname?
If i ping the IP everything works...

On all my other machines (that i can ping without problems) my hosts file looks like this:

127.0.0.1    localhost
127.0.1.1    BOB.skulltronics.net    BOB

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

The one Proxmox created:

127.0.0.1 localhost.localdomain localhost
10.1.0.20 3-CPO.skulltronics.net 3-CPO

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

interfaces

auto lo
iface lo inet loopback

iface enp2s0 inet manual

iface enp1s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address  10.1.0.20
        netmask  24
        gateway  10.1.0.1
        bridge-ports enp2s0
        bridge-stp off
        bridge-fd 0

The thing is that i made a SAMBA share on the host and the share only shows up if i go there by IP.
\\3-CPO does not show the shares.

 

[wolfgang]

Hi,

Do you have the firewall enabled?
This would prevent ICMP response.

Do you have a DNS server where you add the samba host (3-CPO)?

 

[t.lamprecht]

Is there something special in Proxmox that prevents pinging the machine by hostname?

No, not by default.

 

[Interceptor]

Hi,

Do you have the firewall enabled?
This would prevent ICMP response.

Do you have a DNS server where you add the samba host (3-CPO)?

I did disable the firewall on 3-CPO (Datacenter is off by default)...
I did put 3-CPO in the pfSense DNS resolver <- something i don't do for other machines and they work without it...

Ping request could not find host 3-CPO. Please check the name and try again.

I can ping another Debian in Hyper-V on a Windows machine without problems:

ping bob

Pinging bob [10.1.0.42] with 32 bytes of data:
Reply from 10.1.0.42: bytes=32 time<1ms TTL=64
Reply from 10.1.0.42: bytes=32 time<1ms TTL=64
Reply from 10.1.0.42: bytes=32 time=1ms TTL=64
Reply from 10.1.0.42: bytes=32 time<1ms TTL=64

Ping statistics for 10.1.0.42:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

I also can't ping a Windows 10 VM in Proxmox:

ping cameron

Pinging Cameron.local [fe80::c935:5def:970d:7d8c%9] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for fe80::c935:5def:970d:7d8c%9:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Where does the .local come from?
And i also can't ping Cameron by her IPv4.

 

[wolfgang]

Can the PVE host ping the other Servers?

 

[Interceptor]

Ok, after trying to ping from PVE i found out i can ping all machines except my workstation.
Then i found out that in Windows 10 the ICMP echo request is disabled by default.
There was no problem pinging the other Windows 10 machine that has Hyper-v running.
Seems like activating Hyper-V does enable ICMP echo request.

But its killing me.
\\3-CPO from two other Windows 10 PCs does show the SAMBA shares but it does not work on my workstation.
\\BOB works and has no DNS entry in pfSense.

Then i found this:
https://raspberrypi.stackexchange.c...connect-to-samba-via-hostname-from-windows-10

And \\3-CPO.local works.
I don't get it. All Windows machines are on the same release and are configured the same way.

So not a PVE problem.