Accessing the internet with forefront after subnet change.
I change my subnet from 255.255.255.0 to 255.255.254.0 to allow more IPs. My old range is 192.168.1.0 - 192.168.1.254.
The new range is 192.168.0.0 - 192.168.1.254. The 192.168.1.x computers with the new subnet mask can still access the internet through Microsoft Forefront. The 192.168.0.x computers can not access the internet.
I added 192.168.0.1 - 192.168.1.254 to the internal address range in forefront but still no access. I also changed the mask on the internal network card on Forefront
Microsoft Server OSMicrosoft Forefront ISA ServerDHCP
Last Comment
Chris
8/22/2022 - Mon
Chris
you will need to make sure the routing and networking is up to date on the TMG/ISA server as well so that the new network range is configured as being internal otherwise anything in the 192.168.0.0/24 subnet will be considered as external and dropped
for TMG if you go to the networking container and then on the networks Tab get the properties of the Internal Network and check on the Addresses Tab of the properties to make sure your new subnet is present or add
then check the routing tab and make sure the routing is up to date
If you have a standard two legged TMG setup then you will need to add the route via "route add" first to make sure the static route is correct and then TMG should pick it up
Biofilminc
ASKER
It looks like it may be because my DNS server was not yet using the same subnet. Anything else I need to worry about with changing subnets?
for TMG if you go to the networking container and then on the networks Tab get the properties of the Internal Network and check on the Addresses Tab of the properties to make sure your new subnet is present or add
then check the routing tab and make sure the routing is up to date
If you have a standard two legged TMG setup then you will need to add the route via "route add" first to make sure the static route is correct and then TMG should pick it up