Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
It seems I need to use legacy adapter drivers to get network connections with older version of windows and fedora (fedora 14 and windows xp), but with the newer versions I can use regular network adapters. Is there a way I can install the correct drivers needed for the regular network adapters to connect on the older guest OS's or are the drivers needed to connect incompatible windows xp and fedora 14?
Hyper-V has two kinds of NICs: emulated and synthetic. Emulated corresponds to what your refer to as 'legacy'. Synthetic corresponds to what you call a 'regular network adapter'.
To operate a synthetic NIC, the guest OS needs extra drivers. These are called Integration Services
AFAIK, Hyper-V ships with drivers for WindowsXP. They come in the form of an ISO that you can add to attach to the VM's DVD drive. Under the Hyper-V manager, connect to the VM (select the VM, then use Action -> Connect...), and in the window that pops use Action -> Insert Integration Services Setup Disk. You install the drivers from inside the Guest O/S.
For Linux OS's, you should download Linux Integration Services 3.4, which is the latest at the time of writing. Unfortunately, only CentOS and RHEL are explicitly supported. You can try installing the RPMs that come with Linux Integration Services, but its unclear whether they will work properly.
Good luck!
Update:
Hyper-V drivers have been added to the linux kernel. I posted details on how to determine if they are available with your distro on my blog.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
So the reason I am writing here is because I did not find a solution for this problem anywhere else. Hence, Kindly read the whole post before marking it as a duplicate thread. And if indeed, this question is answered, kindly lead me to it.
So I have a Dell XPS 13 9350 with Windows 10 on it. I installed Virtual Box and run Windows 7 on it. Now here is the problem, the network adapter works fine but it shows as an ethernet adapter and not as a wireless adapter. And I want it to be a wireless adapter so I can connect it to the EZCast Dongle I use.
Here is what I have done so far -
I have left the Virtual Box network preference to default
I have changed the network adapter to Bridge Mode & selected my Wlan adapter on the VM machine settings
Kindly request you all to help me out with this.
Cheers,
Jesse
Connect your dongle with host. Enable USB in virtual box settings and select the dongle.
save configuration and reboot your guest.
Ex:
Maybe you need to download and install the Extension Pack to enable USB ports.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
You may know that windows server VPN often can run on SSTP. Connecting from Windows 10 is pretty easy, but if you have to work remotely from your personal Mac? Mac OS does not support SSTP VPN out of the box.
Below is short instruction what to do if you want to connect Windows SSTP VPN from MacOS
Prerequisites:
Homebrew installed - see here
Run terminal and install sstp-client
brew update
brew install sstp-client
In order to connect to your SSTP VPN with login and password use the following command line:
sudo /usr/local/sbin/sstpc --log-stderr --cert-warn --user <user> --password <password> <server> usepeerdns require-mschap-v2 noauth noipdefault defaultroute refuse-eap noccp
If you prefer to have UI to start your VPN connection you can use iSstp
https://www.axot.org/2015/03/03/isstp-a-sstp-client-for-mac-osx/
I hade some problem with this too, so I deleted one /sstpc and command sudo /usr/local/sbin/sstpc was correct
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I am attempting to pxe chain boot with http download. The problem I am having is the file retrieval always just stops on one of the random files below, at some random % complete. Usually it is the boot.wim, but I assume this is only because it is the largest. It has stopped on a simple font file as well though.
What could be causing this sporadic download behavior?
If I attempt a windows download off the samba share where those files are, the download is 1-2 secs. If I wget it from a nix host its about the same. Only when pxe is attempting to retrieve them does it seem to have an issue. I am fairly new to all this so hopefully I am giving good info. Samba server is running via apache.
I have tried numerous builds of kernel and boot.wim. Frankly, Im at a loss.
<%#
kind: PXELinux
name: Windows PXELinux
oses:
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
%>
DEFAULT linux
LABEL linux
KERNEL ipxe.lkrn
APPEND dhcp && chain <%= foreman_url('iPXE') %>
IPAPPEND 2
the chain then goes to:
#!ipxe
kernel http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/wimboot gui
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/fonts/segmono_boot.ttf segmono_boot.ttf
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/fonts/segoe_slboot.ttf segoe_slboot.ttf
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/fonts/segoen_slboot.ttf segoen_slboot.ttf
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/fonts/wgl4_boot.ttf wgl4_boot.ttf
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/bootmgr bootmgr.exe
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/BCD BCD
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/boot.sdi boot.sdi
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot.wim boot.wim
imgstat
boot
Edit 1:
here is a screenshot showing the connection just freezing. all the established # 0, are the files that worked fine. the one stuck here is the boot wim (this time)
Issue here was the ipxe version on the server was like 3 years old. We git cloned it, and remade(make) the ipxe.lkrn. Files download just fine now.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
My host operating system is Ubuntu 12.04, in which I have VirtualBox installed. Then I have two Windows 7 guest machines configured in the VirtualBox. I need to communicate between the two Windows machines. I have tried using Bridged Networking and Internal Networking with reference to the following article:
http://www.virtualbox.org/manual/ch06.html
I used the same network name for both networking types in my experiments. However, I'm still unable to ping from one Windows machine to the other. If there is anyone who has done this, please give me some guideline how to do so.
Thank you.
It should work with Bridge networking, when both virtual boxes (and eventually also the host) will be on the same LAN.
HOWEVER, Notice that typically Windows will respond to ping request ONLY if there is at least one shared folder! If you don't have any shared folders, Windows will not return the ping, and that's where the problem may be.
So I suggest you share a folder on both Windows machines, set them up with bridge networking and try to ping again.
Hope that help!
Perhaps you could try the suggestions here.
Working solution involves a combination of Bridged Adapter + NAT + Host-only Adapter.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
Is it possible to run more than one virtual machines on my PC using virtual box/ vmware/ virtual pc etc and connecting all of them together? So if i write an application like a chat program or something else, it treats running image as separate machine.
All machines should have different IP addresses and they could have different OS as well.
Please tell me how can i do this.
You will have to start with a machine that has loads of RAM and CPU power. Other than that there is nothing difficult. All you have to do is install virtual box(Freely available) And download several Linux flavors(You can use windows too) mount the drives in virtual box and start creating the machines. You can start all of them together if you want to and they will have different IP addresses.
Read
http://forums.virtualbox.org/viewtopic.php?p=33943#33943
http://www.virtualbox.org/manual/ch02.html
http://www.virtualbox.org/manual/ch03.html
Finally
http://www.virtualbox.org/manual/ch06.html#network_internal