Opened 14 years ago
Last modified 13 years ago
#6959 closed defect
NAT regression from 3.1.8 — at Version 1
Reported by: | cprofitt | Owned by: | |
---|---|---|---|
Component: | network/NAT | Version: | VirtualBox 3.2.4 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description (last modified by )
After upgrading from 3.1.8 to 3.2.0 or 3.2.4 I encounter a regression in NAT. Details below:
Running 3.2.4: Computer is using NAT for networking
- I can authenticate to Active Directory if I do so immediately. If I allow the machine to sit at the login prompt for more than 60 seconds I get a message 'internal error'
- If I use the Microsoft DNS Management tool I can not access the DNS server and manage it
- If I launch Microsoft DHCP Management tool I can not access the DHCP server
Running 3.2.4: Computer is using Bridged for networking
- I can authenticate to Active Directory
- If I use the Microsoft DNS Management tool I can access the DNS server and manage it
- If I launch Microsoft DHCP Management tool I can access the DHCP server
Running 3.1.8 Computer is using NAT for networking
- I can authenticate to Active Directory
- If I use the Microsoft DNS Management tool I can access the DNS server and manage it
- If I launch Microsoft DHCP Management tool I can access the DHCP server
Note:
See TracTickets
for help on using tickets.
VBox.log file with NAT issues