[2.2.2]DNS stopped working

[kriko]

I have one xp virtual machine and NAT networking suddenly stopped working there.
To be precise - I can ping on outside (direct ip), but xp guest machine it's not able to resolve them, meanwhile
networking on host machine is working as usual without problems.

Network status in xp guest:
IP Address: 10.0.2.15
Subnet Mask: 255.255.255.0
Default Gateway: 10.0.2.2
DHCP Server: 10.0.2.2

What could be the problem?

[vbox4me2]

What are the DNS entries on the Guest?

[sej7278]

why do people use nat/dhcp still these days?

just use bridged and fixed ip with your host's gateway information.

[kriko]

@vbox4me2: DNS is empty

sej7278: I'll try that later.

[vbox4me2]

If the DNS is empty how do you expect the Guest to resolve DNS queries? set dns to 10.0.2.3

[kriko]

If I do that then xp machine crashes (aborted).
It used to just work without any modifications in past....

[vbox4me2]

Strange, have you tried to re-install vbox with the repair option?

[kriko]

I did redownloaded rpm and reinstalled it.
I also installed other virtual machines with xp - same problem.

How does the Vbox internal DNS works? Does it just forwards dns requests to real DNS server?

[vbox4me2]

Try a different network adapter for the VM.

[kriko]

I tried to add another NAT adapter, but virtual machine crashed when enabling it in windows control panel.
I'm attaching log.

[vbox4me2]

Try the intel ones, but get the drivers first (transport them via CD/ISO) install them, reboot and try enabling the VM nic.

[kriko]

No, still no luck.
Shared folders works, pinging ip works, but dns is dead.

EDIT: downgrading Vbox to 2.2.0 doesn't help either.

[vbox4me2]

Configure 2 dns's, the first 127.0.0.1, if that doesn't crash add a second 10.0.2.3

[kriko]

Nope, every restart of network adapter causes a crash.
In every single copy of virtual machine. Will try a clean install (guest), but I doubt it will fix anything.

[vbox4me2]

Or downgrade to vbox 2.1.4