I'm running an Ubuntu 14.04 LTS LAMP server on Hyper-V, which itself is running under Windows 8.1. When I first set it up on my usual home network, I set it up with an 'External' virtual switch (VS1) which connected the VM to my laptop's NIC, and made the server available around the rest of the network as 192.168.6.42. So far, so good and having got that far, I successfully installed a copy of the b2evolution CMS, which I could then access, not only from Win8.1 via a browser on 192.168.6.42/b2evolution.
Fast forward a week or so, and I needed to take the laptop into the office, where there was no WiFi available initially. I tried connecting to the copy of b2evolution I'd installed when all was well, but the browser was no longer able to find the server and gave me the message "This web page is not available". Whilst eventually, I found myself a WiFi feed, the IP range wasn't what the server was used to seeing, and I still couldn't get connected.
Taking it back home didn't improve matters - I could still not get a connection despite the laptop being back on its usual IP address. The end result of the above was that I ended up re-installing b2evolution, with it picking up an IP address based on what the laptop's NIC was assigned. Where I am now, it's using 192.168.0.13 and b2evo is working just fine again. The problem will come when I take the laptop elsewhere, as I'll need to do shortly.
What I need to understand is the best approach to configuring Hyper-V and the Ubuntu VM on it, so that I can target a single IP address and/or computer name, regardless of where the laptop is, or IP address its NIC picks up.
Anyone care to offer suggestions?
Fast forward a week or so, and I needed to take the laptop into the office, where there was no WiFi available initially. I tried connecting to the copy of b2evolution I'd installed when all was well, but the browser was no longer able to find the server and gave me the message "This web page is not available". Whilst eventually, I found myself a WiFi feed, the IP range wasn't what the server was used to seeing, and I still couldn't get connected.
Taking it back home didn't improve matters - I could still not get a connection despite the laptop being back on its usual IP address. The end result of the above was that I ended up re-installing b2evolution, with it picking up an IP address based on what the laptop's NIC was assigned. Where I am now, it's using 192.168.0.13 and b2evo is working just fine again. The problem will come when I take the laptop elsewhere, as I'll need to do shortly.
What I need to understand is the best approach to configuring Hyper-V and the Ubuntu VM on it, so that I can target a single IP address and/or computer name, regardless of where the laptop is, or IP address its NIC picks up.
Anyone care to offer suggestions?