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

    How to RDP to a computer that is connected to 2nd DHCP in 2nd network

    Scheduled Pinned Locked Moved Firewalling
    17 Posts 3 Posters 6.6k 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.
    • M
      mst
      last edited by

      WIFI router is not PFSENSE WIFI. This is just Trendnet Router hooked to 192.168.5.0 network that has 192.168.5.119 IP. This device has it's own gateway
      192.168.1.1 and it's own network 192.168.1.100-192.168.1.120

      I know I should have added another NIC to PFSENSE and name it OPT1 - then it would even be place as DMZ or whatever just WIFI to be isolated from the rest of the natework.

      1 Reply Last reply Reply Quote 0
      • M
        mst
        last edited by

        Thank You Cral Havok.

        regarding 2) Forward 3389/TCP on the WAN router/firewall to 192.168.5.119 (the WiFi router) - yes I did that rule in firewall but I am not able to RDP that server from the LAN. I cannot ping 192.168.1.0 network from 192.168.5.0

        Is there static route needs to be created ?

        MST

        1 Reply Last reply Reply Quote 0
        • Cry HavokC
          Cry Havok
          last edited by

          Try RDPing to 192.168.5.119 instead - if you've left the WiFi router doing NAT you won't be able to route to the 192.168.1.0/24 network.

          1 Reply Last reply Reply Quote 0
          • M
            mst
            last edited by

            I can RDP that (192.168.1.100) server from 192.168.5.0 LAN; however I cannot RDP from outside WAN

            MY NAT:

            WAN  TCP  3389 (MS RDP)  192.168.5.119 3389 (MS RDP)

            WAN RULES:

            TCP  *  *  192.168.5.119  3389 (MS RDP)  *

            And LAN rules:

            *  LAN net  *  *  *  *

            Still not able to rdp from WAN.

            RDP2.JPG
            RDP2.JPG_thumb

            1 Reply Last reply Reply Quote 0
            • Cry HavokC
              Cry Havok
              last edited by

              If you can RDP to the IP then it suggests that your WiFi router is only routing and not doing any NAT.  You need to change your port forward and rules to reflect the IP accessible from the 192.168.5.0/24 LAN - 192.168.1.100.

              1 Reply Last reply Reply Quote 0
              • M
                mst
                last edited by

                OK, lets forget about RDP throught WiFI router with enabled DHCP.

                Simply I added port forwarding with Firewall rules to one of my desktops(yes I have enabled RDP in Windows XP prof. adding one user to RDP list) Now I can RDP from inside LAN but from WAN no. This was pretty easy on any devices like linskys, etc…. Why the simple think does not want to work with such amazing soft firewall like PFSENSE? I want to believe that I made some "user errors" not the soft. I will be fallowing another guide example from net.

                I have to add I just simply copied rules from ENDIAN firewall that so far work pretty nice. I don't want to believe that I have to reboot PFSENSE in order to get it works after made any changes to rules. What I do wrong that simple RDP is not working?

                MST

                1 Reply Last reply Reply Quote 0
                • Cry HavokC
                  Cry Havok
                  last edited by

                  Does the pfSense host know how to route to the 192.168.1.0/24 network?  If not, how do you expect it to know how to forward packets…

                  1 Reply Last reply Reply Quote 0
                  • M
                    mst
                    last edited by

                    Should it looks like this:

                    ![Static Route.JPG](/public/imported_attachments/1/Static Route.JPG)
                    ![Static Route.JPG_thumb](/public/imported_attachments/1/Static Route.JPG_thumb)

                    1 Reply Last reply Reply Quote 0
                    • Cry HavokC
                      Cry Havok
                      last edited by

                      If 192.168.5.1 is the gateway to the 192.168.1.0/24 network then yes.  However you've previously posted that 192.168.5.119 is the gateway.

                      1 Reply Last reply Reply Quote 0
                      • M
                        mst
                        last edited by

                        I am sorry - my bed. 192.168.1.119 is IP address of WiFI Router

                        WAN –--- 192.168.5.1 PFSENSE ----192.168.1.119 Wifi Router (DHCP) Gateway 192.168.1.1 ------- WINSERVER 192.168.1.110 (Static IP)

                        Should't I be able to ping 192.168.1.1 from network 192.168.5.0 ? after setting static route to 192.168.1.0/24 ?

                        1 Reply Last reply Reply Quote 0
                        • Cry HavokC
                          Cry Havok
                          last edited by

                          What IP addresses does the pfSense host have?  What IP addresses does the WiFi router have?  Please complete the following with the real IP addresses (if IP A is your real WAN IP then replace it with WAN):

                          WAN –-- IP A (pfSense) IP B ----- IP C (WiFi) IP D --- WinServer (192.168.1.110)

                          1 Reply Last reply Reply Quote 0
                          • M
                            mst
                            last edited by

                            WAN –-- 24.13.54.21 (pfSense)  192.168.5.1 ----- 192.168.5.119 (WiFi) 192.168.1.1 --- WinServer (192.168.1.110)

                            PFSENSE has GW 192.168.5.1 and it's DHCP 192.168.5.100-192.168.5.120

                            WiFI ROuter has GW 192.168.1.1 and its DHCP 192.168.1.100-192.168.1.120

                            WiFi is simply connected to 192.168.5.0 network

                            1 Reply Last reply Reply Quote 0
                            • Cry HavokC
                              Cry Havok
                              last edited by

                              Hopefully you're confused about those gateway addresses.  The gateway address is the address of the device that connects to other networks.

                              For the pfSense host the gateway (default route) should be being set by DHCP.  There should be a static route for 192.168.1.0/24 with a gateway of 192.168.5.119.

                              For the WiFi host the gateway should be 192.168.5.1.

                              1 Reply Last reply Reply Quote 0
                              • M
                                mst
                                last edited by

                                OK so that was user error I mean my ….  :-\

                                I have been trying to experiment with static routes and after I added 192.168.5.1 to 192.168.1.1 and 192.168.5.1 to 192.168.5.119
                                my whole network went down and DHCP on WiFi router has been changed from 192.168.1.100-192.168.1.120 to 192.168.2.100-192.168.2.120

                                I am trying to figure it out why that happend.

                                Thank You for Your help. Every message make me closer to what I messed up.

                                MST

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