Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 231
  • Last Modified:

WebSite deployment in IIS 6.1

Hello Experts,
I am trying to deploy a dot.net 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!
0
RadhaKrishnaKiJaya
Asked:
RadhaKrishnaKiJaya
  • 4
  • 4
1 Solution
 
becraigCommented:
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 ?
0
 
RadhaKrishnaKiJayaAuthor Commented:
Publish in internet.  Thank you!
0
 
becraigCommented:
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 :
http://www.wikihow.com/Publish-a-Web-Site-on-Your-Own-Domain
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
RadhaKrishnaKiJayaAuthor Commented:
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.
0
 
becraigCommented:
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.
0
 
RadhaKrishnaKiJayaAuthor Commented:
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!
0
 
becraigCommented:
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:
192.168.47.4      test.mydomain.com  (where 192.168.47.4 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.
0
 
RadhaKrishnaKiJayaAuthor Commented:
Thank you.  Very helpful.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now