Jump to content

Recommended Posts

Posted

So we had 1000 addresses and we are maxing out so we have been given an additional range by SWGfL of 4000 addresses.

 

We don't want to have to move all our fixed devices to the new range so SWGfL have done whatever on the router so the two ranges can talk to each other.

 

Looking at creating a DHCP superscope and just wondered if anyone has one? If so here's some questions:

 

1) Does the DHCP server need an IP on each subnet?

 

2) What DNS should the second range provide? I assuming it's the DC IP as normal or do I have to give my DCs second IPs as well.

 

 

3) Any traffic crossing subnets, and there will be a lot as the data server is on the smaller subnet, will need to be passed through the router right? Will that cause a bottleneck at all?

Posted

Small update.

 

The scope is delivering IP addresses and I can go on to internet and ping the clients on the other subnet.

 

But I am unable to rdp or network browse to clients on the other subnet.

 

Is that a router thing or something else?

Posted
So we had 1000 addresses and we are maxing out so we have been given an additional range by SWGfL of 4000 addresses.

 

We don't want to have to move all our fixed devices to the new range so SWGfL have done whatever on the router so the two ranges can talk to each other.

 

Looking at creating a DHCP superscope and just wondered if anyone has one? If so here's some questions:

 

1) Does the DHCP server need an IP on each subnet?

 

2) What DNS should the second range provide? I assuming it's the DC IP as normal or do I have to give my DCs second IPs as well.

 

 

3) Any traffic crossing subnets, and there will be a lot as the data server is on the smaller subnet, will need to be passed through the router right? Will that cause a bottleneck at all?

 

1) You shouldn't need multiple IPs unless the router doesn't have the ability to route between the two ranges, if you are using a flat network then it should just work

2) It can use the default DNS ips, worst comes to worse it'll route via the router the DNS request

3) Yes it will go via the router, you can get around this by issuing your servers with additional IP addresses on the other subnet and the subsequent DNS entries

Posted
Small update.

 

The scope is delivering IP addresses and I can go on to internet and ping the clients on the other subnet.

 

But I am unable to rdp or network browse to clients on the other subnet.

 

Is that a router thing or something else?

 

You'll need to get the ISP to add some additional routing information to the router's routing table to avoid it bouncing the requests out and back in again.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...