Quick network question, NAT vs Bridged

[tk_]

I tried searching the forums, and I don't get what I need from the user manual on this...

VB 3.1.2
Host: XP Pro SP3
Guest: XP Pro SP3

Is it not possible for the guest to see the host (other than using the Shared Folder) when the NIC is set to NAT? I like the protection NAT gives me vs Bridged, but I can't browse my host from the guest using NAT, unless I have something misconfigured.

Also, if I change the NIC to Bridged, I'll be able to browse the host, and still get to the Internet, right? (I just lose the 'security' that NAT provides.)

Thanks,
tk

[jorgensen]

You are completely right.

For NAT networking you will need VPN or FTP, but maybe NAT + Host-only networking connection could do the job for you.

[tk_]

...but maybe NAT + Host-only networking connection could do the job for you.

Ahhh! Now there's something I hadn't thought of. Outside the box thinking, I like it and I'll try it!

[MarkCranness]

Is it not possible for the guest to see the host (other than using the Shared Folder) when the NIC is set to NAT?

It is possible to see the host for TCP/IP connections, but probably the host will not appear (be 'browsable') in the guest's 'My Network Places / Microsoft Windows Network'.
It will not be 'browsable' because it is on a separate network.
However, if the host has File and Printer Sharing enabled, the guest can connect to a host network share and browse the files on that host network share. If the host has a web server, then the guest can connect to that webserver and browse web pages.

I like the protection NAT gives me vs Bridged, but I can't browse my host from the guest using NAT, unless I have something misconfigured.

I'm unclear on what protection (if any) NAT provides compared to bridged... I think NAT protects the guest somewhat, but potentially exposes the host somewhat.
See here: http://forums.virtualbox.org/viewtopic.php?f=1&t=27295

Also, if I change the NIC to Bridged, I'll be able to browse the host, and still get to the Internet, right?

Yes.

[tk_]

maybe NAT + Host-only networking connection could do the job for you.

Well, I tried NAT on one NIC, and Host-only on a second NIC, didn't work. Kept getting duplicate name on the network, and still couldn't get to the host.

Guess I'm left to using Bridged as MarkCranness suggests. My understanding of NAT and the advantage it provides is that all traffic is routed through the NIC on the host via the NAT and segregated before going on. I'm probably just confused about this since I'm fairly ignorant about these.

Thanks for the help jorgensen and MarkCranness!
tk