First, allow me to specify that I am new to the Router OS world. I am using a ‘hex S’ 5 port unit running version 6.49.11.
Before using the hex router, I had used n EdgeRouter device. While using this device, I could make multiple Tiger VNC connections to different users on a remote system.
However, now while using the hex router, I can make the first connection to user-A on the remote server successfully, but when a second session to user-B is attempted,
a connection timeout is reported.
Basically, I have no idea where to begin addressing the problem because I cannot understand why the problem should exist. This is not a new Tiger VNC environment.
As I stated previously, this action of connecting to different users on the remote server from the same host operating behind a router was successful.
Thank you in advance for any suggestions and guidance.
Question: Where was the hEX S installed? Your network or remote?
Answer: The hEX S is the router for my local home office. It is
connected to the cable modem supplied by the local cable company.
Question: What purpose does the hEX S serve in its current installation?
Answer: The router provides simple, standard connection services for
a group of 3 or 4 host machines.
Question: Can you share an export of the config and remove any sensitive information?
Answer: Below is the output from 'export' command.
[admin@RouterOS] > export
jan/07/2024 10:44:46 by RouterOS 6.49.11
software id = 0NB0-TKCV
model = RB760iGS
serial number = HEX094HV8PV
/interface bridge
add admin-mac=78:9A:18:37:2A:C0 auto-mac=no comment=defconf name=bridge
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip pool
add name=dhcp ranges=192.168.0.10-192.168.0.250
/ip dhcp-server
add address-pool=dhcp disabled=no interface=bridge name=defconf
/interface bridge port
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=ether5
add bridge=bridge comment=defconf interface=sfp1
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether1 list=WAN
/ip address
add address=192.168.0.1/24 comment=defconf interface=bridge network=192.168.0.0
/ip dhcp-client
add comment=defconf disabled=no interface=ether1
/ip dhcp-server network
add address=192.168.0.0/24 comment=defconf gateway=192.168.0.1 netmask=24
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.0.1 comment=defconf name=router.lan
/ip firewall filter
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=
established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment="defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=drop chain=input comment="defconf: drop all not coming from LAN" in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=established,related
add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=
established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat connection-state=
new in-interface-list=WAN
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" ipsec-policy=out,none out-interface-list=WAN
add action=dst-nat chain=dstnat dst-port=443 in-interface-list=WAN protocol=tcp to-addresses=192.168.0.104 to-ports=443
add action=dst-nat chain=dstnat dst-port=22 in-interface-list=WAN protocol=tcp to-addresses=192.168.0.104 to-ports=22
/ip service
set telnet disabled=yes
set ftp address=0.0.0.0/0 disabled=yes
set www address=192.168.0.0/24
set ssh address=0.0.0.0/0
set api disabled=yes
set winbox disabled=yes
set api-ssl disabled=yes
/system clock
set time-zone-name=America/Chicago
/system identity
set name=RouterOS
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
[admin@RouterOS] >
Question: How are you connecting to the remote systems? VPN?
Answer: No VPN connections. The remote server in this case is accessed primarily
via TigerVNC or simple ssh sessions. The remote server is running Arch Linux.
My local host from which I make multiple vncviewer connections is also an
Arch Linux system.
Postscript: If I attempt a second TigerVNC connection from a seperate host
within my local network, it is successful. The connection failure only occurs
when attempting to make an additional connection from the same local host.
Thank you.
Can you try running torch under Tools and plug in your IP and destination port to see what’s happening?
Is the Mikrotik receiving the public WAN IP from your modem? You can verify this in IP → Addresses
The problem has been resolved.
On the remote server, I was unaware of a firewall issue on the remote server.
Thank you for forcing me to make a deep check.
I apologize for consuming your time.
I’m glad you got it figured out!