Frazzle Posted January 14, 2016 Posted January 14, 2016 I need to change the IP Scope of a Windows 2008 network due to change of broadband provider. The network has 2 VLANs. I have changed IP scopes before but only on flat networks. Is it any different when VLANs are involved?
twin--turbo Posted January 14, 2016 Posted January 14, 2016 I need to change the IP Scope of a Windows 2008 network due to change of broadband provider. The network has 2 VLANs. I have changed IP scopes before but only on flat networks. Is it any different when VLANs are involved? I assume you have a L3 Switch on which the VLANS are set up. The vlan will need to be re-configerd with an IP to be the DG of the new subnet. TT 1
Frazzle Posted January 14, 2016 Author Posted January 14, 2016 I assume you have a L3 Switch on which the VLANS are set up. The vlan will need to be re-configerd with an IP to be the DG of the new subnet. TT I would assume so. Its not in my school, its a Primary down the road. I know they have cisco switches but other than knowing how to change the IP of the actual switch I dont know anything else.
twin--turbo Posted January 14, 2016 Posted January 14, 2016 Thinking on it, why do you need to change internal scopes?
Frazzle Posted January 14, 2016 Author Posted January 14, 2016 Thinking on it, why do you need to change internal scopes? Been told we need to in order to get the filtering to work.
Frazzle Posted January 14, 2016 Author Posted January 14, 2016 Am I better off getting someone in to do this?
twin--turbo Posted January 14, 2016 Posted January 14, 2016 If your asking the question, and have never used vlan routing, then i think you should be seaking some advice. There needs to be a clear reason to change the ip scope as saying filtering wont work is a little vauge . TT
Steve21 Posted January 14, 2016 Posted January 14, 2016 Only a guess here, But if it's anything like our old primaries: Without being behind a NAT device and/or private internal range (as I'm guessing the Cisco switch is the ISPs etc), a lot of the cloud based filtering will use their "private" range of IPs as the allocation out to clients. Therefore if you're on currently lets say 10.x range, and the "new" private range is 192.x they won't authorise and pick it up etc But if that is the case I'm assuming the old Switch/Router would get replaced by a new one from the new ISP, and obviously all the server side settings need changing too. Personally if you don't know what you're looking at better not to change it, as could take the network out Steve 1
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now