Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Configure IIS for Internal/External website.

Status
Not open for further replies.
ScottishFencer

ScottishFencer

Technical User
Sep 27, 2005
74
GB
Hello there,

The company I am working with is currently moving from its current website (inhouse) to an externally hosted website. We own our domain and I've already asked our DNS provider to change the existing record to point to the new IP address. So far so good.

I still have the old IP address with the webserver still hosting the old site (just in case).

The main reason I have kept it open is twofold:

We have external contractors who use a web app we provide.
Part of the site was the company's Intranet.

What I want to know is this:

I have provided the contractors with the current url (in the form of and notified the intranet users that the intranet is still available at It isn't very user friendly...

I would like the users to just be able to type in "Intranet" in their browser and go straignt there. I would like to type " for the external users. I suppose I will have to register a new domain for them.
We are using IIS 5 and I am no sure how I go about doing this.

FYI I have just started with this company and the manager left to get a better job. I have no one else to bounce ideas off.

I'm pretty new to configuring IIS - and maybe this isn't the correct way to approach this situation. I would appreciate any advice that members could offer.
 
Sort by date Sort by votes
Have you looked into configuring your clients to use an internal DNS server for name resolution. That way they could resolve an internal domain or alias like locally. The DNS server can forward requests to your ISP DNS server for all other lookups. External users would use public DNS to resolve a real domain that points to your public IP.
 
Upvote 0 Downvote
You could ask your DNS provider to add an additional A Record going to the IP address of your localserver called webapp

Then people could goto
If you wanted people to goto you could make an HTML page to redirect the user so;

<html>
<head>
<script language="JavaScript">
var time = null
function move() {
window.location = '}
</script>
</head>
<body>
<body onload="timer=setTimeout('move()',1)">
</body>
</html>

Put this is
When a user goes to /webapp (regardless of where they are) it will redirect them back to your local server.

It should hopefully cut out the amount of users going 'i cant see the webapp!!'

Hope this helps.

I wish someone would just call me Sir, without adding 'Your making a scene'.

Rob
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

ravalos
  • Locked
  • Question
Problem with PDFs in IIS
Replies
1
Views
1K
gbaughma
gbaughma
Abdullah Al Maruf
  • Locked
  • Question
Telnet help for
Replies
2
Views
764
gbaughma
gbaughma
dpellegrini
  • Locked
  • Question
Website will load using hostname but not IP address
Replies
3
Views
1K
mangentle
mangentle
DrB0b
  • Locked
  • Question
Windows 2016 IIS FTP server with a ton of user accounts
Replies
4
Views
772
DrB0b
DrB0b
mangentle
  • Locked
  • Question
What are the key advantages of using Microsoft Windows Servers for businesses?
Replies
1
Views
1K
gbaughma
gbaughma

Part and Inventory Search

Sponsor

Back
Top