***********************************

When you super scope, you are essentially telling the DHCP server that, if it run's out of IPs in one scope, it can use IPs from another scope. For example:

<all masks are 255.255.255.0>

DHCP_Srv

Scope1 and Scope2 are combined in a superscope.

When DHCP_Srv runs out of IPs in the 192.168.0.0 subnet (scope1), it will begin issuing IPs from the 192.168.1.0 subnet (scope2).

Other than using reservations, you will have no control over which subnet a given client receives its IP from. So some clients will end up on subnet 192.168.1.0 and some will end up on subnet 192.168.2.0. This means you will have all the same problems as with any other LAN with more than one subnet.

1) In this case, DHCP_Srv is configured to act as a router and the client's have been passed the proper Default Gateway. So you should have IP connectivity between the subnets, using IP addresses.

2) However, because I have made no provision for name resolution (the default broadcast resolution won't work across most routers), you will not be able to make connections, using names. The solution is to provide some other form of name resolution (WINS, DNS, lmhosts, hosts).

3) On top of this, if you want to provide browsing (e.g. Network Neighborhood) between these subnets, you will need to implement an NT domain, using single homed machines for the PDC and all potential SMBs.

***********************************