I hope you can give me some hints on how to find the reason for the following behaviour. I'll start googling around right now, but I can't test it whatever turns out within the next 8 hours. Thanks in advance!
Imagine a small network class C (192.168.1/24).
1) Suse 10.1 Server running named, dhcpd, squid, apache2, MySql, vsftpd. Firewall is open for dhcp, named, squid, apache2, vsftpd, ICMP, ssh. Basic task for now: Serve fixed IP adresses based on MAC Adress, but using DHCP mechanism.
2) Different Client PCs using Win2K, WinXP, Suse9.1, Suse9.3, Suse10.0 should get IPs and network settings from Server, basically stating that Server is also the DNS server.
Now:
3 WinXP SP2 Clients, 1 Win2K SP4 Client, 1 Suse9.1 Client, 1 Suse9.3 Client work as expected - they get their IP, their network settings and can resolve local and outer names to IPs using the Server.
1 Suse9.3 Client, 1 Suse10.0 Client get IP and network settings and can ping around to inner and outer IPs, all settings were perfectly set, but name resolution does not work, and pinging the Server by IP returns "icmp host unreachable". Pinging the clients from the Server works perfectly.
I've heard about quirks with winbind and nscd, but not with dhcpcd and nscd, but anyway I'll try to remove nscd from the machines and see if it works then. It wouldn't explain the ping result from above, anyway.
Any further suggestions? Thank you very much, it's extremely appreciated. |
