• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 52
  • Last Modified:

Routing problem

We replaced a RV320 with an RV345. In the old router we had a routing to another network: 10.10.69.0/24 with next hop of 192.168.1.253, this worked fine.

When we enter the routing in the new RV, we can only seem to ping the 10.10.69.0 network, but our applications to the eternal network stopped worked.

We worked around this by adding the routing option to the PC’s itself, however this cannot be the solution for use with the Cisco RV345.

What can be the cause of this?
0
IT Meetjesland
Asked:
IT Meetjesland
  • 5
  • 2
  • 2
4 Solutions
 
AlanConsultantCommented:
Hi,

Things to check / try:

Have you updated the RV345 firmware to the latest edition?

Can you ping the router (default gateway) of the 10.10.69.0/24 network?

Can you ping multiple hosts in the 10.10.69.0/24 network (not just the router)?

Can you ping the device at 192.168.1.253 itself?


Thanks,

Alan.
0
 
nociSoftware EngineerCommented:
the /24 wasn't  forgotten on the route  somehow?
0
 
IT MeetjeslandAuthor Commented:
I can ping all the devices on the other network and I can ping 192.168.1.253., I get an error of I don't add the /24, so it's not forgotten. Firmware is the latest.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
AlanConsultantCommented:
Hi,

You said in your OP that:

When we enter the routing in the new RV, we can only seem to ping the 10.10.69.0 network, but our applications to the eternal network stopped worked.

Then you said just above:

I can ping all the devices on the other network and I can ping 192.168.1.253.


Those two statements appear to contradict each other, but I suspect I am not understanding what you mean?  Please can you explain / reconcile for me.


Thanks,

Alan.
0
 
IT MeetjeslandAuthor Commented:
The application on the 10.10.69.0 network is phone software called Go Connect. This software refuses to connect to the 10.10.69.0 network.

We however can ping everything from the 192.168.1.0 network to the 10.10.69.0 network and the other way around.

The Go Connect software only seemed to work again when we added the routing to the PC's itself.
0
 
nociSoftware EngineerCommented:
is the RV345 the same address as the RV320... if not you may need to change (default) gateway addresses in systems (DHPC?).
0
 
AlanConsultantCommented:
Hi,

So, just to be clear, you can ping from the machine where the 'Go Connect' software is installed (which has an IP of 10.10.69.X) to any other host (anywhere on the 10.10.69.0/24 and 192.168.1.0/24 networks) , but the 'Go Connect' software itself won't connect to any other host at all on either network?

Is that correct?

Thanks,

Alan.
0
 
AlanConsultantCommented:
Hi IT Meetjesland,

Given that what I posted above is correct, then the issue must lie entirely within the 'Go Connect' software itself.

If that is the case, probably the best way to resolve the issue is to go to their support people - they should be able to advise what you need to configure within their software to make it work (or advise you if it cannot do what you want).


Alan.
0
 
AlanConsultantCommented:
Good advice and solutions offered
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now