Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have an Amazon EC2 Instance running Windows Server 2012. I connect to the instance using RDP.
From RDP, I'm unable to connect to the VPN.
I actually think I'm getting connected to VPN, and immediately, I lose the RDP connection.
I cannot reconnect to the Instance through RDP unless I reboot the instance. But, if I reboot the instance, I lose the VPN connection.
This is happening everytime.
Any thoughts on if at all it is possible to connect to VPN from RDP on AWS.
Your problem is that the AWS server's public IP address is no longer reachable when you start the VPN. What you need is a VPN split-tunneling exception for your source IP address (i.e. the IP address where you initiate the RDP session... not the AWS IP... presumably this RDP session is initiated from India); however, split-tunneling is normally only configurable by the VPN administrator.
If your administrator allows split-tunneling, then you might be able to persuade them to help you make this work.
Another alternative is to ditch AWS altogether and go with a hosting service that offers KVM over IP access to the hosted machine; this would allow you to start a VPN within the windows machine and use the KVM IP address for management while you're connected via VPN. Sadly AWS does not seem to offer KVM services.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
A SOHO network exists with many devices on it including more then 1 server, several end clients and network switchs. Lets say the private IP address for a specific server is 192.168.0.10 we will say the public IP address for the whole network is 11.2.2.11. A device from a different location wants to connect to the specific server mentioned earlier using SSH from 141.10.2.2. With so many devices on the network 11.2.2.11 how does the computer know that 141.10.2.2 wants to communicate with the server at 192.168.0.10? Using putty as an example we know that SSH communicates on port 22, how would the computer know that we want to connect to 192.168.0.10 on the private network and not another one of the servers with SSH setup? Does the person on the private network need to setup SSH to work on different port numbers for each server that is expecting to be remoted into?
For some context i am currently trying to setup a basic Linux server on my own home network and I am confused as to how I would connect to my servers when I am on different networks. I plan to have more then one server and I intend to use virtual machines. I am learning and trying to figure out how i would connect to each server.
You should use ssh port forwarding
let's say you want to connect to the port 22 of the 192.168.0.10 inside the private remote network .
use
ssh -L1337:192.168.0.10:22 user_remote_public#11.2.2.11
this will tell the 11.2.2.11 that you want to connect to the host 192.168.0.10 inside their private network on the ssh port .
now in order to establish the connection you should ssh on your localhost on port 1337 which will then be forwarded to the port 22 of the 192.168.0.10 inside remote private network
ssh user_remote_private#localhost -p 1337
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I am running Tunnelblick from my Mac.
My local network is 192.168.0.0/32 and the network I am trying to connect is 192.168.252.0/22.
Also, I am using a VM (Parallels) running Windows 8.1.
I want to connect to a VPN from my Mac and share this network with my VM.
So, I am facing some problems to do that. Here they go:
When I'm connected to the VPN, my ip address does not change to the ip address from the VPN network. My ip is still 192.168.0.132.
Despite the problem with the ip address, from the host I still can 'ping' the hosts from the network I am trying to connect writing 'ping host.domain.com'. But 'ping host' does not work.
I've already set the network to ‘shared’ in the device menu from Parallels. But, even with this, my ip address from the VM is 10.211.55.4.
In my VM I can't even ping the hosts from the other network
I'm sorry if I wasn't clear enough. All this problem is a little complex to describe.
Something important: The same configuration file I am using works perfectly (without the IP and the DNS problems) when I am using a Windows machine.
Change the VM's network adapter type to "Shared" within Parallels Desktop.
Configure virtual machine
Change network source to shared network
if that still does not work, disable ipv6 in guest machine.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I'm hoping for a high level discussion of this problem I know is quickly approaching my application.
I have a server that binds on a specific port and manages TCP Sockets from my clients. I know that it is common practice to use VMWare to virtualize servers and run multiple servers at once.
How can a single server design be changed to support multiple servers?
Multiple servers can't bind to the same port. If I had to guess I would say a proxy server binds to the port and then sends connections off to the other servers to be handled as if it was still a single server application.
I'm wondering what options there are and what are the common practices for solving this problem?
Thanks in advance!
Each VMWare machine is essentially a standalone PC, as far as the OS running inside a VM is concerned. Like on a real PC, a server can bind to the same port on different IPs, and each running VM can have its own IP on the virtualized network. VMWare has a built-in DHCP router that manages the IPs and network traffic of its running VMs. Each VM can have its own real independant IP on the Host machine's actual network, or they can share the Host's IP via VMWare's built-in router. The OS in each VM doesn't know the difference. Go ahead and bind your server to the same port on each running VM, it will work fine. VMWare will handle the packet routing as needed.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I am developing a windows service application that listens on port 63639
and can get messages an retrive messages
When I do this in the cmd
telnet 127.0.0.1 63639
it get inside and get back the welcome message
but I want to communicate with this application from another computer on the local area network
I have 3 computers on the network with a d-link dsl-2650u router.
My ip address is 10.0.0.3
When I try the cmd:
telnet 10.0.0.3 63639
from another computer I receive "could not open connection to the host, on port 63639"
Then if I try:
telnet 10.0.0.3 80
I am able to get access. I also tried port 135 and that is able to get access also.
That leads me to think the blocking is from my router because I have win 7 and I looked in the firewall logs and I can see the logs for ports 80 and 135 but not for port 63639.
I am very sure that is the router. I also set the router for NAT/DMZ for 10.0.0.3 and it still does not work and I am not able get any log. I also tried defining NAT/Virtual Servers.
Thanks guys, I am going crazy since I have been trying to get it to work for over 6 hours
If you bind to 127.0.0.1, you'll only be able to connect from 127.0.0.1; if you bind to 10.0.0.3, you'll only be able to connect from devices on that network interface. If you bind to 0.0.0.0 you'll able to connect from interface the computer has.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
How do I set up a network between the Host and the guest OS in Windows vista?
Give the guest two network adapters, one NAT and the other Host-only. The NAT one will allow the guest to see the Internet, and the Host-only one will allow the host to see the guest.
One of them also allows the guest to see the host. I'm not sure which, but I know it works since I've tested web server stuff with it. You just have to choose the right IP address, 10.x.x.x or 192.168.x.x.
Also, you may have to be careful about having File and Printer Sharing running on both adapters at once, since the guest will see its own name and conflict with itself. I ran into this during install.
I've got a better answer than my first one.
Give the guest a single Host-only network adapter, and enable Internet Connection Sharing (ICS) on the host. I've tried this on a Windows XP host with a Windows XP guest.
The guest can connect to the Internet.
The guest can connect to the host at an address like 192.168.0.1 (chosen by ICS). -- Remember to allow the guest through the host's firewall.
The host can connect to the guest at an address like 192.168.0.22 (assigned by the DHCP service provided by ICS).
You can do this on a Linux host. I've documented the steps I took in Ubuntu 9.04 here.
I don't run vista, but virtualbox should do most of the setup for you - all you need to do is assign an IP address, subnet mask, and (optionally) a default gateway to your guest OS, and it should just work.
Don't bother with any of the advanced network settings in the options for the VM - they're useful in some situations, but I've never had to use them, and I've been using virtualbox for some years now.
If you post the specific problem you're having perhaps I can help more. But your question is rather vague...