RPC Publishing and Internal Network routing.

I have two ISA 2006 problems I want to tear my hair out because off.

I recently upgraded my ISA 2004 Server to 2006 to be able to allow rpc over
https on the same connection since 2004 does not support basic auth fallback.

Problem 1 RPC

I have tested the rpc connection on Isa to the exchange front end server by
opening https:\\(external url)\rpc\rpcproxy.dll and I get a blank page witch
is according to the information I looked up the correct response.

However even after testing rpc publishing rule with the built in rule tester
when I test connecting to the rpc connection from the outside I get a
different message.

This seems to indicate my rule is not working properly.

I get a “The page cannot be displayed…” page.

Problem 2 Additional Internal VLAN/NETWORKS

I have 2 additional internal networks I would like Isa to route traffic to
and from.
One is a voice vlan that mostly contains VOIP Phones but also one or two
servers.
The other is a VPN that connects to another branch of mine.

My working internal network range is 10.0.0.0 mask 255.255.252.0 Default
gateway is 10.0.0.3(ISA)
The ip address ranges I want to route to is 192.0.0.0 mask 255.255.252.0
Default gateway 10.0.3.254.
And finally 192.168.0.0 mask 255.255.255.0 default gateway 10.0.0.21.

I have tried the following.

Adding the 192.0.0.0 network as an additional network in Isa under
Configuration-Networks. Then under network Rules adding a route rule between
the default internal network and 192.0.0.0. Finally I added 2 network rules
stating allow all protocols I defined from internal to 192.0.0.0 network and
another that says allow all protocols from192.0.0.0 to internal network.

Yet I cannot communicate between the networks.

Well that is it. Any and all help appreciated.

.

Relevant Pages

  • Re: Juniper Ssl Vpn
    ... out a different gateway as well (not the ISA). ... added to the Internal Network Address List then the SecureNAT Service would ... My LAN Router is the Default ... Changing the Internal Network Addresses to include this number causes ALL ...
    (microsoft.public.isa)
  • Re: Configuration error alert
    ... All of those IP Ranges have to be included in the Internal Network ... You cannot use the ISA as the Default Gtgeway for any Hosts on the LAN. ...
    (microsoft.public.isa.configuration)
  • Re: Site to Site Access on ISA Server
    ... I added the melbourne range to the internal Network and added that static ... and I am now able to Ping the vpn device in the melbourne office.. ... The internal network object definition on ISA is currently 192.168.1.0 to ...
    (microsoft.public.isa)
  • Re: New subnet with two NICs
    ... We do use a layer 3 switch and the routing is being handled with RIP ver2. ... what needs to be done on the ISA is to: ... current Internal network list. ... Internal Network Definition. ...
    (microsoft.public.isa.configuration)
  • Re: New subnet with two NICs
    ... On both subnets, each device is configured to use this layer 3 ... what needs to be done on the ISA is to: ... current Internal network list. ... Internal Network Definition. ...
    (microsoft.public.isa.configuration)
Loading