Much thanks.
I'll get cracking on that as soon as possible. I will
look at the DNS server in the medium term, and go
with the /etc/hosts for now I think.
Nice one.
--
Matt
--- Michael Brown
20 quid says it's a name resolution problem. Check all your DNS settings on both clients and servers. Ensure that forward and reverse maps exist for all machines (either in DNS or in /etc/hosts). Thanks. I thought this may be the case, but my DNS knowledge is poor. We use a DNS server at our ISP (!), and have no local servers (!). I use DHCP to configure clients, so I can't just use /etc/hosts file right? Please point me at the relevant sources for help - I don't even know where to start. I tried to setup samba as a wins server, with dns proxy, but I shouldn't think it worked. What would be the _simplest_ way to fix this? I'd be happy to use text files instead off DNS _if_ it could work with DHCP.
Two alternatives:
1. Set up /etc/hosts with an entry for the server and entries of the form 192.168.0.1 client-1 client-1.my.fake.dns.suffix 192.168.0.2 client-2 client-2.my.fake.dns.suffix 192.168.0.3 client-3 client-3.my.fake.dns.suffix 192.168.0.4 client-4 client-4.my.fake.dns.suffix 192.168.0.5 client-5 client-5.my.fake.dns.suffix for the clients (adjusted as appropriate for your IP address range). It doesn't matter that these names won't always correspond to the same client computers; the important thing is that when Samba (or anything else) tries to do a reverse name lookup on a client IP address it gets an answer immediately instead of having to wait for a DNS timeout.
2. Set up a local DNS server to claim to be authoritative for your fake DNS suffix (my.fake.dns.suffix) and your IP address range (0.168.192.in-addr.arpa). Create a DNS record for the server. You should be able to get away without creating records for the clients; when Samba tries to do a reverse name lookup the local DNS server will give an authoritative "unknown host" error and so you will not have to wait for a DNS timeout. Having said that, I would be inclined to create records anyway, because there are just too many things in Linux that seem to go slightly pear-shaped if name resolution isn't set up comprehensively.
Either way, I suggest you use a quick little script to generate all the client entries. For example:
perl -e 'for ($i=1; $i<254; $i++) { print "192.168.0.$i client$i client$i.my.fake.dns.suffix\n"; }'
will print out
192.168.0.1 client1 client1.my.fake.dns.suffix 192.168.0.2 client2 client2.my.fake.dns.suffix 192.168.0.3 client3 client3.my.fake.dns.suffix 192.168.0.4 client4 client4.my.fake.dns.suffix 192.168.0.5 client5 client5.my.fake.dns.suffix ... 192.168.0.252 client252 client252.my.fake.dns.suffix 192.168.0.253 client253 client253.my.fake.dns.suffix
HTH,
Michael
-- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com
__________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com