# Shutting down the Network Server

To shut down the Network Server, you can invoke a script, a jar file, or a class.

The scripts to shut down the Network Server are located in the `$DERBY_HOME/bin` directory.

Important: If user authentication is enabled, you must specify a valid Derby user name and password; if the user authentication check fails, you'll see an authentication error and the running server remains intact. Note that Derby does not yet restrict the shutdown privilege to specific users: the server can be shut down by any user on the server machine who presents valid credentials.

- To shut down the Network Server by using the scripts provided for Windows systems, use:

      stopNetworkServer.bat [-h hostname] [-p portnumber] [-user username] [-password password]

- To shut down the Network Server by using the scripts provided for UNIX systems, use:

      stopNetworkServer [-h hostname] [-p portnumber] [-user username] [-password password]

- Shutting down by using the command line
  From the command line, you can shut down the Network Server by invoking a jar file or a class.
- Shutting down by using the API
  You can use the NetworkServerControl API to shut down the Network Server from within a Java application.

Parent topic: Using the Network Server with preexisting Derby applications
Related concepts
The Network Server and Java Virtual Machines (JVMs)
Accessing the Network Server by using the network client driver
Accessing the Network Server by using a DataSource object
XA and the Network Server
Using the Derby tools with the Network Server
Differences between running Derby in embedded mode and using the Network Server
Related tasks
Installing required jar files and adding them to the classpath/modulepath
Starting the Network Server
Obtaining system information
Setting port numbers