I am trying to set up the server at an organization I work with to allow me to access a remote desktop from home (or where ever). I tried to set up a port on the internet Gateway to forward to the local IP address of the server. However, there is a router between the Gateway and the server, so the Gateway only recognized the IP address of the router. How can I set it up to remote into the server?
And yes, I am using the ip address from the ISP--not the local ip address of the gateway, router, or server--from external locations.
You need to setup port forwarding on both - router and gateway.
Related
I have a VM running Orion that has an internal status page. Example https://<cluster.com>/internal
I have assigned an external IP to the host and I'm about to SFTP and SSH to the host perfectly. But this internal page requires port 2201 to be open. Which I do have open. But I can't access the site with https://external-IP/internal. If I create a VPN to the network on GCP from my laptop I am able to connect using the https://internal-IP/internal. I'm not a network expert or a GCP expert an help would be welcomed.
This pattern worked for me in the GCP Compute Engine
https://external-IP/internal/internal-IP:2201
I have tried to connect a page which is hosted in ec2 instance. It is showing server timed out error but rest of my collegues able to connect to it.
I use mac laptop
Things i did:
clearing cache
tried to change my network
3.tried in incognito mode
nothing works. Thanks in advance
Things to normally check:
Confirm that the EC2 instance is running a web server (try to access it from somewhere else, or login to the instance and try curl localhost)
Confirm that the EC2 instance is in a public subnet (defined as the subnet having a Route Table entry that points to an Internet Gateway)
Confirm that the Security Group associated with the EC2 instance is permitting inbound access on port 80 (for HTTP) and possibly port 443 (for HTTPS)
Confirm that you are attempting to access the instance via a public IP address (not a private IP address) and that the public IP address is currently associated with the instance
Don't change default NACL rules
You mention "rest of my colleagues able to connect" but you don't mention from where they are accessing the instance. Quite clearly, something is either different with your computer or with the network that you are using. I would suggest you focus on:
The Security Group "inbound" rules, to confirm that they are not blocking access
Try to connect from a different network (eg home vs office vs tethered via your phone) to confirm that your network is not blocking access
If you are connecting from the same network as your colleagues, then the problem is on your computer. This is unlikely because the timeout normally indicates a lack of network connectivity (rather than software configuration).
I have an Azure VPN client that I use for connecting to a web server using RDP and to an Azure SQL Server instance using SSMS. The problem is, I cannot connect to both at the same time.
When I go to the Networking properties of the VPN connection, then select the properties of TCP/IPv4, if I select "Use default gateway on remote network", I am able to connect to RDP, but not SQL Server. If "Use default gateway on remote network" is not selected, I am able to connect to SQL Server, but not RDP.
What can I do to be able to connect to both at the same time?
As far as I know. By default, once a successful VPN connection creates, the highest priority entry will be added automatically in the local machine route table. When you select Use default gateway on remote network, data that can not be sent on the local network is forwarded to the dial-up network when you are connected to a local network and a dial-up network simultaneously. The local network prefers to select a VPN connection route. The connection to a local network is disconnected automatically by default. So you could RDP to the web server via the private VPN connection in the dial-up network. You could not access the Azure SQL server since the traffic from the dial-up network is not allowed in the firewall of Azure SQL server firewall. In this scenario, you could check if the outgoing traffic to the Internet from your dial-up network is blocking.
When you un-select Use default gateway on remote network, usually default gateway of the PPP adaptor will be empty. In this scenario, you cannot connect to resources on the remote network because you have disabled the Use Default Gateway on Remote Network setting in the VPN TCP/IP configuration. You could add routes for the desired VPN subnets. Refer to this paragraph Configuring Split Tunnel for Windows
You could use route print on the local machine to check the route entry. Compare the route table in the two situations. More details you could get from this DOC.
It sounds to me like you need to configure a service endpoint on your vnet to allow traffic to route through to your Azure SQL database.
https://learn.microsoft.com/en-us/azure/sql-database/sql-database-vnet-service-endpoint-rule-overview
Try the link above for help configuring it.
How could to connect to Azure DB from any ip that uses Azure,
Without setting the range 0.0.0.0 - 255.255.255.255 in the firewall?
If by connect to Azure DB from any ip that uses Azure you mean any applications running in Azure, then it is possible to do so. In the portal where you configure firewall rules, simply turn on "Allow access to Azure services".
What this does is that it creates a special firewall rule with Start/End IP address as 0.0.0.0. You will not see this firewall rule in portal though.
To do this thing programmatically, simply create a new firewall rule and set the Start/End IP address as 0.0.0.0.
However if your question is about any client IP address that connects to your database, then I would agree with #Aravind's comment above. You should not allow direct connection to your databases from anywhere but only facilitate it via a proxy service/API layer as mentioned by him.
I have setup a lan with a router, with a few computers connected via both wifi and cables. There are also mobile devices connected to the network.
I have a server running on one of the computers. Other computers can access the server via its hostname (http://myserver:8080/), but mobile devices are not able to.
Is there any softwares or any means I can get the mobile devices to access via server hostname too?
You may need to setup a Name Server (DNS probably) on a computer in your local network. This Name Server should be able to resolve hostnames to IPs (e.g. myserver to 10.0.0.21). Configure your mobile devices so that they use this DNS to resolve device names.