Subnets and host visibility

In this area of networking, I'm fairly "green" so please broach your answer
in a manner that will help me learn some new things...and I'm certainly open
to "finding" the answer if you care to point me toward the resources that
will most benefit me in relation to the situation described below:

*******************************************
We recently moved part of our organization to an offsite location (very near
HQ). In order to facilitate connectivity between locations, we set up a
point-to-point circuit via our telco. The basic setup is:

Location B (subnet 10.1.0.x) -- router -- circuit -- router -- Locaton A
(subnet 10.0.0.x)...everything's behind the firewall located at Location A,
thus Location B is simply an extension of our LAN. No servers are located
at Loc B.

The folks at Loc B authenticate to the AD domain without any problem.
Drives map fine and they can print to/access resources located on Loc A
w/out issue as well. However, when browsing in Net N'hood, they only see
hosts located on their subnet; likewise, when browsing in Net N'hood on Loc
A, only hosts from Loc A show up.

Is this a DNS issue and if so, what do I need to do to cause ALL hosts on
our network to appear in Net N'hood? If not DNS-related, what's causing
this and what can I do to resolve.

Thanks in advance for all responses!!

LJH

The reason is because broadcast name resolution doesn't
traverse routers. In order to successfully browse across
subnets you must have a WINS Server in place or staticl
lmhosts configured. The following MSKB articles should
explain:

Domain Browsing with TCP/IP and LMHOSTS Files
http://support.microsoft.com/default...b;en-us;150800

Browsing a Wide Area Network with WINS
http://support.microsoft.com/default...b;en-us;120151

"LJH" <(E-Mail Removed)> wrote in message news:
> In this area of networking, I'm fairly "green" so please broach your
> answer in a manner that will help me learn some new things...and I'm
> certainly open to "finding" the answer if you care to point me toward the
> resources that will most benefit me in relation to the situation described
> below:
>
> *******************************************
> We recently moved part of our organization to an offsite location (very
> near HQ). In order to facilitate connectivity between locations, we set
> up a point-to-point circuit via our telco. The basic setup is:
>
> Location B (subnet 10.1.0.x) -- router -- circuit -- router -- Locaton A
> (subnet 10.0.0.x)...everything's behind the firewall located at Location
> A, thus Location B is simply an extension of our LAN. No servers are
> located at Loc B.
>
> The folks at Loc B authenticate to the AD domain without any problem.
> Drives map fine and they can print to/access resources located on Loc A
> w/out issue as well. However, when browsing in Net N'hood, they only see
> hosts located on their subnet; likewise, when browsing in Net N'hood on
> Loc A, only hosts from Loc A show up.
>
> Is this a DNS issue and if so, what do I need to do to cause ALL hosts on
> our network to appear in Net N'hood? If not DNS-related, what's causing
> this and what can I do to resolve.
>
> Thanks in advance for all responses!!
>
> LJH
>
>
>

Thanks for the reply, Michael.

I should've mentioned in my original post that I do have a WINS server in
place -- it's located on the Loc A side of the pond. Do I need a WINS
server on the Loc B side as well? If not, what configuration change do I
need to make to my WINS server and/or my DHCP Server Options settings?

FYI...the router on Loc B's side of things is acting as a DHCP server for
the 10.1.0.x side of things. Also, the router settings point to my DNS
server on Loc A side (10.0.0.x). Finally, on the router, netbios-node-type
= h-node. Should I change this to m-mode?

Regards,

LJH





"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message news:(E-Mail Removed)...
> The reason is because broadcast name resolution doesn't
> traverse routers. In order to successfully browse across
> subnets you must have a WINS Server in place or staticl
> lmhosts configured. The following MSKB articles should
> explain:
>
> Domain Browsing with TCP/IP and LMHOSTS Files
> http://support.microsoft.com/default...b;en-us;150800
>
> Browsing a Wide Area Network with WINS
> http://support.microsoft.com/default...b;en-us;120151
>
> "LJH" <(E-Mail Removed)> wrote in message news:
>> In this area of networking, I'm fairly "green" so please broach your
>> answer in a manner that will help me learn some new things...and I'm
>> certainly open to "finding" the answer if you care to point me toward the
>> resources that will most benefit me in relation to the situation
>> described below:
>>
>> *******************************************
>> We recently moved part of our organization to an offsite location (very
>> near HQ). In order to facilitate connectivity between locations, we set
>> up a point-to-point circuit via our telco. The basic setup is:
>>
>> Location B (subnet 10.1.0.x) -- router -- circuit -- router -- Locaton A
>> (subnet 10.0.0.x)...everything's behind the firewall located at Location
>> A, thus Location B is simply an extension of our LAN. No servers are
>> located at Loc B.
>>
>> The folks at Loc B authenticate to the AD domain without any problem.
>> Drives map fine and they can print to/access resources located on Loc A
>> w/out issue as well. However, when browsing in Net N'hood, they only see
>> hosts located on their subnet; likewise, when browsing in Net N'hood on
>> Loc A, only hosts from Loc A show up.
>>
>> Is this a DNS issue and if so, what do I need to do to cause ALL hosts on
>> our network to appear in Net N'hood? If not DNS-related, what's causing
>> this and what can I do to resolve.
>>
>> Thanks in advance for all responses!!
>>
>> LJH
>>
>>
>>
>
>

You could get away with having one in each replication and
choosing one site to push and pull with the other site or you
could have all machines point towards 1 single WINS server.

"LJH" <(E-Mail Removed)> wrote in message news:
> I should've mentioned in my original post that I do have a WINS server in
> place -- it's located on the Loc A side of the pond. Do I need a WINS
> server on the Loc B side as well? If not, what configuration change do I
> need to make to my WINS server and/or my DHCP Server Options settings?
>
> FYI...the router on Loc B's side of things is acting as a DHCP server for
> the 10.1.0.x side of things. Also, the router settings point to my DNS
> server on Loc A side (10.0.0.x). Finally, on the router,
> netbios-node-type = h-node. Should I change this to m-mode?

Do you mean "get away with having one in each subnet?"


"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message news:(E-Mail Removed)...
> You could get away with having one in each replication and
> choosing one site to push and pull with the other site or you
> could have all machines point towards 1 single WINS server.
>
> "LJH" <(E-Mail Removed)> wrote in message news:
>> I should've mentioned in my original post that I do have a WINS server in
>> place -- it's located on the Loc A side of the pond. Do I need a WINS
>> server on the Loc B side as well? If not, what configuration change do I
>> need to make to my WINS server and/or my DHCP Server Options settings?
>>
>> FYI...the router on Loc B's side of things is acting as a DHCP server for
>> the 10.1.0.x side of things. Also, the router settings point to my DNS
>> server on Loc A side (10.0.0.x). Finally, on the router,
>> netbios-node-type = h-node. Should I change this to m-mode?
>
>

Thanks...I'm going to try and point everybody to the one WINS and see if
this works...otherwise, I'll pick up an inexpensive server and drop it in
the other location.

Cheers

LJH

"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message news:(E-Mail Removed)...
> Correct. One on each subnet.. My apology.
>
> "LJH" <(E-Mail Removed)> wrote in message news:
>> Do you mean "get away with having one in each subnet?"
>>
>>
>> "Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
>> message news:
>>> You could get away with having one in each replication and
>>> choosing one site to push and pull with the other site or you
>>> could have all machines point towards 1 single WINS server.
>
>

Correct. One on each subnet.. My apology.

"LJH" <(E-Mail Removed)> wrote in message news:
> Do you mean "get away with having one in each subnet?"
>
>
> "Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
> message news:
>> You could get away with having one in each replication and
>> choosing one site to push and pull with the other site or you
>> could have all machines point towards 1 single WINS server.