Backup Exec / NTHOST TCP Port 10,000 Conflict

Important Note: You may require further consultation on the content of this document. You may not have the in-house expertise or the time to apply the instructions included with this document. Either way, Tecsys can help: just contact our support team at with a brief description of your issue(s) and one of our technical specialists will contact you directly.

Earlier versions of WinSol/Enterprise on a Windows Server used TCP port 10,000 to communicate with its clients. In Backup Exec 9.x for Windows Servers, NDMP uses TCP port 10,000 to communicate with its Remote Agents. This port conflict will cause WinSolís NTHOST program to fail with an error 15 on start up.

Starting with Enterprise 5 the TCP port for NTHOST defaults to 12,000. With previous versions of WinSol the Backup Exec NDMP port must be changed.

Caution: When changing the port for NDMP, the changes must take place on every server or workstation in the environment that needs to be protected by Backup Exec. Failing to do so will result in servers not being selectable inside Backup Exec or not able to be backed up at all.

To change the port, do the following:

On the Backup Exec Media Server:

  1. Open BEUtility.
    Note: By default located in C:\Program Files\VERITAS\Backup Exec\NT.

  2. From the right pane, select the Backup Exec Media Server.
    Note: If it is not listed, then right-click All Media Servers and select New Media Server.

  3. Under Services Tasks, choose Stop services.

  4. Go to Start > Run, and type NOTEPAD.EXE to start Notepad.

  5. Go to File > Open. Browse to the C:\WINNT\System32\Drivers\ETC directory, and select the Services file.

  6. At the end of the document, add the following line (where 9,000 is the port to be used):

      NDMP    9000/tcp      # Backup EXEC

  7. Choose File > Save.

  8. Choose File > Exit.

  9. From BEUtility, under Services Tasks, choose Start services.

Note: Microsoft Windows 2000/2003 Small Business Server will sometimes change the services file back to its original state. If this should occur there will be a port conflict after the next reboot and the above changes will have to be made again.