Re: DHCP and Static Boxes cannot see one another
- From: "Bill Grant" <not.available@online>
- Date: Sat, 7 Oct 2006 10:47:30 +1000
If they are on different VLANs, then you usually get the same result as
if they are on different segments. Each VLAN will have its own master
browser and build its own browse list.
There are two things necessary to browse across segments.
1. You must have at least one DC. Only a DC can act as a domain master
browser and build a WAN-wide browse list.
2. The master browsers must be able to find each other across the router.
This usually requires an integrated WINS setup (ie either all machines using
the same WINS server or multiple WINS servers replicating). This allows the
special Netbios names of browsers to be resolved to IP addresses. They can
then communicate across the router. See KB150800 (not a recommended method,
but it explains the problems) and KB 188001 .
"RicNagy" <RicNagy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2170528B-2ED3-4DDF-9815-29DE65D732C4@xxxxxxxxxxxxxxxx
i know they are on different VLANS i'll have to check on the subnets. Also
in
a recent development I guess now you can only see whats in your VLAN
Ric
"Bill Grant" wrote:
Network Neighborhood displays the list built by the browser service.
The
browse list is built by LAN broadcasts. All machines should show up in
the
browse list as long as they are on the same physical segment.
If you see two separate browse lists there is something odd going on.
Are they in dfferent IP subnets? Different domains/workgroups?
The tool to debug problems with the browser service is browstat (from
the sytem tools).
"RicNagy" <RicNagy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9DEEDFDB-0043-44B9-B6C3-63950DAB5274@xxxxxxxxxxxxxxxx
This is a repost of an issue I was working and had to put on hold but I
am
now able to get back to this issue.
The question was:
We currently have boxes on our network that utilize static IP's and
boxes
that utilize DHCP. Statics are mainly our servers, development and
admin
boxes. Most of are users are dhcp unless neccesity dictates otherwise.
Currently If you look
in network neighborhood and view entire network, if your on one of the
static boxes you will only be able to see other boxes with static ip
addresses and dhcp can only see dhcp boxes. Not sure why this is. The
only
thing that had changed recently was that we went from a 172.x.x.x
network
to
a 205.x.x.x network and that was when this started per my
understanding.
Has
anyone else seen something like this?
Is this something with networking, tcp/ip, security, group policy? Any
assistance or ideas would be appreciated.
.
- References:
- Re: DHCP and Static Boxes cannot see one another
- From: Bill Grant
- Re: DHCP and Static Boxes cannot see one another
- Prev by Date: change the default ip programmatically?
- Next by Date: router issue
- Previous by thread: Re: DHCP and Static Boxes cannot see one another
- Next by thread: Central management remote eventlog
- Index(es):
Relevant Pages
|
