Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    2 Lan(s) network couldn't access each other.

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 2 Posters 569 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Y
      yoddp
      last edited by

      Hi, I'm so novice in network design and config. Please give me some advises.
      My problem was network .2 (192.168.2.x) couldn't connect to other network (192.168.0.1) in some address.

      Problem :
      IP 192.168.2.11 could be able to access NAS (192.168.0.111) and Server 2 (192.168.0.112) but
      couldn't access to Server 1 (192.168.0.110) or some client on this subnet (192.168.0.x).

      Client in subnet .0 (192.168.0.x) can reach to client in subnet .2 (192.168.2.x).

      All client be able to access to 192.168.1.1

      I'm so confuse, are there something wrong with route config (I didn't config any static route for this, pfSense handle it all).
      OR Is it cause by the firewall config? I have already allowed outgoing for any port on those 2 subnet (192.168.0.x and 192.168.2.x).

      Cloud you help me find what cause make this problem exist?
      com.jpg
      com.jpg_thumb

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Check the "Windows firewall" on Server 1 (192.168.0.110). If not that, check the default gateway on that host. It should be 192.168.0.121 based on your drawing.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • Y
          yoddp
          last edited by

          Thank you so much, Windows's firewall on 192.168.0.110 was blocked incoming protocol from other sub net.
          Now, I can access to 192.168.0.110 via 192.168.2.0 sub net.  ;D

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.