One of our client’s proprietary applications called FormMaster has a built-in update feature.
Whenever they ran the update, it refused to connect to the CCH server, or go anywhere beyond the initial connection
In the ISA live query, the following would be seen from the XP Pro client in the log:
- XP –> CCH IP –> Destination Port 80 –> HTTP –> Internal –> External
- XP –> SBS IP –> Destination Port 1745 –> TCP Unknown –> Internal –> Local Host
Enabling SOCKS proxy settings in the application in any combination would not work.
A call into CCH support ended up getting us the setting we needed to make things work:
Make sure the correct customer number, postal code, and phone number are in place.
Check the Override Default Server Information and set the port number to 8093. Leave the Server Name field blank.
Click OK, then click the Next button to initiate the connection to the server and we will see:
Once the scan for files has finished, we will see:
Once the files are downloaded, the original CCH program will need to be closed before the updates can run or the following error will happen:
After closing the application and clicking OK, the updates ran as expected.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book