ISA 2006 – new subnet not working

Home Forums Server Operating Systems Windows Server 2000 / 2003 / 2003 R2 ISA 2006 – new subnet not working

Viewing 1 post (of 1 total)
  • Author
    Posts
  • Avatar
    zakir.ahmed
    Member
    #162449

    HI,

    I have configured ISA 2006 with two(2) nics; below are the network details

    Internal: 192.168.X.X/16
    External: 172.16.33.X/24
    New-Internal: 192.169.3.X/24 (just mentioned for expalining my issue, using private subnet in real environment)

    Deatils of Internal adapter of ISA:
    IP:192.168.1.1
    SM: 255.255.0.0
    GW: –
    DNS: –
    Deatils of External adapter of ISA:
    IP: 172.16.33.1
    SM: 255.255.255.0
    GW: 172.16.33.5
    DNS: 192.168.1.5

    The users in the Internal Subnet(192.168.X.X/16) are able to browse the internet using proxy 192.168.1.1:8080, but in the New-Internal subnet users are unable to access the internet.

    New-Internal can access External Subnet. (Routing is ok)
    I have also created a access rule in ISA, i am getting the below message
    The routing table for the network adapter Internal includes IP address ranges that are not defined in the array-level network Internal, to which it is bound. As a result, packets arriving at this network adapter from the IP address ranges listed below or sent to these IP address ranges via this network adapter will be dropped as spoofed. To resolve this issue, add the missing IP address ranges to the array network.
    The following IP address ranges will be dropped as spoofed:
    External: 192.169.3.0 – 192.169.3.255;
    ISA Server detected routes through the network adapter External that do not correlate with the network to which this network adapter belongs. When networks are configured correctly, the IP address ranges included in each array-level network must include all IP addresses that are routable through its network adapters according to their routing tables. Otherwise valid packets may be dropped as spoofed. The following ranges are included in the network’s IP address ranges but are not routable through any of the network’s adapters: 192.169.3.0 – 192.169.3.255;. Note that this event may be generated once after you add a route, create a remote site network, or configure Network Load Balancing and may be safely ignored if it does not re-occur.

    Please help me to resolve this.
    many thanks in advance

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.