Timeline for VM Pulling IP out of my DHCP Range
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 26, 2016 at 11:23 | history | suggested | user656765 | CC BY-SA 3.0 |
Added images
|
| Oct 26, 2016 at 10:38 | review | Suggested edits | |||
| S Oct 26, 2016 at 11:23 | |||||
| Jun 8, 2016 at 15:28 | vote | accept | Thomas Hutton | ||
| Jun 8, 2016 at 15:16 | answer | added | GiantTree | timeline score: 1 | |
| Jun 8, 2016 at 15:14 | comment | added | Thomas Hutton | @GiantTree Haha, that fixed it! Thanks so much! | |
| Jun 8, 2016 at 15:12 | comment | added | Frank Thomas | Set your VM to use a BRIDGED network connection. When using NAT networking the IP is automatically assigned in the 10. range, and is on a differant network than the physiical LAN. changing to bridged mode will cause the VM to pull from the DHCP server and participate in the LAN directly. | |
| Jun 8, 2016 at 15:11 | comment | added | GiantTree | You are using a virtualized network (a private network only accessible to your PC and your VMs). Use a bridged or NAT connection to get your server into your local network. | |
| Jun 8, 2016 at 15:08 | history | asked | Thomas Hutton | CC BY-SA 3.0 |