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

    Issues with Peachtree

    Scheduled Pinned Locked Moved General pfSense Questions
    9 Posts 3 Posters 2.7k 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.
    • R
      rfischer1984
      last edited by

      Yes I installed a pfsense router on the network here, and peachtree keeps getting the error that the serial number is already in use. Then when i go back to the old firewall it starts working again.  What could possibly be the issue here?  Thanks

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

        Are you talking about this:
        http://en.wikipedia.org/wiki/Peachtree_Accounting ?

        Steve

        1 Reply Last reply Reply Quote 0
        • R
          rfischer1984
          last edited by

          Yes it is actually going by the name of sage 50 but yes that is the program, its an accounting software. This has me stumped at the moment. I cannot figure out why its not allowing anyone to login.  It is hard to figure it out because they need to access the software and it makes it difficult to really troubleshoot it.

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

            Hmm. Hard to say how pfSense could be causing it. I can only think you have several connections being opened and they are sending the same serial number. Do you have multi-WAN?

            What is the topology of Peachtree? Are your local users unable to logon to your local server or are they each making connections to some remote authentication server?

            I'd check whatever Peachtree/Sage support exists to be honest. You can't be the first person to experience this.

            Steve

            1 Reply Last reply Reply Quote 0
            • R
              rfischer1984
              last edited by

              Well, I wouldnt think we would be the first to experience it. I honestly don't know why it wouldnt work with pfsense, it works with the other firewall just fine. Everything else works just fine with pfsense.. The server where the data files are located works just fine, never has that error, so i am guessing that there is some problem communicating with the server. I just dont know why it would be blocking anything locally…I really would like to solve this problem. It is not the hardware or anything either.  It is on a supermicro mini-itx server board, and I even have a dual nic card installed as well. And it is not multi-Wan either. I will be doing that in the future. But right now it is not.  Thanks

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

                pfSense can't block anything on the LAN, since LAN traffic goes nowhere near it. It does sound however like there may be some Internet check going on - have you customised the LAN interface rules (ie, is it anything other than allowing all outbound traffic)?

                1 Reply Last reply Reply Quote 0
                • R
                  rfischer1984
                  last edited by

                  @Cry:

                  pfSense can't block anything on the LAN, since LAN traffic goes nowhere near it. It does sound however like there may be some Internet check going on - have you customised the LAN interface rules (ie, is it anything other than allowing all outbound traffic)?

                  I never did anything to the lan rules. I have traffic shaper enabled. Everything is default settings. This is the first time I used the embedded version, but I wouldnt think that would have an affect on it.

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

                    Before you launch the application the next time, run up Wireshark first (on the PC running the application) and start a packet capture. Then launch the application and once the error appears stop the packet capture. The packet capture may help you work out what's causing the error (it may be useful to compare it with a capture done when the application works).

                    1 Reply Last reply Reply Quote 0
                    • R
                      rfischer1984
                      last edited by

                      @Cry:

                      Before you launch the application the next time, run up Wireshark first (on the PC running the application) and start a packet capture. Then launch the application and once the error appears stop the packet capture. The packet capture may help you work out what's causing the error (it may be useful to compare it with a capture done when the application works).

                      Thank you, I will try that when i get the chance.  I will see what errors i get.

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