How to configure Sharepoint site for intranet? - sharepoint

I am basically a windows developer and very new to Sharepoint. I have Designed a small site in sharepoint on my virtual PC environment.
I want to access it from out side of VPC environment and also from other local LAN machines [like intranet].
How do i configure (IIS/Sharepoint Adm) to make my site as an intranet site?
I googled it, but not able to get desired information. I don't have much knowledge in ISS setting also, kindly provide any help in layman style.

You need to configure Virtual PC to use Virtual Networking:
In this case a virtual machine acts as
an independent computer in a network
with the host computer. If there is a
DHCP server in the network (Dynamic
Host Configuration Protocol) to assign
IP addresses, a virtual machine will
get it and will work as an independent
system in the network (otherwise, you
will have to specify an external IP
manually)
This is actually the default option in Virtual PC. You should be able to access the VM on the network as you would your own machine. Of course this means the VM's network settings must be valid for your network.
You shouldn't have to reconfigure anything is IIS/Sharepoint Adm to get this to work.

Related

How to make a hostname resolvable within a network without the need to add in hosts file for each computer

I have setup GitHub enterprise in a server for on-premise usage. There it is having a private IP and has to be configured a hostname. It is showing
"Ensure this domain is routable on your network."
If I map the hostname with IP address and add to my windows hosts file, then it's fine.
But I want a solution so that any people connecting to the office network has it resolved automatically without a manual entry in their host file.
If you have enough users of your GitHub Enterprise Server that maintaining the hosts files is a pain, I'd suggest this happens when you have more than 10 users, then you will need to look at a DNS server for your Office Network. If you do not already have one then there are many options open to you depending on what your network looks like.

Can't access my website in Network from VM

I deployed a testing website on my host and want to access from VM.
I setup a network connection and both are connected to a home group.
I can share files form one to another using share folder.
I assigned IP to my website so that I may be able to access using its IP.
When I brows at local using IP. it run perfect.
But when I brows from VM. It gives me error This site can't be reached.
in your VM environment, you need to check networking configurations and permissions.
could be a lot of things, if you could add a picture it would be easier to tell you. if you can't, see if your connection is bridged or not.
also, a good thing to check is that your router has an open port for your VM and allows another connection inside your subnet.
The problem is solved. I dig out and taken 3 steps. and my issue is solved.
I Turn off my windows firewall on host.
Authentications:
i) In IIS I click on Authentication.
ii) Anonymous Authentications Enabled.
IP Address and Domain Restrictions:
In IIS Click on IP Address and Domain Restrictions and Add IP address of VM or
any PC
from where I want to access.
and now it worked.

Azure Nested Virtualization - seamless access to guest VMs

I successfully set up nested virtualization in Azure. Using NAT port forwarding, I can RDP to the guest VMs without any issue. For us, this is not a complete solution as we need to access the guest machine (just on the internal network) by machine name not just through a unique port for each machine. For example, if I have a guest VM called guest1, I should be able to launch explorer and go directly to \guest1\c$ (from not just the host, but from outside the host as well) just as would able to if guest1 were a non-nested VM. All we can do right now is RDP to guest1, that too through a unique port, so guest1:port1 for guest1 and guest2:port2 for guest2.
Is this possible? Thanks in advance!
PS: I followed the instructions here (very useful): https://www.thomasmaurer.ch/2017/07/how-to-setup-nested-virtualization-in-microsoft-azure/

Can not find IP address from other network (iis)

I'm attempting to create a server using IIS.
I created a site. Configured the firewall. It's available in the browser as localhost(http://localhost:8555/) and static IP(http://10.12.66.79:8555/) too
But from another network like my phone. I tried accessing using the static IP but it failed. then I tried using the virtual IP then it show me the login page of my service provider.
what I can do next?
Hope you grab a computer networking book some time to study the basic concepts.
10...* is a private address your ISP gives to your server,
https://en.wikipedia.org/wiki/IP_address#Private_addresses
So that this server can be accessed by other devices on the same network.
Your phone is on another network (via Internet in most cases), so it won't be able to access your server.
To pass packets between two networks, many other devices and settings are required.
If you do want to do experiments, public cloud computing platforms are far better an option, as they can give your server public IP addresses that can be accessed anywhere.
you can change the mobile's default DNS to your system's(IIS) IP may be this could help you but it can be able to run locally only. Make sure that your site is working in your system through the static IP (http://10.12.66.79:8555/) if it is working properly then this could be the only problem change the DNS.

Azure VMs Virtual Network inter-communication

I'm new to Azure (strike 1) and totally suck at networking (strike 2).
Nevertheless, I've got two VMs up and running in the same virtual network; one will act as a web server and the other will act as a SQL database server.
While I can see that their internal IP addresses are both in the same network I'm unable to verify that the machines can communicate with each other and am sort of confused regarding the appropriate place to address this.
Microsoft's own documentation says
All virtual machines that you create in Windows Azure can
automatically communicate using a private network channel with other
virtual machines in the same cloud service or virtual network.
However, you need to add an endpoint to a machine for other resources
on the Internet or other virtual networks to communicate with it. You
can associate specific ports and a protocol to endpoints. Resources
can connect to an endpoint by using a protocol of TCP or UDP. The TCP
protocol includes HTTP and HTTPS communication.
So why can't the machines at least ping each other via internal IPs? Is it Windows Firewall getting in the way? I'm starting to wonder if I've chose the wrong approach for a simple web server/database server setup. Please forgive my ignorance. Any help would be greatly appreciated.
If both the machines are in the same Virtual Network, then just turn off Windows Firewall and they will be able to ping each other. Other way is to just allow all incoming ICMP traffic in Windows Firewall with Advanced Settings.
However there is a trick. Both the machines will see each other by IP Addresses, but there will be no name resolution in so defined Virtual Network. Meaning that you won't be able to ping by name, but only by direct IP address. So, if want your Website (on VM1) to connect to SQL Server (on VM2), you have to address it by full IP Address, not machine name.
The only way to make name resolution within a Virtual Network is to use a dedicated DNS server, which you maintain and configure on-premises.
This article describes in details name resolution scenarios in Windows Azure. Your particular case is this:
Name resolution between virtual machines and role instances located in
the same virtual network, but different cloud services
You could potentially achieve name resolution, if you put your VMs is same cloud service. Thus you will not even require dedicated virtual network.
If your VMs are inside a Virtual Network in Azure, then you have to make sure two things.
Required Port is enabled.
Firewall is disabled on the server.
I was trying to connect to one VM where SQL Server DB was installed, from another VM. I Had to enable 1433 port in the VM where SQL was installed. For this you need to add an MSSQL endpoint to the VM on the azure management portal. After that i disabled windows firewall. Then i was able to connect to the VM from another.

Resources