How to configure IIS to respond with a FQDN in the header

I would normally research this for myself, but am short of time and asking is quicker

I have my IT shop deployed onto IIS 7 in customer's DEV domain.   They would like people to be able to access it from their desktops in their production domain (purely for demo purposes)

If we put the FQDN into the URL, the address is resolvable and the initial connection to the IT Shop is made, but the browser then gets redirected to the "hostname" of the DEV server and the we get a "server not found" message.

I'm not an IIS expert, so if someone could just tell me how to get IIS to respond with its Full Qualified Name in the header then the browsers in the other domain(s) will work.

From memory, is it something like setting an Alternate Hostname ??



Parents Reply Children
No Data