Sage 100

Anybody know if you can force the Application Server to bind to a specific IP address on a server (that has multiple interfaces)?

duck tape?

Perhaps using a firewall?

I'm already out of WD40, so I guess duct tape's next.

Can't you use the IP address as the server name? Seems so, see page 37.

Page 37 says Client Config, but can I use that to set the IP that the server daemon uses, or is that only telling the client where the server daemon already is?

Not sure, but since you could specify IP address in the client config string, wonder if it work. Haven't tried it myself.

What are you trying to do? (Something like preventing users from connecting to Sage 100 through a Wireless interface on the server?)

We had a situation where the customer is trying to run the Sage 100 Application Server from a Hyper-V host. Sage App is binding to the physical interface as an APIPA (169.254.x.x), while the Hyper-V host is actually using a virtual interface (192.168.x.x), so no clients are able to establish a connection. In this specific instance, we worked around it by having them create a VM to host Sage 100, but I was just curious if there was a way around this.