Host Header, IIS 6.0 not resolving correctly on LAN
I need an IIS and DNS Server expert on this one.
I have an intranet site on 2003 Server in my office. For several months it has been serving up pages internally to our office. Now, I've added a 2nd site on the same IIS server, and set up Host Headers so that both sites can use port 80. The Server Name is CPU1460, so with the Host Headers in place, the new URLs to get to the two sites should be:
To make this work, I set the server up to be a local DNS server, and added both of those Host Header names to the forward lookup zone.
Now, what's happening when I try to access the server from a remote client machine, the URL Issues.CPU1460 is resolving to http://www.issues.cpu1460/
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need. goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
<p><span>Some days before I have done a job on Windows Server 2003 Enterprise edition & Client XP. It is departmental food court. In the office room of the restaurant have a system which will be Server system and main domain. There was another 8 system in every department of food <span> </span>with printer for billing.I</SPAN><br>
<p><span>Windows Server 2003 includes a mission critical Windows Server operating system, such as security, reliability, availability, and scalability.</SPAN><br>
<p><span>You have to install DNS server for DC without DNS the client computers wouldn't know which one is DC.You can host DNS on a different server than DC.</SPAN><br>
<p><span>Before Starting the DC installation process you need to make sure the <span> </SPAN>following points</SPAN><br>
<p><span>1)You have installed Basic windows server 2003 installation</SPAN><br>
<p><span>2)Make sure you have assigned a static ip address to your server</SPAN><br>
<p><span><span> </SPAN>Now start DC and DNS Setup process</SPAN><span></SPAN><br>
<span>Active Directory is a huge topic in itself. While DCPROMO is easy to run, planning of both the physical and the logical structure is the key to a trouble free active directory. </SPAN>
<p><span>Domain controllers do not have to be your most powerful machines, however they must be reliable and always available to answer logon requests. </SPAN><br>
<a><span>DNS (Domain Name System)</SPAN></A><span><span> </SPAN></SPAN><span>Role</SPAN>
<p><span>Once DNS is setup, it runs itself thanks to the new dynamic component hence DDNS. TCP/IP knowledge plus understanding of how DNS works is essential when troubleshooting connectivity problems.</SPAN><br>
<p><span>DNS enables client machines to resolve servers IP addresses. Once the client finds the server, Active Directory uses LDAP to locate services like Kerberos, Global Catalog that clients request.</SPAN><br>
<a><span>Print Server Role</SPAN></A><span></SPAN>
<p><span>In my experience there is a contrast between the software settings which are easy to configure and the hardware which constantly need for attention e.g. paper jam, 'out of toner'. Check list for print server:</SPAN><br>
<p><b><span>Client Configuration :- </SPAN></B><span>After</SPAN><span><span> Installation of Windows Xp give the IP Add on TCP/IP of IPV4.If you want to manually configure DNS server addresses, click</SPAN></SPAN><span><span> </SPAN></SPAN><b><span>Use the following DNS server addresses</SPAN></b><span><b><span>,</SPAN></B></SPAN><span><span> and then type the preferred DNS server and alternate DNS server IP addresses in the</SPAN></SPAN><span><span> </SPAN></SPAN><b><span>Preferred DNS server</SPAN></b><span><span> </SPAN></SPAN><span><span>and</SPAN></SPAN><span><span> </SPAN></SPAN><b><span>Alternate DNS server</SPAN></b><span><span> </SPAN></SPAN><span><span>boxes. After all job try to ping each other. I'm trying this and it also pinging. Files and data also can be shared through it.</SPAN></SPAN>
Hello, I am using this site's domain name and hosting for my website ,here i am faced these kind of problem, you may use this http://www.tucktail.com/ site's DNS,here your expected domains available .visit here for more details.
In order to access your default web page remotely, port 80 "INBOUND" must be open to the internet.
To access your web server, two things need to happen.
The first is you or someone else must initiate a http request on port 80 using the public IP Address of your DSL connection.
Second, your router must forward that request to your servers internal ip address.
Ex. Lets say your public ip address is 22.214.171.124. In a browser window from a remote location, you enter the URL http ://126.96.36.199 The request will be sent to your router on port 80.
Your web server will not have the ip address 188.8.131.52 because it's on the private network side of your router. So, lets say the private ip address of you server is 192.168.1.100
You need to configure your router to take the http request coming from the internet on port 80 to ip address 184.108.40.206 and forward that request to 192.168.1.100. This is known as port forwarding.
You also need to configure the host header name of your "web page" so it knows it needs to display the web page.
Since we're just using ip addresses in this example and not an actual FQDN (fully qualified domain name), you would make a host header entry for the web page of 220.127.116.11.
To do this open IIS.
Navigate to the web site in question and right click on it then select properties.
On the website tab, ensure the port number is set to 80 and choose the appropriate internal ip address if you have more than one network adapter in the server.
Next click on the advanced tab and look for the heading Multiple identities for this site. This is where you enter the ip address 18.104.22.168.
If you have a fully qualified domain name, you would enter the domain name instead of the ip address as specified in this example.
Host header names are the key to running multiple websites from one physical server as long as it has the necessary horsepower to do so.
Hope this helps and isn't confising. If you're confused in any way, don't hesitate to ask for clarification.
The Scanning feature must resolve the name you have entered into the host location in the one touch screen. If the system is not able to resolve the name to an address it will fail. The easy way out of this is to enter the destination IP address. The hard way is to fix the reason the printer can not resolve destination name to an Ip address. That will require fixing a DNS problem on your network
Just a couple of tidbits when using this approach:
You will essentially be controlling the DNS for the domain internally anyways. Meaning, any subdomains, mail exchangers etc., for the domain will have to be configured as well.
You need to install and run IIS or Apache...they are both web server programs. It doesn't really matter which you use, more of a user preference.
In my case I like to use IIS with Server 2003. Below is a link that is a full guide for setting up your server to host a website. it is step by step and includes pictures along the way. It should have you running in no time!
Does your DNS server have your server fqdn in its tables, and does your PC have the address of your DNS server in its lookup table?
One test you can do is to use the hosts file to put the fqdn into and assign it an address this would let you know the the PCs can use host tables to do the translation then this becomes a DNS issue as opposed to a lookup issue and you cut your troubleshooting in half.
In other words edit your hosts tables (hosts file) with the entry (Example 1):
IPADDRESS FQDN ALIAS
192.168.10.2 somesystem.myhome.com. system 192.168.10.5 somesystem2.myhome.com. system2
This as stated will determine if you have a DNS issue or a lookup issue, because the DNS system will use host tables first and the do a DNS lookup.
Once this is done if it works then try this setup:
1) in your router set the DNS to capture the DNS of your ISP (normally the setting will tell the router to use the DNS given to it by the DHCP protocol.
2) turn on DHCP on the LAN side of the connection in the router and set the controls for proxy DNS service (using the router as the local DNS server also called caching DNS server), However set the router up to allow static IPAddreses and if possible to recognize the domain name of the local LAN.
3) set your servers up with static IP addresses and in their host tables set the fqdn up as stated above in Example 1
4) in your PC set the DNS to be the IP Address of your LAN side of your router i.e. 192.168.1.1 and if needed set the host tables of all PCs to the server addresses, fqdn, and aliases this way if DNS fails the system will at least have the host tables to use.