LinuxQuestions.org - Win7 & CentOS can't reach server by hostname

- Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)

- - Win7 & CentOS can't reach server by hostname (https://www.linuxquestions.org/questions/linux-networking-3/win7-and-centos-cant-reach-server-by-hostname-4175476018/)

Win7 & CentOS can't reach server by hostname

In short: Servers running CentOS 6 are accessible by hostname from Linux (LMDE & OpenSuse) clients, but not by Windows7 & CentOS clients.

Setup:
Firewall is pfSense-2.0.3, local servers are added in dns forwarder.
All servers & clients has the firewall as primary dns server.
Firewall name is cto.office.lan, ip 192.168.120.201
Example record in pfSense dns forwarder:

Code:

Host        Domain          IP

ctl-db0        lan          172.17.4.21

From LMDE:

Code:

ping ctl-db0

PING ctl-db0.lan (172.17.4.21) 56(84) bytes of data.

64 bytes from ctl-db0.lan (172.17.4.21): icmp_seq=1 ttl=64 time=0.165 ms

From Windows 7: (translated from Swedish)

Code:

ping ctl-db0

Could not find host ctl-db0.

BUT!

Code:

nslookup ctl-db0

Server:  cto.office.lan

Address:  192.168.120.201



Namn:    ctl-db0

Address:  172.17.4.21

Using FQDN ("ping ctl-db0.lan") it works fine.

We have several servers and it's the same for all of them so it can't be a caching issue.
All servers have static ip, all added to dns forwarder.
The server used above is a Xen guest on a separate subnet, routed via Xen host.
Other servers are on same subnet as firewalls LAN - 192.168.120.0/24 - it's the same issue with them.

I did empty both arp & dns-cache in Win7 just to make sure.
I also installed samba and started smb & nmb in CentOS-server.

what security setting is your SELinux set to? Have you tried setting SELinux to permissive? DO NOT DISABLE SELinux.

Quote:

Originally Posted by jefro (Post 5022605)

Is ping blocked?

"Using FQDN ("ping ctl-db0.lan") it works fine."

Quote:

Originally Posted by lleb (Post 5022627)

what security setting is your SELinux set to? Have you tried setting SELinux to permissive? DO NOT DISABLE SELinux.

Yes the setting is permissive - at least om some servers.
But as I can ping by HOSTNAME from Linux clients and by FQDN from Windows, SELinux can not be the problem.