[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1275
  • Last Modified:

Super scope problems

I am trying to setup a super scope on windows 2008 R2 server. I have the main scope (scope 1) working no problem. The second scope (scope 2) gives out the ip but won’t let the devices get to internet.
This my settings scope 1 range 192.168.0.1 to 192.168.0.254 with some exclusions.
scope 2 range 192.168.1.1 to 192.168.1.254
Subnet is 255.255.255.0
Gateway is 192.168.0.253
Note the server ip is static with 192.168.0.2 and on same nic 192.168.1.2 subnet 255.255.255.0 gateway 192.168.0.253
Under scope options I have on scope 1
003 router 192.168.0.253
005 Name Servers 192.168.0.2, 192.168.0.253
006 DNS servers 192.168.0.2, 192.168.0.253

Under scope options I have on scope 2
003 router 192.168.0.253
005 Name Servers 192.168.0.2, 192.168.0.253
006 DNS servers 192.168.0.2, 192.168.0.253
I can ping from server 192.168.0.2 to a ip 192.168.1.7 on scope 2 and the pc on 192.168.1.7 can ping server 192.168.0.2 but can’t ping 192.168.0.253. pc can browse server by \\server\apps no problem just can’t get out what am I missing?
one note on the pc ip 192.168.1.7 subnet 255.255.255.0 gateway 192.168.0.253. I wonder if should put put under router 192.168.1.2 (server second ip) that would make pc gateway 192.168.1.2
0
Soupbone79
Asked:
Soupbone79
  • 3
  • 2
1 Solution
 
convergintCommented:
The whole purpose of a gateway is to help devices on one subnet get out to another.  So scope 2 that has ranges in the 192.168.1.x will need a gateway also in the 192.168.1.x range.  So yes in theory if you add a second gateway on the server at 192.168.1.2 and setup the gateway in DHCP to also be the same then it should work.
0
 
Soupbone79Author Commented:
I am going to change the router setting to 192.168.1.2 when i get on site today and see. On all the stuff I read about super scopes they make it sound so easy and it does all of it for you. they left a lot of stuff out.
0
 
Soupbone79Author Commented:
I went on site today and tried many different settings with no luck, scope 1 still working but scope 2 only works internally. I can ping server ip’s not the internet gateway, so no cloud connect. I even tried to do another scope (3) under the super scope and manually set on pc the settings of ip 192.168.2.56 , sub mask 255.255.255.0 gateway 192.168.2.1 (server 3rd ip) and dns 192.168.0.253 (internet gateway) 2nd dns 192.168.0.2 (server 1st ip) but no good still can’t ping 192.168.0.253.  This thing is making my head hurt.
0
 
convergintCommented:
I just noticed something I missed and I apologize for this oversight. 192.168.0.253 is your router and 192.168.0.2 and 192.168.1.2 are actually your server IPs.  Unless you setup routing on your server itself, it won't route to the other subnets.  I'm assuming that 192.168.0.253 is a layer 3 switch?  If so, just configure another ip address on that switch vlan with 192.168.1.253 and change the scope 2's gateway to 192.168.1.253.
0
 
Soupbone79Author Commented:
I got it working by dumping the superscope soulution and do a supernet with the server 2008 DHCP deleting the second ip and changing the subnet from 255.255.255.0 to 255.255.254.0 and doing a range from 192.168.0.5 to 192.168.1.254. All one gateway.
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now