Sage50 Connection manager installed on Colocated Fileserver via VPN. File server Never sees the connections

I installed the latest version of connection manager for the version of the app that we're using and the connection manager software never sees any users connecting and trying to access any companies stored on the shared drives.

The service is started and running and the files are located on the server.  Is there some hidden issue with VPN connected environments?  I swear i've done this before so i don't understand why this isn't working.  We don't have a support contract with sage and i cannot find anything on the web with regards to this issue other than re-install which i've done.

Any help would be greatly appreciated.

Parents
  • 0

    Try Telnet or FTP from the workstation to the Sage 50 Connection Manager port on the server to check connectivity.

  • 0 in reply to RandyW

    Will do so and see what it does.

    Thanks!

  • 0 in reply to gditson

    Telnet Fails, and FTP says waiting for welcome message.... i'm not sure if this means it's working or not.  I know for a fact my firewall policy is allowing all traffic to/from the colo so it shouldn't be a policy issue.  

    Telnet message is: .NEThServer Encountered an internal error.  To get more info turn on the customer Errors in the servers config file

  • 0 in reply to gditson

    That sounds like it connected, but didn't know what to say which is normal.  So there's at least IP connectivity from the client to the the Connection Manager listening port. 

    Sage 50 parses out the server name from the path of the file.  In case the name isn't reliably resolved to the correct IP address, it might be more reliable to put IP address and sharename in the command line, with the executable path quoted:

    "C:\Program Files (x86)\Sage 50 Quantum Accounting Version 2017\Sage50Accounting.exe" \\192.168.0.242\sadata\MyCompany.SAI

    There are log files in the company data's .SAJ folder on the target server that can help sort out what happened if it only sort-of connects.

Reply
  • 0 in reply to gditson

    That sounds like it connected, but didn't know what to say which is normal.  So there's at least IP connectivity from the client to the the Connection Manager listening port. 

    Sage 50 parses out the server name from the path of the file.  In case the name isn't reliably resolved to the correct IP address, it might be more reliable to put IP address and sharename in the command line, with the executable path quoted:

    "C:\Program Files (x86)\Sage 50 Quantum Accounting Version 2017\Sage50Accounting.exe" \\192.168.0.242\sadata\MyCompany.SAI

    There are log files in the company data's .SAJ folder on the target server that can help sort out what happened if it only sort-of connects.

Children