This is my first go at Sharepoint.
I have installed and configured Sharepoint 2013 in a Single VM according to the Hardware and Software Requirements.
Now I have created a site that has the following url:
http://win-5a8pp4v402g/sharepoint_test/site_1/
win-5a8pp4v402g is the part that got pre-pended on its own. It is the computer name.
I am running the Sharepoint Server on port 6666. Also the VM has a local IP assigned for the moment.
When I access the VM through Remote Desktop, and open the browser in the VM itself, the url above works fine obviously.
My problem is that I want to access this site from another system withing the same local network. I can access the Central Administration from the remote system using the local_ip:6666
But how do I access the site from the remote system?
I am asking because I want to use the Sharepoint REST API to do some tasks from the client side and until and unless I can access the site I cant really proceed. Some help here please? I am a little confused.
Moified /etc/hosts file by adding a mapping of the IP address of the VM in the remote system. Since the VM and the remote system are in the same domain, I did this in hosts file:
local_ip win-5a8pp4v402g
hi if you want configure dns server to all computers, how we can do that, can yop please give the steps,
you means adding the domain to the system or something else
To join CLIENT1 to the CORP domain
Click Start, right-click Computer, and then click Properties.
On the System page, click Advanced system settings.
In the System Properties dialog box, click the Computer Name tab. On the Computer Name tab, click Change.
In the Computer Name/Domain Changes dialog box, click Domain, type corp.contoso.com, and then click OK.
When you are prompted for a user name and password, type the user name and password for the User1 domain account, and then click OK.
When you see a dialog box that welcomes you to the corp.contoso.com domain, click OK.
When you see a dialog box that prompts you to restart the computer, click OK.
In the System Properties dialog box, click Close. Click the button that restarts the computer.
After the computer restarts, log on as CORP\User1.
Related
I've got a website in a DMZ that available on the internet. There is an admin site in our LAN that is used to maintain the DMZ site. One of the functions is to add files that need to be accessible on the DMZ site. There is a section of the site on the LAN site where a user can upload a file, that file needs to get saved to the site on the DMZ I have a share created on the DMZ server and have it mapped to a drive on the LAN computer and I can copy, move, and update files directly on the share from the LAN in windows explorer. However, everytime I try to save a file there from within the website on the LAN server I get a permissions error.
I assume I need to use a different identity for the application pool but I can't figure out what to use. There is a local user on the DMZ computer that has read/write access to the share, I used that user to map the drive from the LAN machine. I tried to set that user as the identity in the app pool but that didn't work. I also tried to create a local user on the LAN machine with the same name and password and use that as the identity, but that also didn't work.
They're both windows 2012 machines.
I figured this out .. it wasn't the application pool identity that had to be changed. I had to change the anonymous user identity associated with the anonymous authentication on the site.
Create a local user on both servers with the same name and password.
On the target (DMZ) server make sure that user has permission to do what it needs to do in the directories.
On the source (LAN) server go into IIS and select the site. Double click the "Authentication" feature then right click "Anonymous Authentication" and select edit.
Chose the "Specific user" option and set it to be the user you created that matches the one on the DMZ server.
There is no need to actually map the drive on the LAN server you can just access it with the UNC path (\server\share).
I am a student and for my dissertation I need to configure a Windows Server to be a file server which uses FTP over SSL for file sharing so a user can download a file from the server.
What do I need to do that in terms of setting up the service and calling it from another machine later on?
Thanks in advance.
Step 1. Install an SSL certificate on the server.
You can buy the SSL certificate from your webhost
Your webhost should also have instructions for installing the certificate
If you can't find instructions, try this: GoDaddy SSL Instructions
Step 2. Set up an FTP server on your Windows server
You can set up an FTP server using IIS (Internet Information Services) which is installed by default on every Windows Server.
Once you open IIS, right click on the Server name and select add FTP Site.
Give it a name and a location where you want to save the files that you'll be uploading
You can leave the IP on All Unassigned and port on 21
Select Require SSL and use the Select button to navigate to your certificate
Enable basic authentication, leave anonymous disabled
Step 3. Grant user permissions
Open Computer Management and navigate to "Users" under System Tools / Local Users and Groups.
If there is no user called ftpuser, create one.
In File Explorer, right click on the folder where you'll be storing your files, select Properties and go to the Security tab.
Click the Edit button, then Add
Enter in the name of your ftp user, click Check Names, then OK.
Your ftp user should now be listed in the security tab. Select this user and then grant Modify, Read & execute, List folder contents, Read, Write. Click OK.
In IIS, select your ftp site and then double click "FTP Authorization Rules". Add a new rule for a specific user (ftpuser) and select Read and Write.
Step 4. Connect to your FTP server from your local machine
There are many ways to connect to your ftp server including a browser or file explorer, but arguably the best way to do this is to use an FTP client.
A good free FTP client is Cute FTP. I recommend it, but there are many others.
After you've installed an ftp client, enter in your host name (domain or server ip), user (ftp user you created), password and port number (should be 21).
Now you can drag and drop from and to your server.
Bob's your uncle.
I can't seem to access my server from the local ipv4 my instance shows in Amazon. When I try to access the website it fails also I couldn't ping to it.
Does anyone know how to fix this or help me if possible.
Thanks.
This is a common asked question which I've read a lot on the internet but couldn't find a clear answer. The problem is that your server instance doesn't allow all traffic which is connecting to your server. You have to open all gates for your server. To do so, login into your account on Amazon. When logged in go to your server instance. Then on your EC2 dashboard scroll down and click on 'Security groups'. After clicking on 'Security groups' from the dashboard click on your last created security group, you can see this from the description of your last created instance. Then select your instance and choose >> 'inbound'. Click to see where you have to click. After clicking on the button 'Edit', add a new line under your RDP connection. The new line has to look like this >>
Click this to see how the line has to look like your connection has to allow all traffic as you can notice.
I have a VPS with Windows Server 2016 Datacenter, which I access through Remote Desktop. I would like to access it through VPN, so I tried to repeat the working configuration I have in another VPS with Windows Server 2008 Standard.
Both servers have a single Network Interface with a public address and a second internal address (10.1.0.1/255.255.255.248). As I said, VPN works perfectly on 2008.
The procedure I followed is described perfectly with screenshots in an article by Thomas Mauer
http://www.thomasmaurer.ch/2016/10/how-to-install-vpn-on-windows-server-2016/
So, briefly, I added the Remote Access role with the Remote Access and Routing features. The role and features get installed without any problem and then I am directed to a wizard, though which I try to initialize the VPN-only feature with a custom configuration. When I finally get into the "old" Routing and Remote Access Management console and try to right-click on the server node to "Configure and Enable Routing and Remote Access" this procedure never ends. A rotating clock icon stays there forever, so I have to kill the management console from the task manager.
When I reopen the management console, either with or without restarting the server, the server looks like running. Then I right-click on the server and select "Properties" in order to define the tunneling protocol for VPN as well as the internal address range that will be provided to the connected clients. The problem here is that this properties popup never gets saved. The "Apply" button does nothing, the "OK" button does not close the form and only the "Cancel" button closes the form without changing anything.
Has anybody seen this behaviour? Am I missing something?
Best regards,
Alex
I don't know why, but for this service to work the user "Network Service" needs to have "Logon as Service" permission, other services do not seam to require that...
You can grant this permission either by using secpol.msc or by just switching the service to run as e. g. "Local System" and back to "Network Service" (empty password fields).
To answer my question, it turned out that, for reasons I don't know, when the routing and remote access was being installed, the "Remote Access Management Service" was not starting. And after the server's restart it was always at "Starting" status.
This service is installed to run under the "Network Service" credentials with an Automatic (Delayed start) start type. When I changed to "Local Service" and manual, I was able to install the Role and initialize it without any problem. And then when I went back to Network Service and Automatic it runs without any more problems.
Strange ...
Alex
i am using php in iis in our windows R2 server, the default localhost path is C:\inetpub\wwwroot and i want to change it to D for the reason that C might be full.
Thanks for the help.
Look here for IIS6:
To change the home directory of a Web site using IIS Manager
In IIS Manager, expand the local computer, expand the Web Sites directory, right-click the Web site you wish to change, and click
Stop.
Use Windows Explorer, to rename the LocalDrive:\Inetpub\Wwwroot directory to the name of your choice. Alternatively, you can copy the
entire \Wwwroot directory tree to a new location.
In IIS Manager, right-click your Web site, and click Properties.
Click the Home Directory tab, and under The content for this resource should come from, click A directory located on this computer,
A share located on another computer, or A redirection to a URL,
depending on where your home directory is located.
In the Local path box, type the path name, share name, or URL of your directory.
Note If you select a directory on a network share, you might need
to enter a user name and password to access the resource.
IUSR_computername is the default account used if another account is
not specified. If you use an account with administration credentials
on the server, clients can gain access to server operations. This
seriously jeopardizes the security of your network. For more
information on security user rights see, "Security Best Practices" in
Help and Support Center for Windows Server 2003.
In IIS Manager, expand the Web Sites folder, right-click the Web site you just changed, and click Start.
Yes you can do.... Just do below steps:
1. Open IIS Manager. For information about opening IIS Manager,
see Open IIS Manager (IIS 7).
2. In the Connections pane, expand the Sites node in the tree, and
then click to select the site in which you want to change the physical path
for virtual directory content.
3. In the Actions pane, click View Virtual Directories.
4. From the Virtual Directories page, select a virtual directory in the list.
5. In the Actions pane, click Basic Settings.
6. In the Physical path box, change the path of the virtual directory content.
7. Click OK.