I have ServiceControl setup on it's own VM and configured to use SQL Transport which I have pointed at the SQL database that's currently being used for NServiceBus. I've opened up port 33333 in the firewall on both the VM and in Azure NSG. I also installed OpenSSH and opened those ports.
On my local machine, I've opened a tunnel to the ServiceControl VM and forwarded port 33333. The tunnel opens without issue. I am running ServiceInsight on my local machine and have it connect to localhost:33333 which is forwarded to the remote VM. It connects without any reported error.
That's it. There is no data displayed in ServiceInsight. No endpoints in the endpoint explorer or anything.
Did I miss something? I'm not sure how to troubleshoot this.
Related
I installed SSL Let's Encrypt on Google Cloud VM and now I can't access SSH connection. I can't even access it via https://console.cloud.google.com. I checked the Firewall rules, and the documentation, but I couldn't find what caused this.
These are the possible reasons why the VM instance have been inaccessible via SSH :
If there are no issues with the firewall rules, you can check if port 22 is open inside the VM instance. You can try using an online port checker to verify it.
After installing Let's Encrypt, your VM instance might have exhausted it's resources causing the service for port 22 to be terminated. I suggest you try rebooting/restarting the VM instance.
Upgrade the machine type of your VM instance incase you encounter the issue re-occurs.
I have an public Azure VM instance running Windows 10 . I changed the DNS to Google DNS and I loose RDP connection. Why?
While changing the DNS servers, please follow below steps:
Changing the DNS servers to Google DNS servers can be done via Azure portal or PowerShell.
From Azure Portal, Navigate to your VNET, click on DNS servers and enter the DNS server IPs.
After doing changes to DNS, Virtual Machine need a reboot. Make sure to reboot the VM.
This change can be done on the NIC of Virtual Machine not on the OS level.
Resize the Virtual Machine, if reboot doesn't restore connectivity. This should return the RDP and the DNS entry you defined.
Try redeploying the Virtual machine.
Otherwise, Try resetting the Remote Desktop configuration.
Try Checking the Network Security Group rules.
Try Resetting the NIC for the VM.
To know more in detail, please refer below links:
Lost connectivity to Azure VM after changing DNS to automatically obtain DNS - Microsoft Q&A.
Cannot connect with RDP to a Windows VM in Azure - Virtual Machines | Microsoft Docs
VM getting disconnected after changing preferred DNS IP (microsoft.com).
Change VM DNS Servers - Microsoft Q&A.
I have spun up a Google Cloud Compute virtual machine. It's a vanilla Windows Server 2016 image, and I can log in and see the desktop. I do that by downloading the RDP file and running it.
Due to a license manager for software I'm installing, I need to VPN to my own network. In "Settings -> Network", I add a new VPN connection (using the same creds I use on my machine) and click Connect. It makes an initial connection, verifies my credentials, but during the final stage, my RDP connection to the GCP VM ends.
What is really strange is that, sometimes, I can reconnect successfully after a few minutes and the VPN connection was successful. Sometimes I can't reconnect.
Any ideas?
The VPN connection added as such will be a force tunneled VPN which then adds a default route over the VPN interface on the VM disrupting your connection. The easiest way for maintaining the connection would be to do either of 2 things
Make the VPN split tunneled and add a route for the licensing box. You can do this by using the Set-VPNConnection Powershell commandlet and then adding a route using the route add command in an administrative command prompt
Add a more specific route for the IP Address by which u access the VM using the route add command
UPDATE: Simply setting the VPN to use split tunneling in PowerShell solved the problem.
Use: (Replace "VPNsName" with your VPNs Name)
Set-VpnConnection -Name "VPNsName" -SplitTunneling 1
I am having some issues accessing the rabbitmq_management plugin.
I am running RabbitMQ 3.6.2, where rabbit is installed as a service and the plugin is enabled. Running on Windows Microsoft Server 2012.
Service runs fine, no errors in logs, however when i try and access the management tool via the web browser UI, "This page can't be displayed", I am sure i am going to the right port as the logs show the port it is running on, i have tried adding some rules to the Inbound on the firewall in case it was to do with ports and nothing seems to work. Any ideas?
EDIT
I am able to access the port via another machine on the network but does still not work in local host.
Yesterday I created an Azure Virtual Machine using the simple Win2008r2 + SQL2008r2 image.
I have deployed a website to the VM via an RDP session.
I am able to browse the website locally (via RDP) using
"http://localhost"
I understand that I need to add an Azure endpoint for port 80 to enable me to browse to the site from an external machine.
I have configured the Windows Firewall on the Azure VM to allow traffic on Port 80 inbound and outbound.
Could anyone please advise what I've missed or what I can do to troubleshoot?
---Update-----
I have learned a little more this morning. The website that I'm trying to host on the VM is an installation of Interwoven Teamsite v7.3.x. When I looked in IIS I could see that the "Default Web Site" was stopped. Another website called "TeamSiteSitePubPreview" had been created but was only bound to port 81.
So, what was presenting the website I could see when I browsed to
http://localhost locally?
I ran netstat -ano and this showed me that PID 1604 what listening on port 80. I then ran Process Explorer which told me that PID 1604 was allocated to "Appache HTTP Server".
I know nothing about About Appache, can anyone tell me if there's some Apache config that will be preventing connections from outside of the local server?
For reference, I just tested this sequence and it gives you a website accessible over the Internet:
Create a new Windows Azure virtual machine with the Windows Server 2008 R2 SP1 image.
Add an endpoint on public port 80, private port 80.
While the endpoint is being created, start setting the server up.
Remote Desktop in.
Add the Web Server (IIS) role with default settings.
Test the connection. You should get a HTTP 200 OK status.
If you want to troubleshoot your server, start checking for errors in the event log. Check also the website bindings in IIS (Port 80, IP Address *).
Also consider the connection issue might be on the client (your) side. For instance, DNS caching. Try connecting from another machine with direct Internet connection (such as another cloud server) or from a service such as isup.me.
Additionally, if all you want is to host websites in IIS, the Web Sites service has a more streamlined experience.
You will need to create an endpoint on port 80 thru Windows Azure Management portal as well. This endpoint opens a port in the Windows Azure Load-balancer.
Navigate to your VM within the portal and create a new Endpoint under the Endpoints screen of VM configuration within Azure management portal.