Hi all,
Nat routing between two independent lan networks does not work.
Basically, port forwarding does not work for an unknown reason.
Network configuration and goal
-----------------------------------------
The two networks have their own connection to the internet using a ADSL router.
Internet <--> Router R1 192.168.1.1 <-> 192.168.1.X LAN1
Internet <--> Router R2 192.168.2.1 <-> 192.168.2.X LAN2
Each lan has its own adsl router and connection to the internet.
There is no physical link between the two lans.
The general goal is to make the machine 192.168.1.200 available to the lan 192.168.2.X:
192.168.1.200 -> 192.168.2.11 smb file sharing port 445; 192.168.1.200 initiates the connection
192.168.2.11 -> 192.168.1.200 unkown port (printing); 192.168.2.11 initiates the connection
The only possible traffic between LAN1 and LAN2 should be those two connections:
we do not want to put them in the same LAN.
Current (non working) solution
----------------------------------------
We use a NAT internet router R3 (TPLINK TL-WR741ND)
192.168.1.X LAN1 <--> 192.168.1.254 WAN IP Nat router R3 LAN IP 192.168.2.254 <--> 192.168.2.X
Connection from LAN1 to 192.168.1.200 works fine using routing rules 192.168.1.X -> 192.168.2.254 in R2.
We use port forwading to let 192.168.1.200 connect to 192.168.2.11, using the PF following rule in R3:
External port 445 Internal Port 445 LAN IP 192.168.2.11
Problem
-----------
The problem is that, from a computer in LAN1, the cmd 'telnet 192.168.1.254 445' does not work.
The cmd 'telnet 192.168.2.11 445' from LAN2 works (port 445 is opened on machine 192.168.2.11).
Defining 192.168.2.11 as the dmz target results in the same behaviour ('telnet 192.168.1.254 445' from LAN1 does not work).
Any idea why port forwading is not working in this configuration?
Thanks,
Steven.
Nat routing between two independent lan networks does not work.
Basically, port forwarding does not work for an unknown reason.
Network configuration and goal
-----------------------------------------
The two networks have their own connection to the internet using a ADSL router.
Internet <--> Router R1 192.168.1.1 <-> 192.168.1.X LAN1
Internet <--> Router R2 192.168.2.1 <-> 192.168.2.X LAN2
Each lan has its own adsl router and connection to the internet.
There is no physical link between the two lans.
The general goal is to make the machine 192.168.1.200 available to the lan 192.168.2.X:
192.168.1.200 -> 192.168.2.11 smb file sharing port 445; 192.168.1.200 initiates the connection
192.168.2.11 -> 192.168.1.200 unkown port (printing); 192.168.2.11 initiates the connection
The only possible traffic between LAN1 and LAN2 should be those two connections:
we do not want to put them in the same LAN.
Current (non working) solution
----------------------------------------
We use a NAT internet router R3 (TPLINK TL-WR741ND)
192.168.1.X LAN1 <--> 192.168.1.254 WAN IP Nat router R3 LAN IP 192.168.2.254 <--> 192.168.2.X
Connection from LAN1 to 192.168.1.200 works fine using routing rules 192.168.1.X -> 192.168.2.254 in R2.
We use port forwading to let 192.168.1.200 connect to 192.168.2.11, using the PF following rule in R3:
External port 445 Internal Port 445 LAN IP 192.168.2.11
Problem
-----------
The problem is that, from a computer in LAN1, the cmd 'telnet 192.168.1.254 445' does not work.
The cmd 'telnet 192.168.2.11 445' from LAN2 works (port 445 is opened on machine 192.168.2.11).
Defining 192.168.2.11 as the dmz target results in the same behaviour ('telnet 192.168.1.254 445' from LAN1 does not work).
Any idea why port forwading is not working in this configuration?
Thanks,
Steven.
Facebook
Twitter
Instagram