Invalid Deployment Server address or port

[subagchi]

While installing the splunk Universal Forwarder Version 6.2.15-278770-x86 on a 32bit Windows 2003 server, I am getting a message "Invalid Deployment Server address or port". Even if I leave the Deployment Server Field Blank, the same thing happens. Is there any solution?

I have tried a quiet installation using command line and enabled MSI logs which shows each time the installation is failing with Fatal Error 1603. Please suggest if there is any solution.

[gcusello]

Hi @subagchi,

you have to check the deploymentclient.conf file that should be in $SPLUNK_HOME\etc\system\local

If it isn't in that directory you can find it running this command on the forwarder from the bin directory

splunk btool deploymentclient list --debug > check.txt

At first try to delete or rename it, otherwise, please share it.

Ciao.

Giuseppe

[subagchi]

This is a fresh installation. So there is no configuration files created. I am getting this message while installing the Universal Forwarder. Though Deployment Server field is an optional one, It is not letting me proceed when i leave it blank. Even if I put the correct Deployment server, I get the same message. Also port - 8089 is already allowed from client (Windows 2003 server) to deployment server.

[gcusello]

Hi @subagchi,

which Splunk version have you on Indexers?

if you use the 6.2 forwarder, there could be some compatibility problem: I understand that you server is a Windows 2003 server, try to use a 7.x version, it isn't certified but maybe it runs better.

I hint to open a case to Splunk Support.

Ciao.

Giuseppe

[isoutamo]

Hi

here is list of supported UF vs Splunk server:

• https://docs.splunk.com/Documentation/VersionCompatibility/current/Matrix/Compatibilitybetweenforwar...

Her is told which SSL versions works together

• https://docs.splunk.com/Documentation/Splunk/8.2.0/Security/SetyourSSLversion
• https://docs.splunk.com/Documentation/Splunk/8.2.0/Security/AboutTLSencryptionandciphersuites

Usually we are using separate app which contains all needed DS & Idx output configurations. In that way we can easily change those later if/when we need e.g. change DS address/name etc. So my proposal is that you install latest working UF version to this node without DS configuration. Then add separate TA named eg. zzz_TA_DS_configuration (so it's precedence is lowest)

r. Ismo