This is driving me nuts. I am trying to setup a webiste on our dev server with a specific url name www.mystpidsite.com as an example. mystupidsite is not the same name as the dev server.
1) specify a specific url to use for the website I create in IIS
2) run it and use that url to access it
I have:
1) created a new site in IIS 7 in Server 2008
2) attempted to access it via the site name which I set to the desired url and port 8888. So if we want it to be www.mystupidsite.com I setup the website name to mystupidsite in IIS 7.
3) I even tried to create an application under mystupidsite with the same name in IIS 7.
The server is definitely accessible and pingable on the network from my local PC, we have other stuff installed on this new server. Do I need to create an application or is just creating the website enough in IIS 7? I specified the IP as the server's IP in the website I made.
For the host name in the bindings of the site I put www.mystupidsite.com
when I try to access the site via www.mystupidsite.com it can't find it and the site in IIS7 on the dev server is running. It's running on a HyperV instance which is our dev server. Everything else has worked just fine. I just wnat to understand how to get a specific url by name setup.
Do I need to add something in the hosts file on the server or something?
You're not going to be able to have a site on your dev box answer to both the mystpidsite.com and mystupidsite.com domain names.
Unless you have the domains registered and have your domain's nameserver directing that name to your dev machine, IIS is only going to answer to requests either the machine name on the network or the IP address of your machine (in addition to 127.0.0.1 and localhost).
The only thing you're going to be able to do outside that scenario is set up two sites on two different ports on your machine and access them from http://localhost:80 and http://localhost:8888 (or network computer name equivalent).
you need to have an entry in dns to be able to hit the server when using www.mystupidsite.com
Because you have the site running on an alternate port you should be able to get to it by http://your-server-IP-address:8888
If you want to test it locally using the host name and do not have access to dns you can add the appropriate entries to the hosts file on your local machine (c:\windows\system 32\drivers\etc\hosts)
What happens when you type 'nslookup www.mystupidsite.com'? Do you get the IP address of the virtual server?
Do you have the windows firewall enabled on the server? if so, did you add an exception for port 8888?
add a default binding (no host header / blank) and try accessing it by IP
Related
I am trying to set up a secondary web site hosted on our local domain controller running IIS-8.
I already have one site working successfully thought our network, the default site.
I have successfully got the second one to work on the localhost (the domain controller Server 2012-R2), but I can't seem to access it from any of the other workstations on our network.
I added the new site.
Set the binding to IP address:192.168.1.1, Port:80, Host Name:dyo.mysite.com
I have modifed C:\Windows\system32\drivers\etc\hosts to show 192.168.1.1 dyo.mysite.com, and I have added an alias to the forward lookup Zone in the DNS Manager. (Name:byo.mysite.com, FQND:byo.mysite.com.mydc.com, Target Host: 192.168.1.1)
I can't seem to access the site from any of the network work stations. I have tried many combinations of addresses, http://byo.mysite.com, 192.168.1.1/byo.mysite.com, \mydc\byo.mysite.com, etc.
I would imagine that I am probably missing something simple. I just don't know it is.
Any insight would be greatly appreciated.
To get your server accessed from other workstation. You have to promise
Your IIS site can be accessed via IP address directly.
the client workstation is using your DNS
Your client workstation is not bypassing your DNS server by .pac proxy
So could you get access the website via IP address by disabling default website and set the site to unassigned IP or 192.168.1.1 with null domain name?
If you want to access the website via byo.mysite.com. Then you shouldn't set FQDN like byo.mysite.com.mydc.com. because Web browser will never consider byo.mysite.com as an alias but a different server. That's why When you set FQDN like byo.myDC.com, you could get work by access http://dyo and you could also access website via byo.mysite.com.mydc.com but fail with byo.mysite.com.
How to set DNS correctly
To get it work, please create an new primary Forward Loopup Zone named mysite.com. Then create a new HOST(A) record to map to your machine name like dc.mysite.com and 192.168.1.1. Then create an Alias(CNAME) called www to map to this A NAME. Then the FQDN will be www.mysite.com.
Finally bind your IIS site and access the website should work.
PS: Please make sure your other workstation is not using a proxy.
I have got a strange problem while setting up my .NET website on IIS server on Amazon EC2 instance.
I have created a new website giving its path to my website folder in IIS 7.5.
I have given the ip address and DNS in domain settings.
And configured the host name in bindings section of website with www.domain.com
I am able to browse it through the IP address but not able to browse it using domain. It is showing some service page...
Can any one help me?
You need to configure your host header in IIS. Here's how to do it on IIS 6.0 for example:
http://www.visualwin.com/host-header/
Also, does www.domain.com actually resolve to your IP address?
It sounds like the A record for for the domain isn't set to the correct IP address. Have you confirmed that the changes took AND that they've propagated to your computer? If you ping www.domain.com, do you get the correct IP?
Hi i am developing a website and want to test it on local machine
the flow is like this:
A -- my website
B -- third-party website
From A a request is sent to B with a url eg: http://mywebsite/abc.aspx which is a url on which B reports success or error.
so i need to define the url to report to
for this i need to give a absolute url or path.
thats why i cannot test it on local machine and have to upload it and test it.
but this doesn't allows me to track down errors and debug it.(through break points.)
so i am trying to get the local machine address like "http://123.456.7.8/abc.aspx"
but doesn't seems to work.
my pc is running on windows xp and is connected to router and my pc is in a network and i think that's why gets a dynamic IP.
have also tried public ip address but no luck.
any work around or help for this.
I believe you're trying to get an external website to contact your local PC. Your local PC is behind a router and getting a private IP from your local router.
You'll need to supply the external website with an address that has the external IP of your router and configure your router to forward incoming requests to yuor PC.
i.e. to forward port 80 on the router to port 80 on your XP machine.
Thus when the external website, tries the contact http://1.2.3.4/abc.aspx it will talk to your router, that will then pass ("forward") the request onto your PC at e.g. http://192.168.0.1/abc.aspx.
I believe You can try to use your Machine name.
You can set up a local DNS server or simply utilize hosts file, to cheat your web browsers. For example, register test.com to your machine's IP address, and then you can use http://test.com to access IIS default web site (or your web site on IIS if you configure it for the default URL).
http://en.wikipedia.org/wiki/Hosts_%28file%29
This is a typical approach to test out web application locally.
try hosting your website on IIS and then give fix IP to your system and try to access it with your IP. Another thing is get your global IP (you can check it from Whatismyip.com ) and set it in your binding in IIS for getting request to it from across the internet.
I have application..its runnning on my localhost.. i need one more machine to access that application.. but when in tht link i type my IP address instead of localhost.. it showing cannot find server.. can you plz tell me steps what i need to do in orderr to access appplication to other machine.. as such there is no UAT server as of now...
First off, make sure your firewall allows access through port 80.
Then, check if your IIS allows access from outside IP's.
I can help more if you provide this:
Your OS (XP, Windows 7, etc)
the local link to your app. Is there a port number needed to access the app?
LaterEdit: Ok, then you need to do this:
Now, your app will be served by IIS on port 80 (default). Check your firewall to allow traffic through this port.
If you IIS is set for another port, then use that one.
Checking the port in IIS:
I'm going to assume that you are running the application from Visual studio which allows the localhost to run.
In order for your application to be available to other machines on the network, you have to ensure that IIS is installed on your development machine and then a website is set up for that application as well.
The application existing in IIS is what will make it accessible across your network.
I want to run my web application in another machine.My problem is that i have already created virtual directory in iis 7.5 and add web application in it. Its running in my machine properly but i am trying it run in another machine through url and add the ip address along port number but its not found the web page.Plz help me .
What you need to do is go to the machine on which you want to run your web application, then set up a virtual directory on that machine. Make sure port 80 (or whatever port you decided to run your web application on) is open on the firewall (probably Windows firewall) too. Then you can access your web app on the other machine with a url like http://hostname, where hostname is the NetBIOS name or IP address of the machine you want to access.
If you get a timeout, then IIS isn't running or the firewall is closed. If you get a 404 error, then your virtual directory isn't set up correctly or you typed an invalid URL.