I have developed an asp.net web site and deployed it to IIS on my local pc. I am trying to set up my pc to be a temporary web server, but no matter what I do, I cannot access it from another machine. I just get a "Server not responding message". I have turned off the firewall and MS Security Essentials, but it is making no difference. All the other tips I have seen do not work.
The trouble is there are so many ways to go wrong here.
You are currently running IIS and not just testing in Cassini?
You can go to IIS Manager and see Default Web Site?
You can do a Browse under Actions when Default Web Site is selected?
You can get to your machine from another machine?
On your machine, can you browse to http://your-machine/your site? (Not just http://localhost).
Ensure that remote access and http access is turned off on your firewall. Are the other machines you've tested within your domain?
Related
I built an ASP.NET Web API. I run it locally from Visual Studio on IIS Express. I need to access this api from other device from another network, so I understand that it has to be hosted on the development machine on IIS, right? What I read is that:
I need to enable IIS Manager in the Control Panel (source) - DONE
Assign the IP of the dev machine to the localhost (source; source 2) - I don't see my site in the IIS Manager under Sites, only see Default Web Site. Why is that?
I assume the site needs to be hosted somehow on the dev machine, because I need to stop Visual Studio, therefore the IIS Express will be stopped and the site would not be accessible, even from localhost right?
My dev machine has a public static IP and I can access this Default Web Site successfully from outside.
You should consider your API in IIS just as any IIS App. i.e. a website.
It needs to have an IP (or a hostheader value)
Lets say api1.example.com binded in IIS with your IIS Application.
Your DNS must resolve this to the IIS machine IP.
then you can access it in that URL.
You can also just hit the machine IP running the IIS web server (on the port you added for the api - if its not :80)
See "Bindings" in IIS
See this Video : https://www.youtube.com/watch?v=I32AnqJzD58
Is it good /Fine to connect website on iis as administrator user and not as regular user given by host company?
I need this to download pdf(rotative) for example..
and i notice that it is obligatory(for default application pool in basic setting to connect as administrator) even to enable the website lunch and work..
so i need to know if connecting as administrator - (in advance setting->identity) or in basic setting - is a problem or not fine for websites and is it true that if:
The web application runs as admin, then anyone who wants to run a known exploit (either in IIS, ASP.NET, Rotativa or your application code), will be able to do so and have access to the entire machine
there must be a load of questions on this but I cant get it working. I have a asp.net app running locally hosted within iis (windows 8/ version 6.2) which I can browse locally. Example below, and it works without a problem.
http://localhost:1234
I'm trying to browse this site from a windows virtual machine using remote desktop and then launching the browser on the client machine. Unfortunately this display "Internet Explorer cannot display the webpage"
any ideas why I cant get through on a remote desktop? The client has internet access obviously and I can ping the other machine (both ways). Is there an IIS or firewall setting I can configure. The firewall on the dev box (i.e. the web server in this situation) has a firewall switched on. When I turn it off I still get the same error message.
My iis authenication settings are shown below (for my website, not for the 'Default Web Site'):
On the client machine, I'm using the following:
http://12.34.56.78:1234
Thanks,
James
Try using https: instead of http: and also to access the website from other PC, you need to enable your Anonymous Authentication. And you also need to Enable the Directory Browsing from IIS settings of website.
Can you ping the ip? Disable the firewall on both machines and try.
Let me know
I recently installed webmatrix on a windows 2008 machine.
I installed dotnetnuke using webmatrix, I visited the site using a browser on the server, finished installing the site, and everything works just fine.
I than created a site in IIS, and pointed it at the folder where I installed dotnetnuke.
When I visit the site using my domain name and on port 80 with a browser on my server, it takes me to the install page. When I visit the site using a remote computer, it says "This site is currently Unavailable Please check back later". Yet, when I visit it on iis express, it works perfectly!.
What is wrong?
thanks!
There are a number of things that could be going on at this point.
Incorrect permissions - Ensure that the ASP.NET Worker Process has full permissions to the DotNetNuke directory. (With IIS Express, you are using your user account IIRC)
Incorrect database access - Ensure that the connection information is correct for the database. As with the above, if the connection for example has a "Integrated Security=true" option defined, you will need to either change this to a SQL account or add the ASP.NET worker Process user to have permissions
It could be a missing Portal Alias, but the current versions of DNN don't have the same issue as you use to.
ALso make sure that the UsePortNumber option in the web.config is set to false.
So, I made a cool demo which I want to show to my friends. But when I give them my IP-address (with the Development server's port and aspx page), it doesn't connect. How can I make it work?
They can't see the development server port.
It only serves pages to browser requests on the local computer.
You have to publish it to your IIS or to another machine that has IIS.
Deploy your site to your Local IIS server
The development server will only server connections from localhost. You need to deploy it to a real IIS server instance. Since you don't likely have Windows Server lying around, you can install IIS on any Professional edition of windows. Then your site will run on port 80, just like any other web site. You still may also need to forward that port on your home router.
Cassini (developers web server) has limitations and doesn't serve http requests from intranet/internet
You should deploy your site to IIS on your workstation (if your friends observe workstation via IP) or use Internet Asp.net Hosting
The development server can only be accessed by clients on the local box. You'll need to host your site on IIS to let them access it (assuming they're on your local network.) If you need to expose this on the internet, you'll have to get a hosting company to do that.
You are probably using the built-in webserver called cassini. By default, that webserver does only accept request from the localhost.
Set up a local IIS, and forward all necessary ports through the firewall
You should find a reliable and already configured webhost and host your site there. The first hit on google for "free asp.net host" was here.