I hosted a website in IIS 8 and binding with a proper hosting name (subdomain.xyz.com). It is working from my local machine, but it is not working when I access from hosted server. It is showing authentication window, even I provide a valid credentials it is showing again and again.
The server is hosted in Azure.
Server: Windows Server 2012 R2
It is because NAT loopback,
you can try to use internal ip if you access from hosted server.
if you want to access using your hosting name, make sure to point it inside "hosts" file.
C:\Windows\System32\drivers\etc\hosts
add this line
127.0.0.1 subdomain.xyz.com
so basically what hosts file do is, it actually point to your localhost every time you enter subdomain.xyz.com in your browser.
I read somewhere that a web application consists of a web server, application server and a database server. What is the difference between these three ?
I asked this question because I remember when I hosted a website, all I had was a https login to the control panel of the website, in which I put all my files in htdocs folder. There were no three separate things like the web server, application server and the database server.
This often gets confusing.
Firstly - "Server" can refer to a physical thing (a computer), or a logical thing (a piece of software).
Web, application and database server software can all run on the same physical server machine, or be distributed across multiple physical machines. Most large websites have multiple machines; most "consumer" hosting packages run on a single box.
The logical separation is as follows.
The Web server deals with HTTP(S) requests, and passes these requests on to "handlers". They have built-in handlers for file requests - HTML pages, images, CSS, JavaScript etc. You can add additional handlers for requests that they cannot manage - e.g. dynamic pages delivered by the application server. Web servers implement the HTTP specification, and know how to manage request and response headers.
The application server handles requests which create dynamic pages. So instead of serving an HTML page that is stored on the hard drive, they dynamically generate the HTML sent to the end user. Common languages/frameworks for this are Java/JSP, .Net (aspx), PHP, Ruby (on Rails or not), Python etc. Most of the time, this application server software is running on the same physical server machine as the web server.
The database server software is where the application stores its structured information. Typically, this means custom software which allows the application server to ask questions like "how many items does user x have in their basket?", using a programming language. Examples are MySQL, SQL Server, Oracle (all "relational databases"), and MongoDB, Redis and CouchDB ("NoSQL" solutions).
The database software can run on the same physical machine as the web server, but it's usually the first thing that gets hosted on separate physical hardware when the site needs to scale.
Web Server -
Server on which your website is hosted. This server will have installed web servers such as IIS, apache, etc.
Application Server -
Server on which your created applications which are utilizing your database, web service, etc.
This application server will host business layer (wrapped with web services), scheduled jobs, windows services, etc.
Database Server -
Database server will have your one or more database hosted such as Oracle, Sql Server, MySql, etc.
If you are referring to htdocs then it is a Web Server. The database you are using is must be installed on different server which is your Database server. Application server can also be installed on the same web server machine.
Reference - Deployment Patterns
Web Server: The server on which all your HTTP requests are handled is known as a web server
where as
Application Server: Including the services of web server i.e responding to the HTTP requests it also responds to the business logic thus not just limited to the HTTP protocol
Eg. gaming servers, chat rooms etc.
Hey all I have created a web service that starts on my local intranet and sends out data to an outside server. This works awesome and all using classic asp on the server side and vb.net program sending the info from the intranet pc.
But now I need to do the opposite. I need to have the web service be called from the server web page to the intranet pc. Problem being is that we do not have access to any ports or any means of getting data from the server because of the firewall.
How can this be possible to do with my current scenario above?
I am currently developing a website in C#, It requires to send requests to remote SQL Server.
I need to encrypt any communications from the client to the web server and to the SQL Server.
The SQL Server is currently used locally by another windows application, so the SQL server is being used locally and remotely.
So my concern is do I need to install cert for both servers ? If so will there be any connection problem between windows application and sql server ?
Thanks
you would only need a certificate on your sql server
use the encypt=yes option in your connection string on the web server.
I am trying to host a WCF service in IIS 6.0 on server 2003. And when I
browse to the server I get the following error.
SecurityException: Request for the permission of type
'System.Net.DnsPermission
Is this related to the permissions granted to the user account the app
pool is running under or some other problem, and how do I fix this.
This might be related to the settings for local Intranet. I am assuming that you are browsing from your PC to the server. Try this:
Connect to the server via Remote desktop (or just use the server console), then browse the service and see if you get the same error.
If you do not get an error:
On your PC add the address of the server to local intranett, then try and browse the service again.
Good luck
Shiraz
To answer the replies.
Yes that was the entire error message Terry. It didn't appear to be a WCF issue but a security configuration problem on the web server that wasn't allowing DNS Permission as required by WCF.
The problem was resolved by uninstalling SharePoint services on that server where the WCF service was being hosted. Not sure still, why SharePoint would change the security permissions.