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

    Outlook Email Can't send & receive for Windows 7\.

    Scheduled Pinned Locked Moved Off-Topic & Non-Support Discussion
    18 Posts 6 Posters 7.8k 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.
    • G
      gunan
      last edited by

      i m using PFsense 1.2.3-RELEASE. When i use windows XP no problem but when i install Win 7 i can't send & receive for my outlook 2003. Any Solution..

      Need Help….

      1 Reply Last reply Reply Quote 0
      • JackLJ
        JackL
        last edited by

        gunan,

        Before anything, check the possibility of updating your pfSense to version 2.0.1: http://doc.pfsense.org/index.php/Upgrade_Guide

        Are you sure that the default gateway of his season Win7 is the same pfSense you stand with WinXP? It would not be releasing a lack of access rule for the season Win7 on "Firewall-> Rules-> Lan"?

        []`s
        Jack

        Treinamentos de Elite: http://sys-squad.com
        Soluções: https://conexti.com.br

        1 Reply Last reply Reply Quote 0
        • G
          gunan
          last edited by

          hi ,

          I will check the firewall rules for win 7. If i update to version 2.0 all my data will be remain or i need to reconfigure back?

          Thanks for your support…

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            @gunan:

            If i update to version 2.0 all my data will be remain or i need to reconfigure back?

            http://doc.pfsense.org/index.php/Upgrade_Guide

            1 Reply Last reply Reply Quote 0
            • N
              nearones
              last edited by

              @gunan:

              hi ,

              I will check the firewall rules for win 7. If i update to version 2.0 all my data will be remain or i need to reconfigure back?

              Thanks for your support…

              Sorry for peaching myself inside, Please do not try to upgrade PFsense Please install 2.0 version fresh and recreate all rules, cause upgrading may malfunction ur pfsense and rules too. I had a very bad experince of upgrading.
              Even after installing fresh 2.0 ver. do not use 1.2.3 ver xml file, make is fresh.

              1 Reply Last reply Reply Quote 0
              • G
                gunan
                last edited by

                JackL

                Please refer to my attachment for the firewall>>rules>>Lan

                [firewall rules lan.xls](/public/imported_attachments/1/firewall rules lan.xls)

                1 Reply Last reply Reply Quote 0
                • JackLJ
                  JackL
                  last edited by

                  @gunan:

                  I will check the firewall rules for win 7. If i update to version 2.0 all my data will be remain or i need to reconfigure back?

                  Read carefully the instructions in the guide: http://doc.pfsense.org/index.php/Upgrade_Guide

                  You can also take a look at this blog we created in the text of the Brazilian community with steps and best practices when upgrading your system (to avoid problems reported by nearones, for example): http://www.pfsense-br.org/blog/2012/02/passos-e-boas-praticas-na-hora-de-atualizar-o-sistema/

                  []`s
                  Jack

                  Treinamentos de Elite: http://sys-squad.com
                  Soluções: https://conexti.com.br

                  1 Reply Last reply Reply Quote 0
                  • JackLJ
                    JackL
                    last edited by

                    @gunan:

                    Please refer to my attachment for the firewall>>rules>>Lan

                    In the most casual look you can see various inconsistencies and redundancies in your rules. Some tips that can help you:

                    1. When you want to refer to your LAN, try to use the alias "LAN SUBNET" instead of description in ipv4;

                    2. You have multiple subnets? or was refer to a station when the field source 192.168.204.0/24 quotes?

                    3. Implement a firewall like 'prudent', ie, create rules only for what you want to pass on your LAN to WAN. By default, everything should always be denied.

                    4. Do you have a rule blocking connections from on high ports. However, almost every type of connection is originating from high port!

                    Review your firewall completely … Who knows, a good start would you buy the book: http://pfsense.org/book

                    []`s
                    Jack

                    Treinamentos de Elite: http://sys-squad.com
                    Soluções: https://conexti.com.br

                    1 Reply Last reply Reply Quote 0
                    • G
                      gunan
                      last edited by

                      JackL,

                      Thanks for the tips..but i m a new for PFsense and i didn't get any proper passdown for my Ex clex…i don't understand why Windows XP no issue but Win 7 got this ISsue..Please help me on this issue since i couldn't purchase new System win 7. i need to purchase few new System. i also Have few IP's for by bass Our firewall and i have used it also same. Even i disable PC's firewall also same. I really need helps on this ISSUe...

                      1 Reply Last reply Reply Quote 0
                      • JackLJ
                        JackL
                        last edited by

                        Are you sure that the "default gateway" of his station Win7 pfSense is this?

                        Use tcpdump on pfsense to know if the packets are arriving at the station Win7 firewall and what happens to them afterwards!

                        Note: Even if resolving this problem off, you still have all the inconsistencies mentioned above.

                        []`s
                        Jack

                        Treinamentos de Elite: http://sys-squad.com
                        Soluções: https://conexti.com.br

                        1 Reply Last reply Reply Quote 0
                        • G
                          gunan
                          last edited by

                          hi JackL,

                          My default getaway is : 192.168.0.1 ( my pfsense).

                          Where can i check the TCPdump?

                          1 Reply Last reply Reply Quote 0
                          • JackLJ
                            JackL
                            last edited by

                            @gunan:

                            Where can i check the TCPdump?

                            Read more about the tool TCPDump. So you will be able to understand how to use it to diagnose problems on your network:

                            • http://www.thegeekstuff.com/2010/08/tcpdump-command-examples/#more-5676

                            • http://www.freebsd.org/cgi/man.cgi?query=tcpdump&sektion=1

                            Treinamentos de Elite: http://sys-squad.com
                            Soluções: https://conexti.com.br

                            1 Reply Last reply Reply Quote 0
                            • G
                              gunan
                              last edited by

                              hi I really need help.. I cannot solve the problem…

                              1 Reply Last reply Reply Quote 0
                              • G
                                gunan
                                last edited by

                                hI aLL,

                                For this issue NO solution ???

                                i really need a help…

                                1 Reply Last reply Reply Quote 0
                                • N
                                  novacoresystems
                                  last edited by

                                  lol.. dude. Upgrade your pfsense. Case closed.

                                  1 Reply Last reply Reply Quote 0
                                  • G
                                    gunan
                                    last edited by

                                    hi,

                                    CAn i upgrade my version then restore back my current configuration setting into the new version?

                                    1 Reply Last reply Reply Quote 0
                                    • C
                                      cmb
                                      last edited by

                                      @gunan:

                                      CAn i upgrade my version then restore back my current configuration setting into the new version?

                                      http://doc.pfsense.org/index.php/Upgrade_Guide

                                      1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        Please post a complete list of your firewall rules.

                                        However I would say the only thing that could be causing this difference between XP and Win7 is either some Layer 7 filtering or Win7 clients are receiving/handling dhcp information differently.

                                        Though from the rules I can see in your screenshot (in a spreadsheet) if Win7 uses different source ports it could explain it. Why are you blocking so many source ports?

                                        Steve

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