Re: 1st time linux setup in win network

From: Richard Bell (rbell01824_at_earthlink.net)
Date: 05/12/04

  • Next message: Kyuso Cahi: "Re: tar whole windows partition"
    Date: Tue, 11 May 2004 22:18:48 GMT
    
    

    Thanks very much for your response. I've been out of town for several
    weeks and am only now getting back to this.

    As I understand your note, the behavior is expected and I should not
    worry and be happy, install Samba and all should be well.

    Thanks.

    On Sun, 02 May 2004 18:56:09 GMT, Minderbinder
    <milo_and_minderbinder@hotmail.com> wrote:

    >On Sun, 02 May 2004 14:45:16 +0000, Richard Bell wrote:
    >
    >> I'm installing a Fedora Core 1 based machine into an existing network of
    >> Windows machines.
    >> ...
    >> The existing machines are all
    >> connected to a LinkSys Router configured as a DHCP server that, in turn,
    >> provides access to the Internet for all the machines.
    >> ...
    >> From the new
    >> Fedora machine, F1, I can access the Internet via Mozilla, ping various
    >> Internet sites by name, etc. All seems well relative to the Internet.
    >> Unfortunately, from F1, while I'm able to ping the existing Win machines
    >> by IP address, I can not ping them by name (get an "unknown host" error
    >> message).
    >
    >Surely the Windows machines are resolving names "the Windows way", ie.
    >WINS, as opposed to with DNS... This is generally how Windows resolves
    >names on a LAN.
    >
    >If you need to resolve names "the internet way", for normal IP
    >applications, you need to register the names with DNS - this would
    >probably require running your own name server. This is the traditional
    >UNIX way of resolving names to IP addresses.
    >
    >If you only need to resolve names to access Windows file shares via SaMBa,
    >you probably don't need to do anything special. SaMBa usually has no
    >problem resolving WINS names on the LAN in its default configuration.
    >
    >Making linux resolve names to IP addresses more generally might be more
    >difficult. Probably your best option is to run your own DNS server, and
    >make sure that names are registered in DNS when DHCP leases are handed
    >out. OR: you may be able to make your DNS server do WINS lookups.
    >
    >Try reading this related link:
    >http://www.ale.org/archive/ale/ale-2000-11/msg00160.html
    >
    >If that seems like overkill for one linux box, you may be able to resolve
    >WINS names on just the one machine by using nmbd (a SaMBa component) as a
    >WINS proxy for transparent resolution. You'll have to research this
    >yourself (try samba.org), but it seems possible according to the nmdb man
    >page:
    >
    > In addition, nmbd can act as a WINS proxy, relaying broad- cast
    > queries from clients that do not understand how to talk the WINS
    > protocol to a WIN server.
    >
    >Cheers,
    >Minderbinder.


  • Next message: Kyuso Cahi: "Re: tar whole windows partition"

    Relevant Pages

    • Re: How to enable communication between Two different lans (subnets)/ domains 2003 server based? Ass
      ... You will also almost certainly have DNS problems running a domain behind ... server domain, with a DHCP server running on one of the 2003 boxes. ... the "inner" subnet can see the original subnet and the Internet, ... The .227 machines can see the machines on the 192.168.1.0 subnet and the ...
      (microsoft.public.windows.server.networking)
    • Re: Help with Swing Migration
      ... you can't use your server name references consistently in the ... then the IP address for the Primary DNS Server ... >> the SBSnameDC, then the IP address I should enter into the Primary DNS ... >> DNS entries for the two machines. ...
      (microsoft.public.windows.server.sbs)
    • Re: Group Policy and DNS
      ... > is our only server so it is doing DNS, DHCP, AD, etc. ... I narrowed down to a DNS issue, ... > The machines that are getting the policies ping the server ...
      (microsoft.public.win2000.dns)
    • Re: blocking annoying login popup applets
      ... > DNS server as centralized within my local network? ... Another machine is definitely not necessary for a local caching DNS ... Choice of djbdns vs. BIND: ... domains will resolve to 192.168.27.1. ...
      (comp.os.linux.networking)
    • Re: DNS not authoritative for domain
      ... I am using an internal DHCP server which is also my DNS and WINS ... I have configured a PPTP VPN using ISA to test whether or not I had an issue ... >> I can correctly resolve short and FQDN inside my domain. ...
      (microsoft.public.windows.server.dns)

    Loading