I setup a samba box this week. Works really well as a PDC but all clients pause when browsing the network neighbourhood - they seem to wait for something for about 20 seconds, then resume as normal. Log ons are fine, but log offs seem to pause for the same length (no, there's no sound file playing). Very odd. The network and hardware is all good, as we replaced SuSE 6.4 with Samba configured as PDC but with SHARE level security, with RedHat 7.2 with samba configured with USER level. Now, for some reason, a mysterious pause. Any ideas please? Thanks -- Matt __________________________________________________ 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
On Wed, 10 Apr 2002, Matt Johnson wrote:
I setup a samba box this week. Works really well as a PDC but all clients pause when browsing the network neighbourhood - they seem to wait for something for about 20 seconds, then resume as normal. Log ons are fine, but log offs seem to pause for the same length (no, there's no sound file playing). Very odd. The network and hardware is all good, as we replaced SuSE 6.4 with Samba configured as PDC but with SHARE level security, with RedHat 7.2 with samba configured with USER level. Now, for some reason, a mysterious pause. Any ideas please?
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). Michael
--- Michael Brown
I setup a samba box this week. Works really well as a PDC but all clients pause when browsing the network neighbourhood - they seem to wait for something for about 20 seconds, then resume as normal. Log ons are fine, but log offs seem to pause for the same length (no, there's no sound file playing). Very odd. The network and hardware is all good, as we replaced SuSE 6.4 with Samba configured as PDC but with SHARE level security, with RedHat 7.2 with samba configured with USER level. Now, for some reason, a mysterious pause. Any ideas please?
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).
Michael
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. Thanks -- Matt __________________________________________________ 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
On Thu, 11 Apr 2002, Matt Johnson wrote:
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
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
On Thu, Apr 11, 2002 at 11:07:58AM +0100, Matt Johnson wrote:
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.
If you go down the nameserver route in the future you might want to check out pdnsd. It might meet your needs and is a lot easier to set up then bind although not as configurable. You'll find it on Freshmeat. Anybody used pdnsd on a network of any size? I've just used it primarily as a caching nameserver for my small home network but have been pleased with it. -- Frank *-*-*-*-*-*-*-*-*-*-* Boroughbridge. Tel: 01423 323019 --------- PGP keyID: 0xC0B341A3 *-*-*-*-*-*-*-*-*-*-* http://www.esperance-linux.co.uk/ TV is chewing gum for the eyes. -- Frank Lloyd Wright
On Thu, 11 Apr 2002, Frank Shute wrote:
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. If you go down the nameserver route in the future you might want to check out pdnsd. It might meet your needs and is a lot easier to set up then bind although not as configurable. You'll find it on Freshmeat. Anybody used pdnsd on a network of any size? I've just used it primarily as a caching nameserver for my small home network but have been pleased with it.
Never had any problems with bind - it works "out of the box" as a caching nameserver and takes maybe 10 minutes to set up a private DNS zone. Michael
On Thu, 2002-04-11 at 08:45, Michael Brown wrote:
Two alternatives: ...
Third alternative: dhcp-dns --- use dynamic DNS to update your domain as people are issued DHCP leases --- bit more of a headache to set up, but cute once it's working. Cheers, Phil. -- Say no to software patents! http://petition.eurolinux.org/ |)| Philip Hands [+44 (0)20 8530 9560] http://www.hands.com/ |-| HANDS.COM Ltd. http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND
participants (4)
-
Frank Shute -
Matt Johnson -
Michael Brown -
Philip Hands