NAT does't work with Backtrack

Ehlo!
I have a backtrack 5 installed on VirtualBox on Windows. NAT doesn't work. My network adapter is not recognized. Ping response used for internet connection test (unknown host) + airmon-ng doesn't show any network interfaces.
I didn't find a VBox.log to post here. Bridged network works but it emulates a cabled connection and I need my network adapter to be recognized by Backtrack (hence NAT needed!)
WICD doesn't show anything and gives this error:
"Could not connect to wicd's D-Bus interface"
I understand that this might be VirtualBox's configuration and so I've posted to both forums.
Has anyone had previous experience with this?

Your wireless adapter on the host will be seen as cable inside a virtual machine, unless you have an USB adapter.

Thanks for the reply sickness.
So:
1. Just making sure, but even if I'm using NAT (which by definition emulates a Router) i'm still going to get a cable connection in the virtual system?
2. My primary goal is capturing data packets with airodump-ng. If my adapter is not supported on Windows, is it going to make a difference if I use Backtrack?
3. Is there an alternative program to airodump-ng that works with aircrack-ng?
4. Is there any other ways to still use aircrack-ng if my adapter is not supported?
Thanks a lot again for the reply.

Wich usb adapter are you using

VM will make your host adapter appear as wired, to be able to use wireless you need a USB adapter.
The other questions you can answer by documenting yourself :)

Thanks again for the reply. I liked backtrack enough to re-partition my hard disk and install it as a native OS!:cool:
But the issue still remains unresolved: Why didn't NAT function properly? Bridged network works fine but if I choose NAT as the networking method, my adapter doesn't show up at all.
I'm on a Dell Laptop, using Backtrack 5 R3, VirtualBox on Win7 as VM. Network adapter is a Realtek. AT&T U-Verse router (if it matters) and that's about all the info I can think of.
Thanks again for the answers.

This at the end of the day is how VMware is built, if you want more details for how it works or why it doesn't work as you wish I suggest you contact them.