virtualbox.org

I think the problem arose when I recently installed Service Pack 3 on my windows XP pro guest (windows 10 host). The previously available internet connection is not longer available. I get either "Connected to..." or "waiting for..." which doesn't go away. The computer gets stuck there.

I don't know why Service Pack 3 would cause such a problem. The browser is Firefox. But I also tried Internet Explorer with the same result.

The network is set to NAT, Adapter PCnet-FASTIII. In the advanced it shows some MAC connection and "Cable Connected" is checked. The Port Forward entries are all empty. Changing the adapter to Bridge didn't help.

I would appreciate a solution to it.

If you can ping your gateway,
If you can ping 8.8.8.8,
If you can ping google.com,
VirtualBox is working as it should. You should look other for your networking connectivity. Look for firewalls, proxies, antivirus filters, web-cleaning applications, redirectors, etc. Windows XP is well known to have expired certificates for example and IE6 will not work, with almost no web site of today.

The service pack 3 was installed as it was needed to install Wannabe virus patch from Microsoft.

I tried once again to connect to Providentcu.org. In the status bar it was saying "Connected to 7217018.collect.igodigital.com", and then it gets stuck there. Is this some kind of virus?

Yes, I understand, but WinXP has a lot more worries compared to the Wannacry virus, it's simply that it got a lot of media attention. In any event, if you pass the 3 ping-tests that I told you to try, then it's not VirtualBox.

And as I said in my previous response, connecting or not to a specific website does NOT mean that you have or don't have internet. Only the pings will tell you.

Thank you for your reply.

First, please understand that it was working fine before I installed Service Pack 3. "Look for firewalls, proxies, antivirus filters, web-cleaning applications, redirectors, etc." Whatever these are must have been there before. No?

Could you please give me instructions as to how to ping?
What would be my gateway?
And how would I ping 8.8.8.8 and Google.com?

I will try these pings once I know how to do it.

You open Command Prompt. You give it the command:

• ping 8.8.8.8

If you get back response times in ms, you're pinging (that's Google's DNS server). Then

• ping google.com

Both pings are successful (TTL:52 and TTl:53).

Now, how do I ping gateway?

Gateway = router. But it doesn't matter anymore, once you can ping 8.8.8.8, that means that you can get outside your home and on the internet. Once you can ping google.com, that means that you can resolve hostnames to IP addresses. Both of these together mean that you have an active (alive and kicking) internet connection. VirtualBox has done it's job.

Why you can't access a specific website, with a specific browser on a specific OS, that's not a VirtualBox problem, so it's best if you treat it like that. I gave you some ideas. Firewalls and antivirus are not only on the guest, they're on the host too. There's a gazillion of thing that can go wrong; none of them has anything to do with VirtualBox.

Thank you so much. I will work from there.

I can't remember what happened as a sequel to the last query I made. But when I recently opened the XP browser, (It still has Service Pack III) I couldn't connect to the internet. And I worked on changing settings and all that.

And just now after I reviewed the previous postings, I pinged 8.8.8.8, and I got the reply: "Destination host unreachable." When I wrote ipconfig in cmd, I got the error: "Eternet adopted LA connection 5. Media state: Media disconnected. Tunnel adapter Toredo Tunneling: Pseudo interface. Connection Specific DNS Suffix: IP address: fe80: ffff:ffff:ffff:fffdx5. Default getaway: ….

Under Event viewer: I found sever system errors in Service Control Manager.

When I entered any address in Firefox I get the message "server not found. "

These are the settings in Networking under Xp in Virtual Box: Attached to NAT, Advanced: Adapter type Intel Pro 1000 MT Desktop (8254OEM).

And finally, under Local Area Connections Properties: TCP/IP properties: IP address: 192.168.1.2; subnet mask 255.255.255.0; default getaway: 192.168.1.1.1. Under DNS Preferred: 202.96.134.133. Alternate DNS: 202.96.134.134.

I have downloaded and installed PRO2K3XP_32 on the XP. All these are a result of the various suggestions I followed from different sources.

I don't know much about configuring networking. But I am hoping you could help. The Host is Windows10.

Thank you.

Thank you.

open a command prompt in XP and type:

ipconfig /all > c:\ipconfigXP.txt

Find the file c:\ipconfigXP.txt in the XP C drive, transfer it into the host PC and zip it, and post the zip file, using the forum's Upload Attachment tab.

Also, open the main Virtualbox window, right click the XP guest in the guest list, and choose Show in Explorer. In the folder that opens, find the .vbox file, zip it, and post the zip file, using the forum's Upload Attachment tab.

Why did you decide to update the NIC driver using Pro2k3xp_32 ? Were you having problems with the NIC?

I have never had any problems with the standard driver supplied by Microsoft.

1) I have attached two zip files from the current state. Let me explain some changes that I have made since yesterday.
After I read my previous postings, I decided that the Service pack III is what caused the connectivity and I have uninstalled it. The results are not much better. I have removed all the settings in the NAT or whatever settings. And reinstalled Firefox. Neither IE or Firefox still connect. I still the get the message "server not found" in Firefox.
2) Why did I decide to update the NIC driver? Because that was one of the suggestions I found on the Internet.
3) Since I didn't have any luck with any of the above, I have installed another instance of XPPro, this time without adding SP2. Now there is connectivity, although very limited on IE (that's probably because that version of IE is not so great. Firefox connects to everything, but it's pretty slow.
These are the current results, and if either of you could help in anyway to make things work or work better, I would appreciate. Thank you both.

Thanks for posting the zips. However, if this:

Moorty wrote:I have installed another instance of XPPro

happened after these zip files were made, then the files are old data.

Moorty wrote:Now there is connectivity

Good, so the network and internet are working again.

Moorty wrote:very limited on IE

To be expected. XP's IE, even if you got SP3 installed, would be way too old and incompatible for modern internet.

Moorty wrote:Firefox connects to everything, but it's pretty slow.

Provided you did not install extra drivers in the guest, this could be because the last version of Firefox that is XP compatible is pretty old now too.

I don't think there is much more Virtualbox can do. Let's go back to Socratis' post above:

socratis wrote:once you can ping 8.8.8.8, that means that you can get outside your home and on the internet. Once you can ping google.com, that means that you can resolve hostnames to IP addresses. Both of these together mean that you have an active (alive and kicking) internet connection. VirtualBox has done it's job.

Whatever you want to do beyond getting a running guest OS and an active internet connection is beyond the support scope of the Virtualbox forums.