>>>>> "JH" == Jeffrey Hawkins <[EMAIL PROTECTED]> writes:

    JH> You can't suppress this Name Server Request via DIALD, because this
    JH> would cause the Name Service Request you want to be inhibited.

But why should the windows box be generating a Name Sever request at all?  If
I have a hosts file and an lmhosts file containing the names of all the nodes
on my home network, what could it possibly be looking for?  I understand that
it might want to generate packets in order to its browsing and broadcasting
but why a name server packet?

    JH> Instead of configuring your Windows Machines to point externally for
    JH> DNS.  Set the only DNS Server Address on the Windows Machines to your
    JH> Linux Machine.  What is happening is that the Windows Machines are
    JH> trying to perform Name Resolutions, which DNS is part of the Name
    JH> Search Mechanism.

Eventually I will set up a caching name server on my linux box.  In the
meantime the windows boxes need the address of my remote ISP name server.
However, with a properly populated hosts and lmhosts file, it should be able
to resolve all internal addresses without querying any name server at all,
no?  It should only attempt to contact a name server when it cannot resolve a
name!

    JH> Put the Remote DNS Servers in your /etc/resolv.conf file on your
    JH> Linux Machine.  Your resolv.conf file should look something like:

    JH> search DOMAIN.COM nameserver xxx.xxx.xxx.xxx nameserver
    JH> xxx.xxx.xxx.xxx

    JH> DOMAIN.COM should be the Domain Name of your ISP, followed by the IP
    JH> Addresses of the Name Servers for you ISP.

    JH> If the Search Line contains your the "localdomain" or your Local
    JH> Domain Name, then remove it....

    JH> Are your LMHOSTS and HOSTS Files correct on your Windows Machines for
    JH> the Systems in your Network ?

    JH> If they are correct, you might have to create a Local Domain, with
    JH> your Linux System as the DNS Server, and your Windows Systems as
    JH> Clients.  As I stated in an earlier e-mail, I had a similar situation
    JH> with the Home Network.  Since I created a Local Domain, I don't see
    JH> this type of DNS Requests going outside my Network.  However, it
    JH> might be a coincidence with some of the other changes I have
    JH> performed.

    JH> Try the changes to resolve.conf and the Windows DNS Settings, as well
    JH> as, verify the HOSTS and LMHOSTS Files, before you try the things
    JH> discussed in the last paragraph...

Hmmmm.  What I have already done is create my own private domain
('jnchome.com') using the RFC set of private addressed (192.169.0.x).  My
resolv.conf contains:

        search jnchome.com 
        nameserver x.x.x.x
        nameserver x.x.x.x

Each windows machine lists all the nodes on the 192.168.0.x network in both
the hosts and lmhosts file.  The netbios names configured in the windows
networking properties matches the names in the hosts and lmhosts file.  I
_think_ I have this all done properly and, sure enough, network browsing
works across the windows machines (samba to be installed shortly) and pinging
works every which way.  My one outstanding issue, I think, is the friggin
unexpected udp packet triggering diald.

What have I missed?



-- 
Jake Colman                     

Principia Partners LLC                  Phone: (201) 946-0300
Harborside Financial Center               Fax: (201) 946-0320
902 Plaza II                           Beeper: (800) 505-2795
Jersey City, NJ 07311                  E-mail: [EMAIL PROTECTED]
                                       E-mail: [EMAIL PROTECTED]
                                          web: http://www.ppllc.com

"Every time I think I've idiot-proofed something someone comes up with a
better idiot"

-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to