Opened 15 years ago
Closed 15 years ago
#6415 closed defect (worksforme)
NAT: can't create datagramm socket
Reported by: | Raveman | Owned by: | |
---|---|---|---|
Component: | network/NAT | Version: | VirtualBox 3.1.4 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description
I get this error in the log file. VBox running but i cant connect from outside.
Attachments (1)
Change History (7)
by , 15 years ago
comment:1 by , 15 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
follow-up: 4 comment:2 by , 15 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Connect from outside = via vrdp connection and this is works with NAT ... i get this error randomly (guest run for a while and i cant connect via vrdp what when the guest started worked of course) i need restart guest and again works for a while. i have 10 vps / host so havent a day without this error of course until i havent restarted the guest in guest no network i run some netapp in background. this is the nature of NAT?
comment:3 by , 15 years ago
If you are using RDP to connect to the VM then this has nothing to do with NAT. However, the NAT error in your VM shows indeed a NAT problem.
comment:4 by , 15 years ago
Replying to raveman:
Connect from outside = via vrdp connection and this is works with NAT ... i get this error randomly (guest run for a while and i cant connect via vrdp what when the guest started worked of course) i need restart guest and again works for a while. i have 10 vps / host so havent a day without this error of course until i havent restarted the guest in guest no network i run some netapp in background. this is the nature of NAT?
Could you please describe what applications are working in your guest? It looks like problem is with applications using UDP. I'll upload debug bits to fetch more information about failure nature.
comment:5 by , 15 years ago
Could you please do the following:
- Download VBoxDD.so and corresponding binary in your installation (please don't forget save original copy).
Note: debug bits are closer to 3.1.6 so the upgrade is strongly recommended to avoid unexpected side-effects
- install wireshark on your host system (http://www.wireshark.org).
- Launch the guest in the following way:
# export VBOX_LOG=drv_nat.e.l2 # export VBOX_LOG_DEST=file=nat.log # VBoxManage modifyvm <your-vm-name> --nictrace1 on --nictracefile1 nat.pcap # VirtualBox -startvm <your-vm-name>
- collect pcap files from host (using wireshark ) and guest (please see http://www.virtualbox.org/wiki/Network_tips for details).
- please send me collected data (nat.log, nat.pcap and pcap file from host interface) to me (vasily _dot_ v _dot_ levchenko _at_ Sun _dot_ COM).
comment:6 by , 15 years ago
Resolution: | → worksforme |
---|---|
Status: | reopened → closed |
no response, closing.
Please read the user manual and this Wiki article. In short: That's the nature of NAT, the guest behaves like behind a router. If you need to connect from the outside, either use bridged networking or enable port forwarding (all described in the user manual).