WebSite deployment in IIS 6.1

Posted on 2014-03-21
Last Modified: 2014-03-25
Hello Experts,
I am trying to deploy a website in IIS 6.1 in Window Server 2008 R2.  It works when I Browse it.  How would I test it in a browser?  Where should I define the domain name?  Please let me know.  Thank you!
Question by:RadhaKrishnaKiJaya
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 4
LVL 29

Expert Comment

ID: 39945981
Do you want to publish your site to the internet or are you wishing to simply browse via a domain name locally on your own computer ?

Author Comment

ID: 39946023
Publish in internet.  Thank you!
LVL 29

Expert Comment

ID: 39946085
You will need to register your domain name
Find a hosting provider that hosts asp and .net solutions
Then simply upload your content to your website and test.

Here is a good step by step :
Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!


Author Comment

ID: 39946104
This will not help me.  I need to deploy it in my office server.  I am using IIS 6.1 in Window Server 2008 R2.  Thank you anyway.
LVL 29

Expert Comment

ID: 39946115
I asked specifically if you wanted to host internally or publish to the internet, you indicated you want to publish to the internet.

Do you have a publicly accessible internet IP address  ?

How is your current network configured ?

Does your network Admin have network acls / firewall rules in place to block / allow traffic  ?

Simply saying you want to publish a .net site say nothing unless you can provide a picture of your current situation so a potential solution can be suggested.

If your site is already established and you simply want to test the site from your local test machine before putting it onto a production server, you can simply use host files to point dns to your local machine and browse the site.

You need to provide more detailed information to get an actual solution, I cannot determine the best path for you without knowing what your working environment is and what you are really trying to accomplish.

Author Comment

ID: 39946137
The scenerio is I have been given a server with Window Server 2008 R2 to install IIS and website.  Thought it should work in any browser, still should be within our network.  Here is what I did.

1. Installed the IIS
2. Deployed the Website and able to browse it

Question is how would I be able to use the website in Internet Explorer or Google Chrome?  What setup I am missing?

Thank you!
LVL 29

Accepted Solution

becraig earned 500 total points
ID: 39946174
You are not missing anything as such:

If you want a site to be accessible outside your office then you need to have a public dns entry that other persons can resolve via the internet.

You can talk to your Network Admins about setting up the public DNS record and configuring the network to forward internet traffic to your server on the http/https ports.

If you want it to be accessed locally by everyone you can do one of two things:

1. More cumbersome and time consuming have everyone update their localhost file
located at c:\windows\system32\drivers\etc\host to include a line such as below:  (where is the private IP Address of the site in IIS on your server)

2) Have your Domain Admins add an A record to point the test url to the IP address on the internal site.

Author Closing Comment

ID: 39954190
Thank you.  Very helpful.

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Performance in games development is paramount: every microsecond counts to be able to do everything in less than 33ms (aiming at 16ms). C# foreach statement is one of the worst performance killers, and here I explain why.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question