Ben Barker, on Monday, February 10, 2020 03:57 PM, wrote... > > Cheers - yes I checked that. I think perhaps it is some oddity of the > host machine. On a different host (same subnet, same settings, but > different NIC hardware) it seems to work as expected
Can you ping the name and the IP address from both places? Does nslookup for both machine and full DNS address return the same IP address? > But I have tried a few virtual adapters on this machine and when in > bridged mode all tell me "cannot resolve hosts hardware address" > > I have tried using Trumped and mTCP - so perhaps the issue is with the > packet driver / virtual adapter... > > On Mon, Feb 10, 2020 at 7:37 PM Louis Santillan <lpsan...@gmail.com> > wrote: > > Are your `IPADDR`, `NETMASK` & `GATEWAY` vars that which match the > subnet of the Ubuntu machine? `IPADDR` & the `ethernet address` > should be unique from your Ubuntu machine's setting. > > To compare, in Ubuntu, type `ip a` or `ifconfig`. > > On Mon, Feb 10, 2020 at 5:18 AM Alain Mouette <ala...@pobox.com> wrote: > > > > Use netbootdisk.com to setup your NIC > > > > > > Em 10/02/2020 09:02, Ben Barker escreveu: > > > > Morning > > I have a freedos install running on virtualBox, with the host machine > being Ubuntu > > > > If I run the networking in NAT mode, all is fine > > > > If I try "bridged mode", then at startup fDos sees the network adapter, > and reports: > > > > Interrupt number 0x9 (9) > > I/O port -xD020 (53280) > > My ethernet address is xxxxxxxx > > > > but any attempt to see the outside network gives the error: > > > > "cannot resolve host's hardware address" > > > > My mtcp.cfg is: > > > > PACKETINT 0x09 (tried a few values here...) > > IPADDR xxxxx > > NETMASK xxxxx > > GATEWAY xxxxx > > NAMESERVER xxxxx > > > > Any ideas...? > >
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
