[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

04/05/2009 at 10:47AM PDT, ID: 24296332
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.2

RRAS static routes for Routing different subnets

Asked by ArmstrongInt in Windows NT Operating System, Network Design & Methodology, Network Routers

Hi there

I have two networks connected via VPN (Cisco ASA 5505 - 5510) all setup and working.

Network A 172.16.0.0/22
Network B 172.16.100.0/22

On network A I have a server with the IP 172.16.36.240 that will need to connect to a server on Network B 172.16.40.240.

The reason I need to use these ranges it because I am using replication software (Neverfail) to replicate exchange servers (Site A - Site B) so these IP's are essentially a 2nd Network adaptor dedicated for that traffic.

Exchange A - Public Adaptor 172.16.0.240, Channel 172.16.36.240
Exchange B - Public Adaptor 172.16.100.240, Channel 172.16.40.240

The I have enabled the RRAS service on both servers as 172.16.36.240 needs a static route to connect to 172.16.40.240.

The gateway on Network A is 172.16.0.1 so I created a static route bonded to the 2nd (Channel) NIC with destination 172.16.40.240 with netmask 255.255.255.255 and gateway 172.16.0.1 and on the otherside (using Destination 172.16.36.240 and 172.16.100.1 as gateway on Exchange B).

However it doesn't seem to work, I am a little stumped as to how this can work though I am sure it can.

If anyone has come across anything similar any ideas would be appreciated.

Thanks very much

Arm
[+][-]04/05/09 12:49 PM, ID: 24072716

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]04/06/09 01:15 AM, ID: 24075163

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]04/06/09 12:03 PM, ID: 24080584

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Windows NT Operating System, Network Design & Methodology, Network Routers
Sign Up Now!
Solution Provided By: Qlemo
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20091028-EE-VQP-88 - Hierarchy / EE_QW_3_20080625