Sage 100

I have a client who receives the following error when trying to launch MAS 200 Workstations: ""Unable to connect to server 192.168.1.103. The server cannot be found."" I looked up this error in the Sage Knowledgebase and changed the SOTA.INI file to the IP Address of the server to avoid possible conflicts. I have triple checked the port ID of the MAS instance on the server. I have made sure that the service IS running and, when running the workstation FROM the console of the server, I don't get this error. The error happens on the workstations only. KB article 110-400203 mentions the following: ""A network router may be interfering with WINS name resolution, or there may be more than one workstation on the network with the same name. Test by changing the server name to the server's IP Address in SOTA.INI. If the connection is successfful, troubleshoot accordingly."" What is another way to test to see if the server is accessible AND the port is properly open/broadcasting?

If this a new server, check the firewall settings on the server. Set an inbound rule for pvxwin32.exe.

Can it be pinged? Can you run MAS200 as a MAS90 All workstations?

probably windows firewall - but wouldn't you add a rule for the port, not the file? Or does either one work? Not sure, but I've typically opened the port on the firewall.

Try right-clicking the MAS200 desktop shortcut and viewing the Properties. You may be missing the port number in ""Start In"" field.

First thing to check would be to open a command line on the workstations and type ping 192.168.1.103. You should immediately get results along the lines of ""4 packets sent, 4 received"". If you get ""Request timed out"" there is a firewall or other application/device blocking access to the server. Popular candidates include software firewalls like the Windows firewalls or over zealous hardware firewalls blocking internal traffic. Depending on what you find and who manages the clients network, you may want to check with their system administrator prior to making any changes. In addition to getting to the bottom more quickly, you'll also make sure there are not other business security requirements in play that are affecting things.

You can use the ""netstat"" command from the command line on the server to see how it is listening. @EricAnderson: Windows firewall lets you add connections for a certain program so that no matter what port it listens on, it will be allowed.

Some switches with netstat: netstat -a shows All connections and listening ports. netstat -b (must be run as administrator) tells you which EXE is doing the listening.

Windows firewall was locked down tighter than Ebeneezer Scrooge! I simply turned the **** thing off and the workstations worked. Now I need to fix it. Thanks for all of the quick responses!