IIS on Windows 2016

[bankingguy]

Hi Guys,

I'm trying to use IIS as a file server for my firmware download. I configured port 443 for secure connection as mandated by our security team. I installed an identity cert and it is successful. When i try to browse the fqdn of the browser i get success. When phone starts to pickup firmware files it keeps on redirecting to port 411. Do i have to change the service port to 411 of my IIS? What is the logic behind it? Also I need a reference 46xx settings how to fill up the TLSRVR parameter and port.

 

[bankingguy]

This is what I have:

46xx:

SET BRURI

https://xxxadmin:xxxxxxxx2k16@10.206.70.46:411/PhoneBackup/

SET BRAUTH 0
SET TLSSRVR 10.206.70.46
SET TLSPORT 411
SET TRUSTCERTS Intermediate_CA_G1.cer,Root_CA_G1.cer,Intermediate_CA_G1.pem,Root_CA_G1.pem

Certificates are installed in my IIS successfully.

Also the PhoneBackup folder has the "write" access on the folder sharing security.

 

[jimbojimbo]

Probably not going to work until after you download the 46xxsettings.txt file and the applicable certificate authority files identified in the TRUSTCERTS parameter. The phones come default with no CA certs so they cannot negotiate the HTTPS connection.

 

[bankingguy]

Hi Jimbojimbo, how can it pickup the 46xx settings if it cant even pickup anything using HTTPS. Nothing is happening.

 

[jimbojimbo]

Why is your TLSPORT set to 411 if you are using 443 on IIS?

Phones must first startup and utilize HTTP to obtain the list of TRUSTCERTS and download the certificates to be stored in the phone. You may need to pre-stage the phones before putting them into production.

I'm not a fan if IIS and typically use Apache since it easily supports Anonymous WebDAV for phone backups. You can do it on IIS but requires some manipulation (such as a PHP script).