Hello all, I've been able to successfully set up a small network, using Samba as a PDC. I'm currently using the latest updated version of Fedora 7, and the latest version of Samba. I'm really new to DNS and WINS, so please excuse my ignorance if I've completely overlooked something. Perhaps you could point me in the right direction... My Samba server is set up as a domain controller, master browser, and I have it set to act as a WINS server. Everything on the client side seems to work wonderfully, except browsing. It is incredibly slow. I've set the client TCP/IP->Advanced->WINS settings to point to directly to the Samba server. All of the client machines pick up a IP and DNS server through a DSL cable modem, and not through the server (right now, I hope to change this as I go). The client is also set to use NetBIOS over TCP/IP. Now, if I manually enter a setting in the client hosts file, browsing is almost instantaneous. Without an entry in the hosts file, though, browsing slows to a crawl. I've certainly got a DNS issue going on here. To work around this, I had to put a entry in the hosts file on every single client in the network. I'm suspecting that I shouldn't have to do this, and DNS will handle IP address resolution for the server. All of our client machines are win2k at the moment. My question is, is setting the server to act as a WINS server (with clients WINS server pointing to the server) enough, or do I need to enable DNS on top of that, and point clients to the server for DNS? Or, more generally, how have you folks set up your server/client networks to use your server as a WINS server... and have any of you experienced very slow network browsing and how have you resolved it? Thank you all, JP
Hi Steven, That's what I was suspecting, I'm sending a DNS query to the outside world, and after some hunting around through various DNS servers, it gives up and comes back empty, so then the clients have to resort to broadcast. So just having Samba act as a WINS server with the 'wins support = yes' option set isn't enough, even if the clients are specifically told that the Samba server is also a WINS server... So... I should learn a little about setting up a DNS server. Cool. Thanks again. JP On Sep 18, 2007, at 10:40 AM, Steven Whaley wrote:> I think you're correct that your problem is DNS related. From the > sound > of it you don't really have a DNS server running. Your clients have > external DNS via the cable providers DNS servers, but that's no > help for > resolving internal network names. So every time you try to browse > to a > client ARP has to run to get an IP for the network name. If you > set up > your PDC, or another machine, to do DNS things will go much > quicker, as > you've seen when you set up the host files. > > James Perry wrote: >> Hello all, >> >> I've been able to successfully set up a small network, using Samba as >> a PDC. I'm currently using the latest updated version of Fedora 7, >> and >> the latest version of Samba. I'm really new to DNS and WINS, so >> please >> excuse my ignorance if I've completely overlooked something. Perhaps >> you could point me in the right direction... >> >> My Samba server is set up as a domain controller, master browser, and >> I have it set to act as a WINS server. Everything on the client side >> seems to work wonderfully, except browsing. It is incredibly slow. >> I've set the client TCP/IP->Advanced->WINS settings to point to >> directly to the Samba server. All of the client machines pick up a IP >> and DNS server through a DSL cable modem, and not through the server >> (right now, I hope to change this as I go). The client is also set to >> use NetBIOS over TCP/IP. Now, if I manually enter a setting in the >> client hosts file, browsing is almost instantaneous. Without an entry >> in the hosts file, though, browsing slows to a crawl. I've certainly >> got a DNS issue going on here. To work around this, I had to put a >> entry in the hosts file on every single client in the network. I'm >> suspecting that I shouldn't have to do this, and DNS will handle IP >> address resolution for the server. All of our client machines are >> win2k at the moment. >> >> My question is, is setting the server to act as a WINS server (with >> clients WINS server pointing to the server) enough, or do I need to >> enable DNS on top of that, and point clients to the server for DNS? >> Or, more generally, how have you folks set up your server/client >> networks to use your server as a WINS server... and have any of you >> experienced very slow network browsing and how have you resolved it? >> >> Thank you all, >> JP > > -- > Puryear Information Technology, LLC > Baton Rouge, LA * 225-706-8414 > http://www.puryear-it.com > > Visit http://www.puryear-it.com/pubs/ebooks/ to download your free > copies of: > > "Best Practices for Managing Linux and UNIX Servers" > "Spam Fighting and Email Security in the 21st Century" >
Hi Ed, No - no local DNS server. I'll try what you suggested and see if I can run bind on the server machine. I kind of blindly assumed that setting 'wins support = yes' would magically do what I needed... Thanks, JP On Sep 18, 2007, at 10:45 AM, Ed Kasky wrote:> At 07:30 AM Tuesday, 9/18/2007, James Perry wrote -=> >> My question is, is setting the server to act as a WINS server (with >> clients WINS server pointing to the server) enough, or do I need to >> enable DNS on top of that, and point clients to the server for DNS? >> Or, more generally, how have you folks set up your server/client >> networks to use your server as a WINS server... and have any of you >> experienced very slow network browsing and how have you resolved it? > > Do you have local DNS on your network? If not, you might look into > running a bind on the same machine. I have a small internal > network with almost the same setup and I run bind for DNS. Works > just fine. > > You may already have it installed - try > #rpm -qa | grep bind > and see what's installed. You should have a number of rpms's > installed already. > > If so, then you need to configure your zones, etc. and start the > daemon. Of course, that is no small job if you haven't done it > before but here are lots of How To's available... > > HTH > > Ed > > . . . . . . . . . . . . . . . . . . > Randomly Generated Quote (230 of 1270): > "When we got into office, the thing that surprised me the most was > that things were as bad as we'd been saying they were." > --John F. Kennedy >
I think you're correct that your problem is DNS related. From the sound of it you don't really have a DNS server running. Your clients have external DNS via the cable providers DNS servers, but that's no help for resolving internal network names. So every time you try to browse to a client ARP has to run to get an IP for the network name. If you set up your PDC, or another machine, to do DNS things will go much quicker, as you've seen when you set up the host files. James Perry wrote:> Hello all, > > I've been able to successfully set up a small network, using Samba as > a PDC. I'm currently using the latest updated version of Fedora 7, and > the latest version of Samba. I'm really new to DNS and WINS, so please > excuse my ignorance if I've completely overlooked something. Perhaps > you could point me in the right direction... > > My Samba server is set up as a domain controller, master browser, and > I have it set to act as a WINS server. Everything on the client side > seems to work wonderfully, except browsing. It is incredibly slow. > I've set the client TCP/IP->Advanced->WINS settings to point to > directly to the Samba server. All of the client machines pick up a IP > and DNS server through a DSL cable modem, and not through the server > (right now, I hope to change this as I go). The client is also set to > use NetBIOS over TCP/IP. Now, if I manually enter a setting in the > client hosts file, browsing is almost instantaneous. Without an entry > in the hosts file, though, browsing slows to a crawl. I've certainly > got a DNS issue going on here. To work around this, I had to put a > entry in the hosts file on every single client in the network. I'm > suspecting that I shouldn't have to do this, and DNS will handle IP > address resolution for the server. All of our client machines are > win2k at the moment. > > My question is, is setting the server to act as a WINS server (with > clients WINS server pointing to the server) enough, or do I need to > enable DNS on top of that, and point clients to the server for DNS? > Or, more generally, how have you folks set up your server/client > networks to use your server as a WINS server... and have any of you > experienced very slow network browsing and how have you resolved it? > > Thank you all, > JP-- Puryear Information Technology, LLC Baton Rouge, LA * 225-706-8414 http://www.puryear-it.com Visit http://www.puryear-it.com/pubs/ebooks/ to download your free copies of: "Best Practices for Managing Linux and UNIX Servers" "Spam Fighting and Email Security in the 21st Century"
At 07:30 AM Tuesday, 9/18/2007, James Perry wrote -=>>My question is, is setting the server to act as a WINS server (with >clients WINS server pointing to the server) enough, or do I need to >enable DNS on top of that, and point clients to the server for DNS? >Or, more generally, how have you folks set up your server/client >networks to use your server as a WINS server... and have any of you >experienced very slow network browsing and how have you resolved it?Do you have local DNS on your network? If not, you might look into running a bind on the same machine. I have a small internal network with almost the same setup and I run bind for DNS. Works just fine. You may already have it installed - try #rpm -qa | grep bind and see what's installed. You should have a number of rpms's installed already. If so, then you need to configure your zones, etc. and start the daemon. Of course, that is no small job if you haven't done it before but here are lots of How To's available... HTH Ed . . . . . . . . . . . . . . . . . . Randomly Generated Quote (230 of 1270): "When we got into office, the thing that surprised me the most was that things were as bad as we'd been saying they were." --John F. Kennedy