These are the commands i ran Administrator Windows Power Shell to create a host-name site collection to a existing web application
powershell -version 2
Add-PsSnapin Microsoft.SharePoint.PowerShell
New-SPSite http://www.test5.sp/ -OwnerAlias MyDomain\administrator -HostHeaderWebApplication http://Mywebapplication/
In this point i see a new site collection created under Mywebapplication in central admin.
I added a new record to hosts file:
127.0.0.1 test5.sp
And i get ping for test5.sp
I edited the bindings of iis and added a new binding:
Type|Host Name|Port|Ip Address
http|test5.sp |80 |127.0.0.1
And then ran
iisreset /noforce
In this point the test5.sp is not accessible from the browser.
Can you please help?
I managed to access the host name site collection that i created after the following changes:
I changed the iis bindings to be:
Type|Host Name|Port|Ip Address
http|test5.sp |80 |*
For some reason (that i don't really understand) there is a problem to access the host name site collection from a machine that the SharePoint is installed on.
So i added the test5.sp to the host files on another machine:
[The ip address of the webapplication] test5.sp
This solved the problem :)
Related
I developed an Application locally with Angular-7. Eventually, I deployed it to the IIS of a VPS server with IP address 20.20.20.20 (not the real IP). When I run the application as 20.20.20.20, it works perfectly.
Now I want to access the Application with customized name (ePortal). So on the IIS of the VPS server, I made the Host Name to be ePortal. When I typed http://jPortal on the browser url, I got an error that the page cannot be displayed and the url does not exist.
How do I resolve this?
If you want to see your desired name on your local computer only please go to
c:\windows\system32\drivers\etc
And open hosts file using note pad having admin privilege.
and add your IP And your desired name to file and save it.
Now you can browse your server by the name you defined.
My client has server which we developed a new website on. We are trying to point an external domain on another server to this website. Do we just update the A record with the highlighted IP or? See image attached
Probably your WHM control just have the option to do it (update DNS records) automaticaly. But, if don't. Try adding at A records:
ns1.gandlp.com > 162.144.250.139
ns2.gandlp.com > 162.144.250.140
at your DNS Zone Editor control on CPanel
For the default Web Site in IIS I have the following binding on the default website:
I have the following binding on the site I want to access:
When I access the site in the browser with localhost/hostname, I'm pointed to C:\inetpub\wwwroot*hostname*. I have another site set up with a hostname binding that uses the same values for Port and IP Address and it points to the right place (a different folder on my C: drive). I'm running my site locally and I have the correct hostname entry in my hosts file. I don't want to create two separate virtual directories under a single website, I want the sites to be available as separate websites. What am I missing?
When you use the hostname feature in iis, you cant use localhost to access the site any more.
Instead use http://myhostname and setup myhostname to point to 127.0.0.1 in your hosts file.
If you want to access the site via localhost, that implies you need to make a virtual directory, or "application" in iis.
I have a remote connection with server machine. I log in server machine as administrator, open Internet Explorer. If I type both localhost and machine name site works . When I log in as another user and type localhost site works. But when I type the machine name, authentication page comes and when I choose either windows or form authentication nothing happens.
I need to work with machine name otherwise when I try to reach some pages such as approval page I get critical error.
Thank you
Authentication page has a simple JavaScript function which blocks all sites, except Trusted Sites. You need to add "machine name" to trusted sites list in Internet Explorer to activate that JS function.
This is because your System Name is not known in DNS; your remote connection works because the system name is known. When you try to access from the outside it's not.
There is a very quick way to check this; on a connection that DOES NOT WORK, open the Hosts file (c:\windows\system32\drivers\etc) - add the entry: xxx.xxx.xxx.xxx systemanme - for example, 10.0.0.20 MySystem. Save the file then open a command window - ping the server name and it should respond. Try the connection again and you should be OK.
The long-term fix is to talk to the system administrator to find out why the system name is not known on the network (often it can be because only the fully qualified domain name is known).
I have inherited a system with a number of servers, but I have never worked with IIS before.
Currently there is a web server set up using IIS, it holds a number of 'test' sites and the server is called Staging. I have network access to the files on the server and I can login to the server via VNC. What I cannot do is view any of the sites in the 'webs' folder. I know they are all switched on and working as they have been used by my predecessor.
I have tried putting into the url bar the IP address, the IP address with the folder appended, the name of the server and still I cant access the sites.
I am behind a firewall so these sites should be accessible to anyone in the network, but obviously I am mising something.
Any tips, anything I can look at to try and find the site. Annoying thing I only need to look at one of the sites in the D:\webs\test site folder for about 5 seconds :(
Look in the IIS properties of the site and look at what IP address and host header values have been assigned to the site.