Hello, I’m relatively new to RouterOS. I have had a private server I have used for file hosting and game servers for a long time now. I recently picked up a mikrotik hEX S to use in my network. I’ve set up my port forwarding same as I have on previous routers but I seem to have no outside communication for any of the server programs launched. I can use remote desktop connect through the opened ports and redirected ports fine but none of the file sharing or game server hosts can communicate with hosting networks or clients. I am unsure if there is a way to export my current settings for someone to view but it’s currently set to;
open tcp port 3389 for remote desktop to one computer
open tcp port 3388 and redirect to 3389 for remote desktop to a second computer
open tcp port 3387 and redirect to 3389 for remote desktop to a third computer
open tcp port 3390 and redirect to 3389 for remote desktop to the server
open tcp ports 7770-7810,27000-27050 for file hosting and dedicated server software to the server
open udp ports 1200,3478,4379-4380,7770-7810,27000-27050 for file hosting and dedicated server software to the server
I did notice RouterOS does not appear to like the standard port formatting as written above. I had to enter them individually for each range, ie: one for 1200, separate one for 3478, another one for 4379-4380, etc. Is it a formatting issue. Is #-# not the correct way to designate a range in RouterOS? As stated everything worked correctly for the 4 remote desktop ports.
If you open a terminal connection (either ssh to router or open terminal from any of GUI), then you can create text export of complete setup by running command /export hide-sensitive file=anynameyouwish. Afterwards fetch the file to your PC, open it with text editor, optionally obfuscate remaining sensitive data (e.g. static public IP address, wifi password) and copy-paste it inside [__code] [/code] environment.
And yes, it does help to see whole config, not just part of it. Things are connected to each other in most mysterious ways
THe format of al the dstnat rules should include in-interface-list=WAN
(assuming you have a dynamic WANIP)
(if its a static fixed IP) the addition would be dst-address=fixedWANIP (and if so you want to make sure you put fake numbers or xx.xx.xx.xx on any future export shown here.
Thank you, that seems to have fixed my issue with external network connections. I am still having an issue where I cannot connect to a server side host from within the network. It will not allow a connection from anything but the external IP as it’s partially managed by steam.
Using the servers internal IP on the others though will allow connections internally but trying to connect using external IP and domain from within network does not.
This is not an issue I’ve had with other routers. Is there a setting I would need to allow internal calls to the external IP?
