Various Windows techniques using VirtualBox: Difference between revisions
Jump to navigation
Jump to search
(New page: == /etc/hosts equivalent == * The equivalent file is in C:\Windows\System32\Drivers\etc\hosts. You can have multiple hosts on a single line. However, if you want to test a host served by ...) |
No edit summary |
||
| Line 2: | Line 2: | ||
* The equivalent file is in C:\Windows\System32\Drivers\etc\hosts. You can have multiple hosts on a single line. However, if you want to test a host served by the Linux mother host OS, put your actual IP on a private network there (eg, 192.168.0.2), not 127.0.0.1 as it would not work with VirtualBox network bridging. | * The equivalent file is in C:\Windows\System32\Drivers\etc\hosts. You can have multiple hosts on a single line. However, if you want to test a host served by the Linux mother host OS, put your actual IP on a private network there (eg, 192.168.0.2), not 127.0.0.1 as it would not work with VirtualBox network bridging. | ||
== Flushing the DNS cache == | |||
* This can be donw with the following command-line command: | |||
ipconfig /flushdns | |||
Revision as of 10:53, 22 August 2008
/etc/hosts equivalent
- The equivalent file is in C:\Windows\System32\Drivers\etc\hosts. You can have multiple hosts on a single line. However, if you want to test a host served by the Linux mother host OS, put your actual IP on a private network there (eg, 192.168.0.2), not 127.0.0.1 as it would not work with VirtualBox network bridging.
Flushing the DNS cache
- This can be donw with the following command-line command:
ipconfig /flushdns