5

Nothing makes you feel dumber than disabling a NIC while in RDP, but here I am :) I have mounted the volume on another instance and tried editing the registry. I have tried enabling auto logon and using runonce to run a netsh command to enable the NIC, but that does not work. I read something about enabling the NIC through the registry directly, but have had no luck in doing this.

Has anyone dealt with this type of issue? I'm going nuts!

Thank you!

Elad Lachmi
  • 189
  • 1
  • 11

3 Answers3

2

Create AMI from that instance. Launch new instance from that AMI but in VPC, there you will have option to add another NIC. Access through new NIC.

Dusan Bajic
  • 2,056
  • 1
  • 18
  • 21
  • This would work, but I ended up just launching a new instance, mounting the old drive and copying the files over manually. – Elad Lachmi Mar 27 '12 at 13:08
0

If you can, get the AWS instance to have another MAC address. This should cause Windows inside it to think it a new interface, and it should use DHCP by default as well.

draeath
  • 366
  • 1
  • 6
  • It looks like AWS allocates a new MAC each time the instance is stopped and re-launched. This does not seem to help. – Elad Lachmi Mar 26 '12 at 17:12
0

Attach an additional Elastic Network Interface to your instance. If you are in a VPC, make sure to provision in the same AZ and VPC as your instance, ensure the security group you select lets you RDP in. Once the ENI is attached, you will have an additional internal IP, this will allow you to RDP in via this new ENI. Then you can enable the previously 'disabled' ENI or NIC and then detach this new ENI.

Scott Moore
  • 561
  • 1
  • 4
  • 11