Bryan said:
I have created a Superscope of my existing scope & a new
one that I just created.
Why? Since so many people misunderstand the purpose of the (misnamed)
"superScopes" it's likely that unless you explain then you have done this
for the wrong reason.
Superscopes SHOULD have been called "Scope Groups". A superscope
combines two (or more) ordinary scopes on the SAME segment
(broadcast domain) into one effective superscope(group.)
[Note: This is not a Microsoft choice; it was already misnamed in the RFC.]
Superscopes are ONLY NEEDED for "Multinets" -- when you have more
than one logical IP on a single segment.
I was sure I setup everything correctly but they cant ping each other.
Likely you didn't, since Ping is about "routing" and basic IP connnectivity
and has nothing DIRECTLY to do with Superscopes or DHCP servers.
(There is an indirect connection if you give our, or fail to give out, the
correct
IP settings.)
How can I get them to see each other? What setting needs to be in place
for this to happen?
Are these machines on separate segments, separated by a router? If so,
superscopes are NOT your problem.
IF so, then superscopes are still not your problem as long as the machines
are RECEIVING IP settings. In this case, the ROUTER must know about
both "subnets" OR the machines must all have a "manual route" added to
allow them to send directly to the "other subnet".
Here's the deal: A machine doesn't "know" about additional subnets on the
"same wire" so it sends such traffic (typcically) to the default gateway...
Either the gateway must forward it -- the only choice if the gateway
separates
the segments -- OR the clients must be given a route.
Again, none of this has much to do with the Superscopes except that you need
that to hand out the addresses.
Describe your routing architecture and show us your IPConfig from a machine
on each subnet, plus the default gateway between or on that subnet.
