By using this web site, you agree to all terms and conditions for acceptable use.

ServiceLedger KnowledgeBase Knowledgebase Home Page > ServiceLedger > Technical | Contact Us

Search the Knowledge Base Browse by Category

ServiceLedger provides this content as-is for self help support purposes. ServiceLedger assumes no liability for any steps you take based on the directions in our knowledge base, and assumes that you have the knowledge to determine whether a given step is appropriate for your situation. Certain solutions can affect third-party software that ServiceLedger relies on or integrates with; it is your responsibility to consult with the documentation or publishers of such third-party software to understand whether any changes suggested here will have negative effects on other applications.


(T0114) How do I setup my firewall to resolve connection errors?

Would you like to...

Print this page
Email this to a friend

ServiceLedger has tested and verified versions 5.0 and higher for compatability with Windows XP Service Pack 2. Service Pack 2 is Microsoft’s best effort to date to prevent malicious network access to your Windows XP machine. Its primary feature is a new firewall that will better protect the machine from outside access. It is Microsoft’s hope that this will lead to a significant reduction in internet spread security exploits such as the several variants of DCOM viruses. Many ISPs have blocked internet access to ports 135, 137 in an effort to prevent their networks from spreading or receiving such traffic. Microsoft is now making attempts to ensure that most machines are now protected. As the number of machines eligible for an infection decreases rapidly, the ability for internet exploits to spread decreases significantly.

ServiceLedger is a network application. In the default configuration of the new XP firewall, ServiceLedger will run as is for most single machine systems. However if you run a multi-machine system (2 or more machines), you should be aware of some items.

The first time you run ServiceLedger on Windows XP sp 2, you will receive a message box asking if you would like to continue blocking this program. You should click "Unblock".

The remainder of these instructions are exclusively for multi-machine installations.

If you have a separate machine acting as a server hosting the ServiceLedger database for you and it is upgraded to Windows XP SP 2, you should configure the "port" for SQL Server to listen to these other requests for the machine that houses the database server.
  1. Go to the new "Windows Security Alerts" in your system tray, and right click it
  2. Select "Open Security Center"
  3. Click on "Windows Firewall" under "Manage Security Settings For:"
  4. Click on the Exceptions tab, and click "Add Port"
  5. In the Name: field enter in MS SQL Server
  6. In the Port Number: enter in 1433
  7. Click "Change Scope"
  8. Click "My Network"
  9. Click "OK"
  10. Click "OK"
  11. Now you should see MS SQL Server in the "Programs and Services" list
  12. Click "OK" and your users should have network access to your server

If you have accidentally blocked access to ServiceLedger please do the following:

  1. Go to the new "Windows Security Alerts" in your system tray, and right click it
  2. Select "Open Security Center"Click on "Windows Firewall" under "Manage Security Settings For:"
  3. Click "Add Program"
  4. Click "Browse"
  5. Locate and open "C:\Program Files\ServiceLedger\ServiceLedger\ServiceLedger.exe
  6. You should now see ServiceLedger in the "Programs and Services" list
  7. Click "Change Scope"
  8. Click "Any Computer" (allows the broadcast 255.255.255.255 UDP protocol)
  9. Click "OK"
  10. Click "OK"

Related Questions:

Attachments:

No attachments were found.


ServiceLedger KnowledgeBase Copyright © 2019 support.serviceledger.com
Powered by AcitveKB Knowledgebase Software