I have seen the thread about how you can get in full control of your db server (Sample code: How to get full control over a SQL Anywhere server). My question is a little different, as I don't want to refuse any new connection to the database but only remote ones. So local connections should be still allowed, so that all your administrative tools still work on the server. |
The easy way is to stop dbsrv*.exe, start dbeng*.exe which doesn't allow network connections. Alas, the personal server is also limited to using one CPU. For all the differences see http://dcx.sybase.com/1101en/dbadmin_en11/introductionrunning.html Or... did you mean WAN-versus-LAN? I gave you a "network-versus-same-machine-connection" answer. |
AFAIK, there's a third possibility besides dbengX and dbsrvX -x TCPIP{localonly=yes}: You can restrict TCP/IP connections altogether by dbsrvX -x none. That enables only shared memory connections and won't even enable local TDS connections (as those require TCP/IP, e.g. jConnect). Take care as this may not support all variants of connections between local clients and services/terminal services, cf. the docs. |