During the project, some installation problems had occurred. most of them can be easily fixed with a bit of research and configuration. System and software had been reinstalled couple times in order to corrected certain configuration setting during the the installation. However, there was a major issue remain unresolvable and required further attention.

The communication between the web server and the data server faced technical difficulty through out the project. For some reasons, the web application (developed by VB.Net associated with ASP.Net via IIS) was not able to "talk" with data server. It returned with the error message of "SQL server does not exist or access denied" Figure 3.a. Different approach had been applied individually or in combination with other techniques to resolved the error; however none fixed the problem. The methods included A)disabled all anti-virus and firewall, B)changed SQL server's user ID and password, C)change port used by the web application and the SQL server Figure 3.ca, Figure 3.cb, D) reconfiguration on IIS and SQL server and VB.Net, and E)different VB command to communicated with the database (using session:
EX: Session("ServerName") = "(local)"
' (to local database)
Session("ServerName") = "98.197.17.70"
' (link to a SQL data server outside of UH network)
Session("ServerName") = "129.7.44.99, 1433"
' (link to data server with specified port and IP)
Session("ServerName") = "UH-36QNY1CUHUOY")
' (link the data server with computer name)
)

After a series of research and trail and error, what turned out to work is A)ping to the other machine (Figure 3.b, Figure 3.c), B)map to data server's network driver Figure 3.d, C)link to the other computer's SQL database from SQL server Figure 3.e link by IP, Figure 3.f link by computer name, D)local SQL server (place the web application and the database in the same machine) Figure 3.g login, Figure 3.h login success, Figure 3.i local database, Figure 3.j local data, E)access to a data server outside of UH's network Figure 3.k login success and F)communication between window application and SQL server on the data server, 129.7.44.99 (no IIS involved) Figure 3.l SQL database on 129.7.44.99, Figure 3.m search for password with user name, Figure 3.n return with the corresponding passwords of the user name, Figure 3.o search for a user name that does not exist, Figure 3.p return with "Not Found", Figure 3.q add new user, Figure 3.r SQL database on 129.7.44.99 after added new user