The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: Re: Re: [OT] (A little) : Firewire cables...


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Fw: Web server DNS name


  • Subject: Fw: Web server DNS name
  • From: Gareth Cook <g@xxxxxxxxxx>
  • Date: Wed, 23 Mar 2005 08:53:14 +0000


Another way is to create a internet shortcut in your favourites folder,
set the address as http://192.168.0.2:52340 and then give
it a name of
"telephone"

Then just type telephone in the address bar

G.

Gareth Cook
SWG EMEA North Account Manager
IBM SWG - BTE Office - Lotus Park, Staines, TW18 3AG
Office: +44 (0)1784 445166 - Mobile: +44 (0)7980 445166
AIM Chat : TheBoyG - MSN Chat : chat@xxxxxxx
email: g@xxxxxxx


----- Forwarded by Gareth Cook/UK/IBM on 23/03/2005 08:51 -----

Discussion
Main Topic

"Paul Gale" <groups@xxxxxxx>
Today 08:40

.
Subject:
.
[ukha_d] Web server DNS name
.
Category:




I asked this a few weeks ago but didn?t get it resolved. This is what I
want to do and need some ideas/help:

I have a xAP application running on my W2K3 server. It has a web interface
service running on port 52340. I also have IIS v6 running on the server
(domain controller that also runs most other services inc DNS) and serve
up local web pages for HA use and Exchange.

What I want to do is type ?telephone? into IE?s address bar and have it
load the correct page. At the moment I have to type 192.168.0.2:52340 or
servername.domain:52340.

I think I need to add a DNS entry and use host headers on IIS maybe??? I
don?t understand the host headers bit though.

Help would be great thanks!

Paul.





[Non-text portions of this message have been removed]






UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.