"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&(E-Mail Removed)> wrote in
message news:%23g2hDxB$(E-Mail Removed)...
> In news:u9IDn5$%(E-Mail Removed),
> Ohaya <Ohaya@NO_SPAM.cox.net> posted their thoughts, then I offered mine
> > "Ohaya" <Ohaya@NO_SPAM.cox.net> wrote in message
> > news:uzh$dv$%(E-Mail Removed)...
> >>
> >> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in
> >> message news:u3mEmf$%(E-Mail Removed)...
> >>> The ping command does not depend on DNS. It can use any TCP/IP
> >>> based name resolution, including NetBIOS, hosts files, lmhost
> >>> files, etc.
> >>
> >>
> >> Doug,
> >>
> >> Apologies if this is a dumb question, but would we have had to
> >> specifically configure the IP address for a WINS server for NetBIOS
> >> resolution to be working on machine A?
> >>
> >> I know that we don't have anything in the hosts or lmhosts files on
> >> machine A, and I know they put in the IP address of machine B as in
> >> the settings for the DNS in network properties.
> >>
> >> Jim
> >
> >
> > Hi,
> >
> > I have to stop doing this, but I need to correct my post above.
> >
> > What I meant to ask was wouldn't we have had to specifically configure
> > machine A to point to a WINS server for NetBIOS name resolution to be
> > working?
> >
> > I know that on machine A, we put in a fixed IP address pointing to
> > machine B for the DNS, and I know that we don't have a hosts or
> > lmhosts files, and I'm pretty sure that we didn't configure any IP
> > address for WINS server (at least not on purpose).
> >
> > So, what's puzzling me is if the possible name resolution mechanisms
> > on machine A are DNS, hosts, lmhosts, NetBIOS (not in that order),
> > and we don't have any of them configured on purpose except for DNS,
> > and our DNS server on machine B is only on a private network, how is
> > the name resolution succeeding???
> >
> > Jim
>
> If machine A (if I got your topology right) is using WINS and the host on
> the external subnet is in WINS, and you are pinging by it's single host
name
> (not the whole FQDN), then yes, it's using WINS. If not, since the subnet
is
> directly connected, then it's going to broadcast on that subnet for the
> name. If using WINS, pinging a single name will check LMHOSTS first then
> WINS, but all before DNS.
>
Ace,
I should've mentioned this. When we did the ping, we used the FQDN of the
host on the external network (e.g., thehost.whatever.com).
Since we were using the external host's FQDN, would the ping still have
caused the broadcast to the external network for the name?
Or, would it only do this broadcast if we had pinged using the hostname
(e.g., thehost)?
I just thought about one other aspect about all of this that I'm starting to
wonder about that might have a bearing on all of this...
This is going to get a bit complicated, so here's what the network config
looks like:
|
|
+---- Machine A ---- Switch ----+----
| |
E | Machine B
x----+ [Domain Controller]
t |
|
+--- ExtDNS
|
|
Machine B = Domain Controller (domain name "test.foo.com")
Machine A = Member (joined to Windows domain "test.foo.com")
ExtDNS = a DNS server on external network, which does DNS for "foo.com"
Ext = a machine on the external network (ExtDNS DNS name=ext.test.foo.com)
Machine A's IP address is registered in the ExtDNS DNS server, with the name
"whatever.test.foo.com".
In other words, if you were on machine "Ext", and pinged
"whatever.test.foo.com", you would end up pinging the external interface of
machine A.
Now, we installed Machine B first, and when we installed Win2K on Machine B,
we set the machine name as "data" and the domain name as "test.foo.com". In
other words the FQDN for machine B from the internal network is
"data.test.foo.com".
I think, based on a thread i posted awhile ago, that we could've picked just
about anything for the domain name (e.g., joe.whatever.foo), but we just
happened to pick "test.foo.com".
We then installed Win2K on Machine A (the member server), and we set the
machine name as "web", and made it a member of (i.e., we joined it to)
domain "test.foo.com". In other words, the FQDN for machine A from the
internal network is "web.test.foo.com".
If you look in the DNS server on machine B, you'll see that both
"web.test.foo.com" and "data.test.foo.com" are registered, and have
"192.xx.xx.xx" IP addresses.
If you ping "web.test.foo.com" from machine B, it resolves to the internal
("192.xx.xx.xx") IP address of machine A.
If you ping "data.test.foo.com" from machine A, it resolves to the IP
address of machine B.
Again, machine B is the Domain Controller, and also has DNS Server running
on it. Machine A is a member server, joined to the domain "test.foo.com"
(whose Domain Controller is machine B).
Here's where this is going to begin sounding strange...
It just happens that on the external network, there is a Windows domain
named "foo.com".
But, remember, our machine A is joined to the domain for which machine B is
the domain controller, not that other Windows domain that is on the external
network.
I'm probably going to muddle this question, but what I'm wondering is if
there is something strange going on with the name resolution when we ping
from machine A because we just happen to pick the name of the "internal"
Windows domain such that that Windows domain's root ("test.com") is the
same as the name of the Windows domain on the external network???
Jim
Similar Threads
