05-26-2021 06:07 AM - edited 05-26-2021 06:16 AM
Hello,
I have created quite a few port forwarding rules on our RV325 so that an external company can communicate with devices on our network.
For example: From outside, communicating on port 5150 forwards to a printer on port 9100, or on port 5151 for another printer's 9100 port.
(TCP/5150~9100; 192.168.11.214)
(TCP/5151~9100; 192.168.11.215)
These rules work perfectly well.
Now I've created another rule, in the same way. TCP/9104~9100; 192.168.10.24
This one doesn't work. At all.
Here are the tests I did:
- I changed the printer's IP address to one in the 192.168.11.x network. Didn't work.
- I tried using another outside port than 9104. Didn't work.
- I CAN telnet into the printer from inside our network on port 9100.
- A PC on the same subnet as the RV325 CAN telnet into the printer on port 9100.
Now my main question is where can I get logs of communication attempts that could tell me where these attempts fail?
Secondly I would appreciate any advice on what I might have missed.
Thanks,
Marc
Solved! Go to Solution.
05-31-2021 12:43 PM
So simply to close the topic, the issue was with the RV325 itself. It was stuck in a weird configuration state.
After rebooting the router, all rules started working without any issue.
Thanks to all who have responded.
05-26-2021 06:16 AM
The rule should work as expected the first one work - i see both the address different here :
Working one
(TCP/5150~9100; 192.168.11.214)
These rules work perfectly well.
Not working one (is this subnet different ? did the RV know how to reach this IP ?)
Now I've create another rule, in the same way. TCP/9104~9100; 192.168.10.24
check the Logs in the RV See why it failing. i do not see reason, other than IP wrong ? (guessing)
05-26-2021 06:35 AM - edited 05-26-2021 06:36 AM
The address is fine, it works internally (telnet 192.168.10.24 9100).
Also, I did try to change the printer's IP address to one in the 192.168.11.x subnet and the forwarding still fails.
Checking the logs, I see the communication coming in as "ALLOW".
05-26-2021 06:56 AM
if the Allow mneas it passed from RV Router, best is download (tcp Listner) run on your PC with same port Listening 9100, make same route toward your PC, run Wireshark and see you able to see the traffic on that port.
https://www.allscoop.com/tcp-listen.php
05-26-2021 07:34 AM
Ok so while testing, I decided to try changing one of the working rules to fit the new printer's IP address.
(TCP/9103~9100;192.168.11.214) changed to (TCP/9103~9100;192.168.10.24)
Connection worked, but it's as if my change of IP address didn't take, as the destination IP remained the same (192.168.11.214).
It's as if the changes I make do show up in the GUI but are not really applied on the router.
Yes, I did click on Save.
05-26-2021 11:03 AM
After Click Save and commit, is that all good, still have issue ?
05-26-2021 11:09 AM
I do not have "Save and commit". Only "Save", which I have clicked every time I have created a new rule.
Yes, I still have the issue.
05-31-2021 12:43 PM
So simply to close the topic, the issue was with the RV325 itself. It was stuck in a weird configuration state.
After rebooting the router, all rules started working without any issue.
Thanks to all who have responded.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide