DNS & Subnets

  • Thread starter Thread starter Matt M
  • Start date Start date
M

Matt M

I have 2 DNS servers configured on my 2 AD domain
servers. I have 2 subnets as well: 192.168.64.x /24
10.1.x.x /16

Until today, DNS was working properly - however, this
morning, i checked my network places and realized that 1/2
the entries were gone. This happened once before 6 months
ago, and they mysteriously came back and have been fine
since.

The PC's on the 10 side can see all the other 10's but
none of the 192's. The opposite is true for the 192's.

I have one site (default-first-site) configured for the
entire network, and the subnets are being routed via a
Cisco 3550-12G (layer 3 switch).

Why did these disapear? What can I do to prevent it?

Thanks
Matt
 
Browsing is a netbios related function. WINS handles netbios name resolution. Since we have two subnets inplace, we'll need to make sure WINS is
configured properly. First, you'll need a WINS server. Second, verify that the server running the PDC emulator service points at the WINS server and have
netbios over TCP/IP enabled. All other machines will also need to point to this WINS server and have netbios over TCP/IP enabled. In WINS manager, right
click on Active Registrations and choose find by name. Search for the domain name. In the list that is displayed, verify that there is a record for your domain
with a type 1B domain master browser. All machines will also need to be a member of the domain.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
Why would we need WINS? Every box is either XP or 2000.
Every pc is also a member of the AD domain in native
mode. And DNS functioned correctly until yesterday. I
don't feel re-enabling NetBIOS on every PC & installing a
WINS server is the appropriate answer for this.

-----Original Message-----
Browsing is a netbios related function. WINS handles
Click to expand...
netbios name resolution. Since we have two subnets
inplace, we'll need to make sure WINS is
configured properly. First, you'll need a WINS server.
Click to expand...
Second, verify that the server running the PDC emulator
service points at the WINS server and have
netbios over TCP/IP enabled. All other machines will
Click to expand...
also need to point to this WINS server and have netbios
over TCP/IP enabled. In WINS manager, right
click on Active Registrations and choose find by name.
Click to expand...
Search for the domain name. In the list that is
displayed, verify that there is a record for your domain
with a type 1B domain master browser. All machines will
Click to expand...
also need to be a member of the domain.
Thank you,
Mike Johnston
Microsoft Network Support
Click to expand...
confers no rights. Use of included script samples are
subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all
Click to expand...
responses to this message are best directed to the
newsgroup/thread from which they originated.
 
Browsing is netbios based. If you want browsing to work accross subnets, WINS is a requirement.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
I'm not sure that installing WINS is the answer. We are
running AD native mode with nothing older than Win2k sp3
on the network. Is AD not subnet aware? Why would
everything on the 192.x.x.x side not see anything on the
10.x.x.x side, but within these subnets, DNS works
correctly. Addtionally, i can ping by name across the
network as well. IS: pc1.domain.com resolves to
192.168.64.1 when pinged from 10.1.1.1 and pc2.domain.com
resolves to 10.1.1.1 when pinged from the 192 side. but
they just don't show up in My Network places.

Why would WINS fix this? What does NetBIOS have to do
with a domain running in native mode? Why do the entries
disapear? I guess if i understood the why, the fix
wouldn't seem so painfully intrusive.

Thanks
Matt
 
Correct Me if i'm wrong, but wasn't it a selling point of
the 2000 platform & AD that you wouldn't need NetBIOS or
WINS in a native environment?

Regardless, it's a poor answer by microsoft. The
assumption that every network large enough to run an AD
domain will also be homed on the same subnet is a case of
poor judgement by you guys. And the fact that you will
still need NetBIOS & WINS traffic on the network at this
point is unacceptable. I don't know much about the 2003
platform, but i hope this is an issue that was addressed.

Regards
Matt
 
In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
Correct Me if i'm wrong, but wasn't it a selling point of
the 2000 platform & AD that you wouldn't need NetBIOS or
WINS in a native environment?

Regardless, it's a poor answer by microsoft. The
assumption that every network large enough to run an AD
domain will also be homed on the same subnet is a case of
poor judgement by you guys. And the fact that you will
still need NetBIOS & WINS traffic on the network at this
point is unacceptable. I don't know much about the 2003
platform, but i hope this is an issue that was addressed.

Regards
Matt
Click to expand...

NetBIOS is not needed in a native WIn2k environment, but your shares and
printers must be published by their FQDN in Active Directory without
NetBIOS.
 
In
Kevin D. Goodknecht said:
In (e-mail address removed)


NetBIOS is not needed in a native WIn2k environment, but your shares
and printers must be published by their FQDN in Active Directory
without NetBIOS.
Click to expand...
Kevin D4 Dad Goodknecht Sr. [MVP]
Click to expand...

I agree. It's not needed. However, for Network Neighborhood, which is a
legacy feature, is based on the Browser service which requires NetBIOS. AD
is purely DNS based and doesn't require NetBIOS. All the directory services
are available via DNS. After all, a UNIX NIS directory service is exactly
the same as AD (both are X.500 based) and there is no Network Neighborhood
with Unix. Users have come to "rely" on Network Neighborhood, even in a Unix
environment, since that functionality came about using Windows client
machines, which are NetBIOS based. Hence, therefore, if you still want this
legacy service, you'll need NetBIOS support for resolution. To note, that
part hasn't changed with Windows 2003.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Thank you for the concise explination. That's all i was
really looking for. It's not a matter of me depending on
network neighborhood \ my net places so much as it is
those around me. The sudden loss of information from
that feature puzzled me more than anything else. The
functionality of my domain remains intact, and that's all
i really care about. I actually like the isolation my
clients have from each other - the less they have, the
less damage they can do.

Regards,
Matt
 
In
matt m said:
Thank you for the concise explination. That's all i was
really looking for. It's not a matter of me depending on
network neighborhood \ my net places so much as it is
those around me. The sudden loss of information from
that feature puzzled me more than anything else. The
functionality of my domain remains intact, and that's all
i really care about. I actually like the isolation my
clients have from each other - the less they have, the
less damage they can do.

Regards,
Matt
Click to expand...

No prob, and agree. But in some cases, users rely on the neighborhood since
they've been "doing this forever" and then it becomes a political issue when
the boss gets involved. With cases like that we would need to support it.

Cheers!


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top