Thank you for your suggestions,
In the end (with the advice from someone on the VB forum) I just
reinstalled VB with the onboard NIC already disabled - that seemed to
work!
Thought I like the more elegant way gharris suggested!
Many thanks
Nic
Well I went ahead and installed VB.
My issue now is that VB insists on using eth0 for the network
connection. My server has an add in NIC that is gigabit on eth1, the on
board eth0 is only 10/100. Even disabling the onboard NIC in the bios
doesn't fix the problem VB still tries to use eth0! How
DrNic wrote:
Well I went ahead and installed VB.
My issue now is that VB insists on using eth0 for the network
connection. My server has an add in NIC that is gigabit on eth1, the on
board eth0 is only 10/100. Even disabling the onboard NIC in the bios
doesn't fix the problem VB still tries
garym wrote:
i'm sure one of the vb gurus at the vortexbox forum can answer this
one.
http://vortexbox.org/forum/
Maybe it's something I'm doing, but I can't register for that forum. It
asks you to answer a Random Question during signup, and I don't seem
able to answer them.
Misquoted
DrNic wrote:
Well I went ahead and installed VB.
My issue now is that VB insists on using eth0 for the network
connection. My server has an add in NIC that is gigabit on eth1, the on
board eth0 is only 10/100. Even disabling the onboard NIC in the bios
doesn't fix the problem VB still tries
