Re: Dropping Netbios over TCP?

From: Doug Sherman [MVP] (dsherman_at_nospam.tampabay.rr.com)
Date: 10/26/04 

Date: Tue, 26 Oct 2004 10:43:43 -0400

Since you have static IP addresses on the LAN, an lmhosts file should work.
Use Notepad to edit the lmhosts.sam file in C:\WINNT\System32\Drivers\etc,
and save it as lmhosts. Double check to make sure it is not saved as
lmhosts.txt.

Do not test this by using the ping command. Ping, http, etc are winsock
based and Windows will first look to hosts files and DNS for name
resolution. For UNC drive mappings and all other non-winsock name
resolution requestsWindows will try NetBIOS name resolution first and an
lmhosts file entry should prevent the need for a DNS query. Also, with an
lmhosts file you can use the #PRE tag to load the names into the name cache
at startup.

If the lmhosts file does not work, run ipconfig /all on the multihomed
machine and report back with the NetBIOS node type for each adapter. Node
type affects name resolution order and may account for your problem.

As a last resort, change the script to \\IPaddressof MyServer\MyShare

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Paul Kraemer" <PaulKraemer@discussions.microsoft.com> wrote in message
news:69C3DBD3-B067-444C-94F3-F69DAE5D367C@microsoft.com...
> Thanks Doug...I moved the LAN connection for the 192.168.3.1 NIC up in the
> binding order, but I still get the DNS query in the log. If I disable
> Netbios over TCP/IP, my 'net use' command no longer works.
>
> Yor posed the question earlier, but I don't know the answer....Do you know
> of anything I can do (hosts file maybe?) that would allow DNS to resolve
> names on my 192.168.3.x LAN so that I could disable Netbios over TCP/IP?
>
>
>
>
>
>
>
> "Doug Sherman [MVP]" wrote:
>
> > Try this:
> >
> > Right click My Network Places and select Properties. Click Advanced and
> > select Advanced Settings. Move the Local Area Connection for the NIC
with
> > IP address of 192.168.3.1 to the top of the binding order.
> >
> > Doug Sherman
> > MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >
> > "Paul Kraemer" <PaulKraemer@discussions.microsoft.com> wrote in message
> > news:C6C72E41-690E-4FA5-AF03-A7AD8A635202@microsoft.com...
> > > Hi,
> > >
> > > I have a Win2k pc with two network cards (NIC's). The first NIC is
used
> > to
> > > connect me to the Internet through a DSL router. I have it setup to
> > receive
> > > it's IP address/DNS info automatically. It receives an IP address in
the
> > > range 192.168.1.x. The automatically assigned default gateway for
this
> > NIC
> > > is always 192.168.1.1 and the automatically assigned DNS server is
always
> > > 192.168.1.2. My internet connection through this NIC works perfectly.
> > >
> > > The second network card is used to connect me to my office LAN. I
have
> > > assigned it a static IP address of 192.168.3.1 (where all of the pc's
on
> > the
> > > LAN also have static IP addresses in the 192.168.3.x range). I did
not
> > > assign a default gateway or DNS server for this NIC because I want the
> > other
> > > NIC to be used for getting on the internet.
> > >
> > > Anyway, when I start this pc, I run the following command in a .bat
file
> > to
> > > map a drive letter (w:) to a share on my 192.168.3.x LAN...
> > >
> > > net use w: \\MyServer\MyShare /user:MyServer\netuser password
> > /persistent:NO
> > >
> > > ...MyServer is another PC on my 192.168.3.x LAN. This command works,
but
> > > the log file in my software firewall shows that this command generates
> > both a
> > > DNS query to my DNS server (192.168.1.2) and some netbios traffic.
> > >
> > > Please correct me if I am wrong, but what I think is happening is
> > this...My
> > > 'net use' command causes the pc to try to resolve the name \\MyServer.
It
> > > tries to use DNS, but this can't work because the DNS server
(192.168.1.2)
> > > knows nothing about my 192.168.3.x LAN. This causes it to fall back
on
> > > netbios for name resolution.
> > >
> > > If I am correct in my description of what is happening, then my
question
> > is
> > > this....I thought I read somewhere that netbios name resolution in not
> > > necessary in a purely Win2k/XP environment (which mine is). Should I
be
> > able
> > > to do away with it in this situation? Is there anything I can do to
allow
> > > DNS to resolve names on my 192.168.3.x LAN if I still want to be able
to
> > use
> > > the 192.168.1.x NIC to get on the internet?
> > >
> > > Any advice will be much appreciated.
> > >
> > > Thanks,
> > > Paul
> > >
> > >
> > >
> > > --
> > > Paul Kraemer
> >
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.782 / Virus Database: 528 - Release Date: 10-22-2004
> >
> >
> > 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.782 / Virus Database: 528 - Release Date: 10-22-2004

Relevant Pages

  • Re: The specified network name is nolonger available
    ... the "The specified network name is nolonger ... > works, NetBIOS is working. ... > you can substitute server with computer if that helps your understanding. ... Edit your LMHOSTS file. ...
    (microsoft.public.win2000.networking)
  • Re: name resolution order
    ... WINS server ... A Windows computer assumes you are seeking to resolve a NetBIOS name unless ... search order becomes, cache, hosts file, DNS server, and yup - lmhosts file. ...
    (microsoft.public.win2000.networking)
  • Re: DNS and Netbios name
    ... I didn't think I was "referring to" you, JohnB. ... If using a WINS server is out of the question, your only other choice, if NetBios name resolution is a must, is to edit the LMhosts file. ...
    (microsoft.public.windows.server.dns)
  • Re: Migrating Domain: Disable Old AD Domain Using LMHOSTS
    ... the LMHOSTS file, directing the FT domain entries to another location. ... This would not typically work for DNS requests since they get answered ... Just to set a reference: I am one of the top NetBIOS ...
    (microsoft.public.windows.server.active_directory)
  • Re: unable to join computer to domain
    ... It's gotta be your lmhosts file.. ... netbios names in the remote name table. ... > - i can browse the workgroup and ping other machines by name ... > - made sure the rpc service was running ...
    (microsoft.public.windows.server.networking)