I'm a new VBox user, and I must say I like it, but I'm having some issues with the networking. It seems really inconsistent. What works one boot fails to work the next boot with no changes.
I currently have a Debian Etch RC1 system set up using bridged networking. I created the adapter, bridged it with my NIC and load it up. One time it will be fine (the virtual nic won't show connected, but I have an IP and everything works great). The next boot, nothing is different, yet I have a 169.x address. Running dhclient won't give me an IP. I've also seen it generate a 169 while the virtual NIC is actually showing connected on the host machine. I'm not sure if this is a host machine issue (Windows Media Center) or an issue with the virtual NIC, the guest OS, or what. I'm not even sure how to go about troubleshooting it at this point. Just now, the virtual NIC was showing connected, but the guest machine couldn't get a proper IP. I shut it down until the NIC disconnected then started, and now its fine again. Otherwise this program is great, but this inconsistency is a bit of a killer. Any help in sorting it out would be appreciated. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
