Can't hit asp.net web on IIS from client - asp.net

I am trying to hit an asp.net 2.0 site that is sitting on another server on my network.
When I run the test site on the server it works : TomsServer:81
However what is the url to hit the same test site when I run it from a browser on another machine on the same network? I tried TomsServer/test but it returns a 404 File or directory not found. How can I access this test site?

check that IIS has an appropriate host header set up on that site and use that host name or that it is accepting all host names

Related

unable to view my IIS hosted site from remote machine but IIS page open

The IP of the machine is suppose 104.68.125.105
In this machine, I configured the IIS server and successfully opened my web app http://merchantcalc/content/lateFine.aspx from inside this machine. This app has default port i.e. 80
But when I tried to open the same web app from remote computer, via url
http://104.68.125.105/merchantcalc/content/lateFine.aspx
I am getting error as ::
Server Error in '/' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
when I open
http://103.69.125.101/ from remote machine, its showing the IIS page.
But why can't I open the web apps? What configuration should I make in IIS to open my web app ?
As Mark said, if you can access http://merchantcalc/content/lateFine.aspx, then you should try http://103.xx.xxx.xxx/content/lateFine.aspx.
Did you host the web site under another website or you just publish the web app as a virtual application under your Default web site? It seems that when you access the website, http.sys is routing the request to Default Web Site. So if this is not the right site that should be routed. You could try to disable Default Web Site and bind your ip address to your web app.
Since there are various kinds of 404 error. You could check the sub-status code by enabling IIS detailed error or failed request tracing.
PS: Expose your public IP address is not recommended.
If you could provide more information, we may get to know how to fix this 404 error.

IIS Server - website keeps showing default page

I currently have a couple of websites setup on an IIS Server. I have setup the Host Headers correctly but whilst testing using the Hosts file (By adding in the URL and public IP address) - it displays the default IIS Start page instead of the actual website, this is the case for all of the websites added to the IIS Server.
Any help would be great.
Many thanks.

browsing with server ip address not loading static content?

I have searched the web i could not find an answer to my problem.
I have windows server 2012 R2.
I deployed a .net website in the server.
browsing the website using the server ip adress does not load the static content (css,images, js) ?
However if I go to IIS and browse the website static contents get loaded.
In the IIS manager, I have binding to the some domain ex.ae.com. but this domain DNS pointing to another server currently. I wanna test my new server first, when things goes fine, i Will point that domain to the new server. But in order for me to do so. I have to first test the current server.
Any reason why browsing with IP address does not load static content ?
Thanks
Have you tried to open to users access to read your path?
User: IIS_USRS
Rights: Read

specify a domain when deploying on iis

I am deploying a web application to a windows server 2008 named jonny521 using IIS7. The domain for most applications on this server is jonny521 however one of the application's domain is jonny521.development.local and I'm not sure how the application got that domain. I want to deploy another application to the domain jonny521.development.local so that it has access to the same cookies.
Does anyone know how I can put my web application in the domain jonny521.development.local?
You can put an application on arbitary domain on your Iis. Just create a new website and in website properties, set the domain as the host name.
The remaining part is resolving the host name by your os so that when you navigate, you get to correct server. You can use a dns server but you can also modify the local host file (system32/drivers/etc/hosts).

ASP.NET and IIS 7.5 - HTTP Error 403.14 - Forbidden

I try to configure IIS 7.5 on a new server (Windows Server 2008 R2), in order to run an ASP.NET 4.0 application. Two "domains" are defined on the server (managed with Parallels Plesk), each one appearing as a site in IIS. One domain is for the public site, the other is used for tests. At the present time, the DNS of the test site points to that new server while the DNS of the public site still points to our old server. We transfer the test site first, to see if everything is OK, before transfering the public site to the new server.
Pointing to the test site in IIS, if I run the Browse command on the folder of the application, I get the HTTP Error 403.14, with the message: The Web server is configured to not list the contents of this directory. The strange thing is this: if I put the exact same folder structure in the other domain on the same server, and I run the same Browse command, I see the default page of the application (I don't know if everything works after that but, at least, the first page shows up as expected). I should add:
Both sites use the same application pool.
Both sites have the same permissions (I checked one by one, also compared with cacls)
The default page is not set in IIS but is the authentication form specified in Web.config
So, same setup but different results. I don't know if there is something else that I should check. I am on very shaky ground when I talk about server configuration and IIS; so I hope that this description is clear enough and makes sense.
I think I found it. It probably doesn't work for both sites on the new server. When I run the Browse command, it shows the page in IE using the DNS of the site. Since the DNS of the public site still points to the old server, the page displayed in IE is not from the folder that I clicked, but rather from the old server site.
I can now look for standard solutions to the 403.14 problem on the new server...

Resources