IIS website publishing [closed] - asp.net

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I'm running an ASP.NET web site through IIS from my computer.
I can access this website with ip address from my computer like http://192.168.2.3:81/
The question is how to access this website from other computers?

you need to open 81 port for your site in Windows Firewall on your computer so that you can access it from other computer.
Please refer here

you can access the url within local system without any issues...but if you want to access your website remotely from other system then you must have to allow that port(here 81) in windows firewall...once that port is opened then other machines can able to access your application with that port...
For enabling port in windows firewall do the following steps
1.Start -> run -> wf.msc (Windows Firewall shortcut)
Goto inbound rules -> new rule
3.give the port number as per your requirement
4.Finish
5.Access your application across the world...Enjoy!!!
For complete reference follow the Microsoft official link below
http://windows.microsoft.com/en-us/windows/open-port-windows-firewall#1TC=windows-7

Related

How to publish website but prevent visitors? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I would like to publish my asp.net core to my own domain that is hosted on a shared hosting.
However, after publishing I would like to spend a few hours live testing it (yeah, I have yet to learn auto testing using selenium).
While doing so, I want to prevent visitors from knowing that the site is published so that they won't use it; some strangers know that I will be publishing some time soon and they may have set up auto monitoring.
How can that be achieved?
Best recommendation would be to use a different subdomain if your applications isn't affected by the domain it is accessed on, this will allow the older version to still be used by others. But if you don't mind if others are completely unable to access the system while you are testing, just whitelist only your IP on the domain.
You can setup a gateway for you website.
You can set IP whitelist in the server hosting provider, or you can use a reverse proxy like Nginx to set IP whitelist or HTTP auth before the requests arrive your website.
If the domain doesn't matters, you can use subdomain as Jacob suggests

Connect to website deployed on local machine from anywhere on internet [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I have hosted a ASP.Net website on my localhost within my organisation. I want to connect to this website from any system around the world. I am unable to access it for now. What things should be done to allow access to the website to everyone in the Internet.
The required port(s) need to be opened in all firewalls that are between your web server and the internet.
This can include both software firewall(s) on your server, i.e. firewalld, and hardware firewalls in place as network middleware.

Which IP is picked up when using Remote Desktop? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
This is not a coding question but I can't find a clear answer anywhere so I thought the stackoverflow community will know. Let's say, I'm currently using computer A and running Remote Desktop on Windows to access computer B. From computer B, I sign in to a website. Would the admin for that website be able to tell I was on computer A when I signed in? Or can they only pick up my computer B IP address? I don't know much about networking and remote desktop so any help is appreciated.
Your IP will be of computer B. You can think of Remote Desktop as a TV (with which you can interact) - the images from the remote computer are transmitted to your computer, but all actions still happen on the remote computer.

How to change Skype port in windows 8.1? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
how to change skype port in windows 8.1? Apache/xampp is not running even after changing default value of httpd.conf and httpd-ssl.conf
Modern Skype app uses port 80 by default. There is no option to change the port settings. Port 80 must be forwarded for modern Skype app to operate properly.
Please See this thread.
http://community.skype.com/t5/Windows-8-1-from-Windows-Store/No-proxy-settings-option-in-Windows-8-Skype/m-p/1155558/highlight/true#M299
Uninstall the Windows 8 "app" version of Skype, and download the desktop version from the Skype website (at the time of writing, this can be found at http://www.skype.com/en/download-skype/skype-for-windows/downloading/ ).
You can then go to Tools | Options... | Advanced | Connection as normal.

Serve website off personal computer to internal network [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
Is there a way to serve a site off my personal computer to other computers on my network?
I have a website that I created that I would like to have others in the same building be able to access it, but not over the internet. I would also not like to have to purchase a domain name.
You can have users access a site on your internal network by running some HTTP Server like Apache HTTPD (an easy installer is included in WampServer) or Microsoft IIS.
If you go the WampServer route, it has an option for making your site available to other computers ("Put Online"); this exposes the website to any computer which can reach yours. Other people in your building would be able to type your local IP address into their web browser and access your site.
For example, if your local IP address is 192.168.0.101, users should be able to access your site using a URL like this: http://192.168.0.101/
Yes you can do that. you need to host your web site in your local computer and then others in your local network can access it using the ip address.

Resources