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.
Related
When I connect to a Windows VM using Bastion, I get the error: “A Bastion session should be initiated only from Azure Portal. Please login to Azure Portal and start your session again.” Of course, I am logged into Azure Portal, and I did start it from there. Then I can see the server desktop, but it is dimmed and not responsive due to the modal dialog with the error and a close button.
More details: On the Connect screen there is an “Open in new browser tab” option. If I clear that, then I don’t get the above error, but then screen is just blank. After I click connect, in the lower right corner it shows for a second, "The network connection to the Bastion Host appears unstable." It acts the same if I am on a VM or not. I am using an AD account; it acts the same if I include just the username or name#domain.
How can I get Bastion to work?
I disabled or deleted all my browser extensions, and that fixed it. The problem extension was Wappalyzer.
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
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.
Help! When I try to creat a web site on Azure, I receive the following error message:
There was no endpoint listening at https://geomaster.azurewebsites.windows.net/subscriptions/2762018c-1ace-4b11-a55d-7b69d004cca3/webspaces/eastuswebspace/sites that could accept the message.
I was able to create 2 sites about 3 months ago without any problem. My subscription is an active pay as you go account. I'm not trying to do anything advanced, just a web site connected to a SQL DB. The SQL DB creates without a problem. I was also able to create a virtual Win2008 machine. Azure reps have said my account is fine. I don't know where else to look. Thanks
-ph
If your development machine is behind a proxy server, the problem could be caused by the machine's proxy server settings. Have a look at them via Control Panel / Network and Internet / Internet Options / Connections tab / Lan Settings and try checking the box for 'Automatically detect settings' if it isn't.
Solved: Azure Problem - There was no endpoint listening at that could accept the message
Windows Azure Package Deployment Failed with Error - "There was no endpoint listening"
Same for me. Seems they simply do not have enough recourses atm.
refs:
http://social.technet.microsoft.com/Forums/windowsazure/en-US/611545bc-a061-4107-9240-597b60131b8b/error-creating-azure-website
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/389cba4f-8943-4f56-8b0e-9f9066154337/error-creating-azure-website
Using the new interface for Windows Azure, how do I enable RDP? I am using a cloud service and my site is mysite.cloudapp.net. In my publish settings, I enabled RDP. Where do I find my RDP credentials? How do I enable FTP, if possible? Here are the instructions that I followed:
https://www.windowsazure.com/en-us/develop/net/common-tasks/remote-desktop/
I see no hosted services tab in the new layout.
When I try to RDP, I receive an instant failure message that I cannot connect. I am using Windows 8 and I tried Windows 7.
For RDP, assuming you've followed all the steps and the configuration is right, you need to use the management portal, click on cloud services on the left and select the service whose instance you want to RDP into, select instances in the menu at the top and then pick the instance you want to RDP into.
The bottom toolbar should include a connect option, clicking on it should download an RDP file you can open to RDP into the machine, this will prompt you for the credentials you need to provide (as provided in your project configuration).
You can actually save this RDP file and re-use it for the deployment, but it may become invalid if you re-deploy as port numbers change.
As for FTP, much has been written about it, for example this, but you really need to consider the note in this article, for example - files you upload to the role instance will disappear if the role needs to be recycled for whatever reason.