Network NOT OK

[GoodMediaOL]

I specifically paid for the HyperV VM, I downloaded it, decompressed it, etc, and mounted the VM using WIN2012 Data Server on a current machine.

It loads up and when it goes through the startup script, it fails on the Network piece;

120.384199 elk_update_request: I/O error, dev fd0, sector 0
couldn't read interfaces file.

I have attached a screen shot

Any ideas to get this working ? All your help files refer to VMWare...

Thanks,

Scott Goodfellow
416 645 0355
goodmedia@goodmedia.com

[enoch85]

Hi @GoodMediaOL Thanks for your report!

How is your network setup? The script fetches the IP from DHCP.

Can you access the interfaces file and post if here? Also, it would be nice if you posted the output for "ifconfig"

[GoodMediaOL]

Ok, I have managed to get this far;


Is that helpful ? Not sure how to move forward...
Thanks!

[enoch85]

Thanks, almost there ;) Post the output of cat /etc/network/interfaces

Also, is this run behind a firewall? 90% of these "bugs" are because the user have failed to setup the network that this VM runs on, or are behind a firewall.

[GoodMediaOL]

Here it is

Yes there is a firewall of course, and the internal IP number NC is picking up does not correspond to an external IP. So the VM can (or should be able to) connect outbound on all ports, but can not be contacted inbound until I can assign it a different IP.

Thanks.

[enoch85]

Ok, so the config files are correct and your IP is 192.168.168.52. Did you enable NAT or is the VM in bridged mode?

This is a firewall setup error or a VM network setup error. Nothing to do with the scripts afaik.

[enoch85]

ping @GoodMediaOL

[enoch85]

I'll close this, please reopen if it's still an issue.

[GoodMediaOL]

I managed to get this working yesterday, by using my laptop / WIN10. The issue is (was) the firewall in the production environment where I was trying to work. If there was a way to assign a fixed IP in the intital setup script, that would have "fixed" this / saved a lot of time. Thanks for your help !

[enoch85]

Like I suspected. ;)

This is a firewall setup error or a VM network setup error. Nothing to do with the scripts

Thanks for reporting this anyway.