Can I connect a external network adapter to Window Server? - amazon-web-services

I want to connect an external Wi-Fi adapter from my local PC to a Windows Server in AWS.
Is it possible?

It appears you are wanting to make your local wifi (eg at home or in the office) accessible to an Amazon EC2 Windows instance.
This is not a capability provided by AWS.
You might be able to find a software product that can extend a USB device or a network connection between two computers across the Internet. For example, I have seen people use a virtual serial port to allow a "dongle" to be connected to a virtual computer. However, any such solution is something you would configure in the Windows operating system and your own computer. It would not have anything specific to do with Amazon EC2.

Related

Is it possible to map a EC2 drive to a local drive with a letter?

In one of our client scenario each laptop running a client software has to have a mapped S:\ drive.
Earlier they would map this S:\ drive to a drive in a Server on the same network like \\Server-name\$D
Now they are planning to move this server to EC2 in AWS. Is it possible to map the drive from EC2 server in local machine?
Local machine is in aclient network connected to AWS via VPN and DirectConnect.
In my research online (I am trying to map an Amazon EC2 drive to a local machine), I came to know that you can enable a VPN on EC2 server to make this happen. But I am looking for a inbuilt windows option as this is a as-is migration to AWS.

Unable to map to share on AWS Ec2 from office, works at home

I've setup an Ec2 instance of Windows server 2016 on AWS.
I can map to a shared drive on this instance from my home (desktop, and laptop) and mobile device. I use domain from home, and IP on mobile.
I bring my laptop to the office and am unable to map to the drive. I have access to RDP still, but no SMB. I believe this is blocked from the ISP.
I tried connecting from home, while connected to a different location on ExpressVPN, and was unable to connect.
The instance hosts software used by the company. There is a DB on the instance and the software on the workstations/endpoints is able to connect to the DB on the instance.
I read I should switch the SMB port to 80. I opened some ports, but still can't connect.

Connect via VPN to third party from AWS

We have a number of 3rd party systems which are not part of our AWS account and not under our control, each of these systems have an internal iis server set up with dns which is only available from the local computer. This iis server holds an API which we want to be able to utilise from our EC2 instances.
My idea is to set up some type of vpn connection between the ec2 instance and the 3rd party system so that the ec2 instance can use the same internal dns to call the api.
AWS provide direct connect, is the correct path go down in order to do this? If it is, can anyone provide any help on how to move forward, if its not, what is the correct route for this?
Basically we have a third party system, on this third party system is an IIS server running some software which contains an API. So from the local machine I can run http://<domain>/api/get and it returns a JSON lot of code. However in order to get on to the third party system, we are attached via a VPN on an individual laptop. We need our EC2 instance in AWS to be able to access this API, so need to connect to the third party via the same VPN connection. So I think I need within AWS a separate VPC.
The best answer depends on your budget, bandwidth and security requirements.
Direct Connect is excellent. This services provides a dedicated physical network connection from your point of presence to Amazon. Once Direct Connect is configured and running your will then configure a VPN (IPSEC) over this connection. Negative: long lead times to install the fibre and relatively expensive. Positives, high security and predicable network performance.
Probably for your situation, you will want to consider setting up a VPN over the public Internet. Depending on your requirements I would recommend installing Windows Server on both ends linked via a VPN. This will provide you with an easy to maintain system provided you have Windows networking skills available.
Another good option is OpenSwan installed on two Linux system. OpenSwan provides the VPN and routing between networks.
Setup times for Windows or Linux (OpenSwan) is easy. You could configure everything in a day or two.
Both Windows and OpenSwan support a hub architecture. One system in your VPC and one system in each of your data centers.
Depending on the routers installed in each data center, you may be able to use AWS Virtual Private Gateways. The routers are setup in each data center with connection information and then you connect the virtual private gateways to the routers. This is actually a very good setup if you have the correct hardware installed in your data centers (e.g. a router that Amazon supports, which is quite a few).
Note: You probably cannot use a VPN client as the client will not route two networks together, just a single system to a network.
You will probably need to setup a DNS Forwarder in your VPC to communicate back to your private DNS servers.
Maybe sshuttle can do, what you need. Technically you can open ssh tunnel between your EC2 and remote ssh host. It can also deal with resolving dns requests at remote side. That is not perfect solution, since typical VPN has fail over, but you can use it as starting point. Later, maybe as foll back, or for testing purposes.

VMware Workstation Player bridged connection doesn't work

I tried to use bridged connection VMware and Virtualbox but doesn't work.I need a router ? or I need another wireless adapter?
Brigde mode means that VM's network cart simulates connection to your real physical network. You may setup static IP, mask and gateway of your network or obtain them by dhcp (yes, you need router to configure your local network).

VirtualBox machine - Set to access LAN only

I've got a VirtualBox machine set up and it runs fine. But I want to limit it's network access to only computers on my LAN (192.168.2.x). I do not want it to have any type of incoming or outgoing access to the internet at all.
Just remove the Default Gateway in it's IP settings. Or modify the operating systems hosts file.
If your really serious about blocking it though you should block it via a firewall.