Navigation: Network & Remote Installation > RI - optional responsive remote interface >
Step #3: RI Testing
It is always recommend to read through all instructions first before proceeding.
Again confirm again before anything further that you can run the AyaNova program itself successfully on the RI IIS server and on local networked computers connecting to the networked AyaNova database first before proceeding.
If any issues at this point, they must be resolved before proceeding with RI.
a. On this RI IIS server, open a DOS command prompt by selecting Start -> Run and typing in the following cmd and selecting OK
b. Type in the following ipconfig at the DOS prompt that appears
c. This will now display the Local Area Connection's IP Address as well as the Subnet Mask and Default Gateway.
d. Write down this IP Address as you will need this to perform internal testing and to identify which internal IP address to forward to via your router. In the screenshot below, the IP Address is 192.168.1.100 Your's will likely be different.
You can also check the IP Address set to a web site via IIS Manager. It is suggested to go through and familiarize yourself with the properties and settings in IIS.
a. Open up a web browser on the RI IIS server itself (where you installed RI)
b. Enter in the path http://localhost/AyaNovaRI if you have not specified a port orhttp://localhost:XXXX/AyaNovaRI where XXXX is the TCP Port number of your Default Web Site on this IIS server if you have specified a port other than the default of 80
(TCP Port determined from step B of IIS Server Configuration)
c. Confirm you can bring up the RI login screen
d. Confirm you can log in using a valid AyaNova User username and password
e.Now test entering in this local computer's private IP address instead of localhost
(Local area connection private IP address determined from step B above)
For example, if the local area IP address is 192.168.1.100 and the TCP Port number of your Default Web Site of IIS is 9632, you would enter in the URL address line in the web browser on the IIS server itself http://192.168.1.100:9632/AyaNovaRI
•If you encounter a 404 error bringing up the RI login page when performing this testing on the server itself, check out the forum topic https://forum.ayanova.com/t/if-receive-page-not-found-or-404-error-or-400-error-testing-wbi/1125
IMPORTANT: Save yourself time - if any issues, refer first to the solutions listed in RI Server Common Issues
a. Open up a web browser on a computer on the same internal network as the RI IIS server
b. Enter in the path http://xxx.xxx.xxx.xxx:XXXX/AyaNovaRI where xxx.xxx.xxx.xxx is the internal local area connection IP address of the RI IIS server and XXXX is the TCP Port number of the Default Web Site on this RI IIS server
(Local area connection IP address determined from step B above)
For example, if I installed RI to a computer on my network that has an internal IP address of 192.168.1.100, and the TCP Port of the Default Web Site on this computer is 9632, I would enter inhttp://192.168.1.100:9632/AyaNovaRI as the URL address.
c. If the RI login screen does not display, but it did in the first two tests above:
•you may be entering an incorrect local IP address for the RI IIS server. Re-check.
•or your RI IIS server may have a firewall enabled that is preventing access. Re-check.
a. On a computer that is connected to the Internet, open up a compatible web browser
b. Enter in the path http://xxx.xxx.xxx.xxx:XXXX/AyaNovaRI where xxx.xxx.xxx.xxx is the public IP address of your router and XXXX is the forward port you have configured on your router (which is also the same as the TCP Port number of the Default Web Site on the IIS server)
For example, if the router's static IP address is 222.333.777.12 and the forwarded port configured for the IP address 192.168.1.100 that I set up in the router's configuration is (and that is also the TCP Port for the Default Web Site) is 9632, I would enter http://222.333.777.12:9632/AyaNovaRI into the web browser URL address.
c. If the RI login screen does not display, but it did in the first three tests above, you may not have configured your router correctly. Review and edit your configuration - don't forget to reset after.