Preparing to run UNICOM Intelligence Interviewer - Server through a firewall
If you will be running UNICOM Intelligence Interviewer - Server through a firewall, some ports on the firewall must be open.
Firewall between the Internet and the web server
All communication between the browser and the UNICOM Intelligence Interviewer - Server Web Server (mrIWeb) and between the browser and the Accessories server defaults to using HTTP on port 80. If your website runs SSL or uses a different port number, you can specify this on the Internet Information Services (IIS) Configuration page during the installation procedure.
Firewall between the web server and the accessories server
When the web server needs to communicate with the accessories server in order to access the image cache, and there is a firewall between the two computers, communication normally takes place using HTTP over port 80. The firewall must allow traffic in both directions on this port. If your website runs SSL or uses a different port number, you can specify this on the Internet Information Services (IIS) Configuration page during the installation procedure.
Firewall between the web server and the interviewing server
Communication between the Web Server (mrIWeb) and the UNICOM Intelligence Interviewer - Server (mrIEng) usually uses SOAP over port 80. If your website runs SSL or uses a different port number, you can specify this on the Internet Information Services (IIS) Configuration page during the installation procedure.
The firewall must allow traffic in both directions on this port.
If the accessories server is separated from the interviewing server, the same ports must be opened between the accessories and interviewing server. Phone Participants, Review Interviews, and the Interviewing Activity reports all run on the accessories server and interact with the interviewing engines on the interviewing server.
Firewall between the UNICOM Intelligence Interviewer - Server Admin/Accessories server and the data server
Communication between the UNICOM Intelligence Interviewer - Server Admin/Accessories server and the data server usually uses TCP on port 1433. This port must be opened before the installation begins, as the installation process writes to the data server.
If you have SQL running on a named instance, the port number is assigned by SQL Server and could be something other than 1433:
▪If the port is statically assigned, and you know which port number is used, open this port instead of port 1433.
▪If the port is dynamically assigned, port 1434 must be opened so the client can resolve the port number to use.
▪If you do not know which port is being used (and for more information about named SQL instances in general), see:
It is helpful to open port 1434 to allow the client to dynamically resolve the SQL Server port to be used for communication. If port 1434 is not open, and the default port of 1433 is not used for communication, the SQL Server port must be set during installation by appending ,portnumber to the SQL Server instance.
Firewall between the DPM servers in the cluster
Communication between DPM servers in a cluster takes place using TCP on port 65100.
When implementing a cluster in a Windows Server environment, you must also ensure that TCP port 65100 is open in the Windows firewall. Refer to the Windows Firewall documentation for information on opening ports.
See