I have recently installed VBox on my Windows 10 Pro machine such that I can run Windows XP Pro 32bit within the VBox. I have successfully managed to load XP SP3, but if I try to access the Internet using IE that is part of XP I get a message saying that the server is not accessible, and any of the suggestions it makes to resolve the problem just takes me back to the same message. (I need XP as I have a number of utilities associated with mobile and amateur radio that I sometimes need to run that require the DOS base on which XP is built.)
If I open a DOS window I can ping the IP address of the W10 PC in the 192.168 address range, I can ping the external address of my main router, and I can ping an outside address, for example bbc.co.uk. which indicates both that DNS is working and I am reaching the outside world. I would like to install Firefox 32bit which will not have the problems that IE may cause. I just cannot understand why this is happening - and although I was a VMWare user/writer before I retired 7 years ago, VBox is a different game to me!
I also have another strange problem within the same operation. I have one machine as described running W10Pro and a second (older) machine loaded with XP Pro which I only switch on when needed. I am trying to run XP within VBox so that I can get rid of my old machine.
As I have only one keyboard/mouse/monitor I use a 2-port KVM switch which requires a double stab on the Scroll Lock key to switch between machines. When I try to shut the VBox down the KVM switch is triggered and it switches over to my old machine, as indeed it does most times if XP throws up an error. I then have no option but to power up the XP machine so that I can switch the KVM back to the W10Pro machine (yes, the KVM switch does have buttons to do a manual change but that is buried against a wall under my desk behind the two desktops so not easily accessible.) I am puzzled how XP or VBox can be sending something that causes the KVM switch to change.
Does anyone have any ideas on either of these issues please?
Problems accessing Internet from within VBox
-
multiOS
- Volunteer
- Posts: 1227
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux, BSD
- Location: United Kingdom
Re: Problems accessing Internet from within VBox
You need to find a more up to date Web Browser that still supports WindowsXP. Internet Explorer, as supplied with WindowsXP, is not compatible with most 'modern' Websites.
-
BillG
- Volunteer
- Posts: 5106
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Problems accessing Internet from within VBox
I use Sea Monkey 2.49.1 (later versions do not like XP) . 2.49.1 works well in Windows XP.
Once you get XP running well in a vm you can turn off the second physical PC and you won't need the KVM switch.
Once you get XP running well in a vm you can turn off the second physical PC and you won't need the KVM switch.
Bill