Missing NAT driver? - Solved

[markfilipak2]

I had NAT working. Then I fiddled with using Host-Only, almost got it to do what I wanted, then learned that what I wanted to do can't be done, then went back to NAT. But NAT is now broken.
Guest properties show:

[x] Client for Microsoft Networks
[ ] File and Printer Sharing for Microsoft Networks
[x] QoS Packet Scheduler
[x] Internet Protocol (TCP/IP)

Isn't something missing? Where's the NAT driver? Note: I did reinstall the Guest Additions. Log is attached. Thanks in advance - Mark.

VBox.log

(78.22 KiB) Downloaded 19 times

[Perryg]

Post the results of ipconfig /all from the guest.
Make sure that you have dhcp enabled in the guest also.

[markfilipak2]

I got it working, Perry. I looked in another guest to see how it was set up and duplicated the setup.

May I ask a question? Is the NAT driver just automagicially installed & connected? (...I expect to see a driver in the list of Network Properties, but it's not there. That's not true when you use Host-Only. When you use Host-Only there's a Host-Only driver in the Network Properties. It's more the lack of consistency than the technology that trips me up.)

You are obviously very knowledgeable, even for the fine details. May I PM you and explain what I'm trying to do (though you probably already have an idea) and get some advice and perhaps guidance? Regards - Mark.

[mpack]

Is the NAT driver just automagicially installed & connected?

There's no NAT driver as such. With NAT it's the VBoxSVC app which is actually doing all the network I/O, and choosing to reflect some of it into a VM. "Host Only" can't work that way because the physical host is a participant, so there must be a host-visible interface.

[markfilipak2]

Thanks mpack. You guys are doing an excellent job moderating these forums. It's a real pleasure to be here. - Mark.