Hello Louis, > Any idea how VirtualBox was configured for the user reporting the > issue? NAT, Internal Network, Bridged, Host-only? This could answer > the firewall question.
This was discovered to be an issue after the last VirtualBox update by Me during final testing just before the final RC1 release. Basically, It is just a test virtual machine using VirtualBox standard defaults. This was fine in previous versions of VB. But, not now. VirtualBox defaults to NAT. I’ve tried others like Bridged and different NICs. But those mostly don’t work at all. I see there is a “Port Forwarding” in VB advanced networking settings. I don’t know if it was there prior to the latest update to VB. ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
