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

    RDP Issues

    NAT
    9
    25
    13.7k
    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.
    • D
      DWAyotte
      last edited by

      yes

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

        Well, I'm not positive what is going on, but I know the MSS feature in PIX's is new to the 7.0 version.

        pfSense, as of right now, does not do any MSS filtering like the pix. The MSS values should remain unchanged as they pass through the pfSense. Negotiation of the MSS value should also work properly through the pfSense.

        I have to say that, since you are able to connect to the DMZ segment from the LAN segment, the pfSense is working as it should.

        That MSS fix should work. If you are running 7.2, and you've tried it the previous fix, try using the ADSM to look for the checkbox about the MSS default deny. I can't remember where it was under the ADSM, but there is a checkbox that says something like 'allow MSS exceeded values.'

        The only thing that I can surmise is that maybe a router might be throwing off the MSS.

        1 Reply Last reply Reply Quote 0
        • iorxI
          iorx
          last edited by

          Maybe this thread isn't active any more. But I could report that I have the same problem.

          RDP Client -(PPTP)-> fpSense 1.2 -(PPTP)-> Corp. Firewall –> Terminal Services / Remote Admin

          I also just get a black screen connecting to machines on the other side. But, If start one more RDP-Client and try to connect to the same host, at the same time the first started show a black screen, I can connect. Strange, but it works.

          Haven't sniffed any traffice on this one. But may the above info can help out resolve this problem.

          1 Reply Last reply Reply Quote 0
          • S
            sash
            last edited by

            @iorx:

            Maybe this thread isn't active any more. But I could report that I have the same problem.

            RDP Client -(PPTP)-> fpSense 1.2 -(PPTP)-> Corp. Firewall –> Terminal Services / Remote Admin

            I also just get a black screen connecting to machines on the other side. But, If start one more RDP-Client and try to connect to the same host, at the same time the first started show a black screen, I can connect. Strange, but it works.

            Haven't sniffed any traffice on this one. But may the above info can help out resolve this problem.

            i have the same issue like you discribed. I think its because of my VMWARE Setu, i have installed pfSense inside a VM and this coused the problem. But if you have a real machine for pfsense, i think its an pfsense fault.

            is there anything to get a fix? Does someone know where or what rdp get blcked?!

            i'll try to help as much as i can - someone hast to say me what i can do :)

            thx,

            sash

            sash(at)gmx.it

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

              I had this problem before. It was caused by the MTU on one end being to big to "fit" at the other end
              Network looks like this
              Pfsense(ethernet - mtu 1500) -> internet -> (ADSL mtu - 1462)Pfsense

              What I had to do was reduce the mtu on the ethernet side ie
              Pfsense(ethernet - mtu 1412) -> internet -> (ADSL mtu - 1462)Pfsense

              My problem was exaggerated by running the rdp through an IPSEC tunnel that adds extra overheads so you may not need to reduce your mtu so far

              1 Reply Last reply Reply Quote 0
              • P
                pinoyboy
                last edited by

                If you are on Vista (machine initiating the connection), then this is a terminal client issue, there's a regfix for this (turn off or disable TCP auto tuning).  Connecting to XP, Vista, or Windows 2003 exhibits this problem…

                1 Reply Last reply Reply Quote 0
                • S
                  sash
                  last edited by

                  i have a win2003 TS behind a pfsense Box. The connection comes from the internet from another winxp client which can't connect to my 2003 server.

                  1 Reply Last reply Reply Quote 0
                  • S
                    sash
                    last edited by

                    i'm having still that problem that i can't connect via rdp to may 2003 Server. Are there any news or suggestions what i can do? I want to fix that problem. with m0n0 i don't have the prob.

                    1 Reply Last reply Reply Quote 0
                    • S
                      sullrich
                      last edited by

                      I had no idea how to fix it but googling tcp auto scaling windows 2003 came up with:

                      http://thesystemadministrator.com/The_System_Administrator/Tips_&Tricks/Disable_TCP_Auto-Tuning_to_Solve_Slow_Network(Vista)/

                      1 Reply Last reply Reply Quote 0
                      • S
                        sash
                        last edited by

                        @sullrich:

                        I had no idea how to fix it but googling tcp auto scaling windows 2003 came up with:

                        http://thesystemadministrator.com/The_System_Administrator/Tips_&Tricks/Disable_TCP_Auto-Tuning_to_Solve_Slow_Network(Vista)/

                        thanks for your reply, but i don't think that this is the issue. It doesn'tmatter which OS the Client has. It can be an Win2003 Server, an XP Machine oder a Vista Box. Everywhere its the same Problem. I can receive some secondes every package from my Server - an then no –> the Server doenst response. if i took my m0n0 back, with the same conf --> everything work fine.

                        Firewall lets every package pass - nat is configured well. what can i do to help you ?

                        greets,

                        sash
                        sashxp@gmail.com

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