Hosting website from home Windows Server 2008 - iis

I have created a website in asp.net and deployed it on IIS. It is working fine locally. Now I want to access this site on internet. I don't want to buy domain name now. So, I am perfectly fine with the URL like this http://120.89.12.32/MyAppName/Default.aspx
Could anyone assist me knowing that if it is possible for me to host my asp.net application from my home? I am using Windows Server 2008 [R2] Enterprise edition.

Yes you can, but you'll need a static IP address. Most people have a dynamic one, unless they've specifically requested a static one. You may have to pay a small surcharge for static.
You can of course just access your site with whatever the current IP is, but being dynamic it will change from time to time.
Also you'll have to make sure that your router's/modem's firewall is configured to relay requests to your server. And make sure that if your ISP also provides a firewall it is configured to allow inbound requests.

Related

Not able to access blazor website from other computers

I am trying to host a Blazor website on a local Windows machine via IIS, and it can be accessed from the same machine using IP address in the URL like https://10.0.0.123:8080/myblazor, and I also make sure port 8080 is opened on the firewall, but I am not able to access my Blazor website using the same URL from other computers. Does anyone know why? Thanks in advance!
I added another regular website (simple HTML website) and I can access from other computers. So doesn't look like it's the firewall issue or IIS issue.

What is the difference between dedicated server,vpn server and webserver?

I am confussed about 3 server so you guys can help me?A web hosting service is a type of Internet hosting service that allows individuals and organizations to make their website accessible via the World Wide Web is it right?
A webhosting allows you to store the files of your website online.
A domain allows users to request those files and view them on there browsers.
Getting a complete website pakkage should include both of them.
A vpn is a virtual private server. Also used for websites but in this case you need to configure your webhosting and domain al by your self (not recommanded)
A dedicated server is used to host gamerooms etc.

Get domain & subdomain of server by console application

Let's take one case that i hosted my web application on window server 2008 R2 and one exe (console application) running on that server.
I can access that web application by URI:
<subdomain>.<domain>.net , is there any way to get subdomain and domain info from EXE (C#) ?
Thanks in Advance.
The answer is... it depends.
If you only have one site hosted on your box then you can just connect to the local instance via either the IP Address the website on the machine resolves too, or by using http://localhost etc.
When you have a URL, the situation becomes more complicated. The machine could be hosting several websites - how do you know which one you want to connect to? In this instance, I would advise just storing the url you want to connect to in config.
However, it should be possible to list the all of the domains from IIS - you'll need to use WMI.

TFS2010: Single Server Deployment wizard, Bad sharepoint URLs

I just installed TFS2010, and set it up with the single server wizard. It installed me Sharepoint Services an let everything working pretty well.
But, the sharepoint URLs it generates from the Server name "server". As my setup is without a domain, the URLs work okay only from the server computer, not from the others.
I have to give access to LAN clients, and Internet Clients, both connected thought my Public Ip.
How can I change those sharepoint IPs from TFS to be generated From the IP, not from the Server's name??
Thanks in advance
Sharepoint is simply an ASP.Net web application sitting on IIS so all the configuration for host headers etc can be added in IIS itself - if you have multiple instance of sharepoint running on the server, you'll have to add URL's using the sharepoint configuration site but most stuff can be tweaked through IIS (IP's its listening on etc)
If you not on an domainan and want people to have access to the site though you'll have to add your machines IP to the DNS server that you clients are using

Alternative Hostname for an IIS web site for internal access only

I'm using IIS in Windows 2003 Server for a SharePoint intranet. External incoming requests will be using the host header portal.mycompany.com and be forced to use SSL.
I was wondering if there's a way to set up an alternate host header such as http://internalportal/ which only accepts requests from the internal network, but doesn't force the users to use SSL.
Any recommendations for how to set this up?
Daniel, keep in mind that just because something is possbile in IIS, and via any number of off box solutions (like hardware load balancers and SSL) doesn't mean that it is supported by SharePoint, or that it is implemented in the same way.
You can do what you are asking for, however you should do it via SharePoint Central Administration, and "Create or Extend a Web Application" and then "Extend and Existing Application".
In this way you can create a new web site (in IIS) for accessing your existing SharePoint Web Application, one that can be accessed via a different hostheader, port, using SSL, Authentication mechanism, etc.
As a general rule, if you can do something in IIS AND in SharePoint, you should do it only in SharePoint.
Assuming that http://internalportal/ wasn't accessible from outside the company, you could set up two websites in IIS. The first site, configured to use a host header value of 'portal.mycompany.com', would require SSL. The second site, configured to use a host header value of 'internalportal', would not require SSL. The host header value is configured under 'Web Site' -> 'Advanced'.
Having a hardware load balancer makes things much easier. The site on the load balancer is set up to require SSL, and your websites in IIS are setup not to require SSL.
You could just add a second host header and internal IP address to the site for internal non-ssl access
172.16.3.1:443:portal.mycompany.com
172.16.3.2:80:internalportal

Resources