Welcome, Guest. Please login or register.
Did you miss your activation email?
Saturday 28 December 2024, 03:20:52 pm

Login with username, password and session length

Visit the Official Endian Bug tracker  HERE
14262 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  Installation Support
| | |-+  Unable to connect to Endian's web interface after install
0 Members and 0 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Unable to connect to Endian's web interface after install  (Read 21943 times)
MAllam
Full Member
***
Offline Offline

Posts: 15


« on: Tuesday 17 November 2009, 03:54:11 am »

Hi,

Ive just tried installing Endian on VMWare Server, the install goes ahead perfectly and I set the green IP to 10.10.254.1 but nothing else from here works, I cannot ping the IP and I cannot access the web interface for it either. I then tried doing a reinstall in VirtualBox and get the same problem, any ideas?

Im installing the new 2.3 ISO

My machine is a Dell PowerEdge 2950 1u
NIC #1 = Connected to network, IP of 10.10.254.3
NIC #2 = Connected to DSL, IP of 192.168.1.254

Ive tried swapping the two nics around, ive tried using NAT and Bridged mode within VirtualBox and none will allow me to ping or access the web interface, am I missing something obvious?

Please help
Mike
Logged
MAllam
Full Member
***
Offline Offline

Posts: 15


« Reply #1 on: Wednesday 18 November 2009, 03:04:30 am »

No one? can anyone give me a quick setting guide for changes I need to make to get endian to run in Virtualbox? please, urgent!
Logged
MAllam
Full Member
***
Offline Offline

Posts: 15


« Reply #2 on: Thursday 26 November 2009, 01:07:21 am »

No one? hmm ...
Logged
mrkroket
Hero Member
*****
Offline Offline

Posts: 495


« Reply #3 on: Thursday 26 November 2009, 02:06:15 am »

It seems a config problem on VMWare Server, not on Endian.

I've setup EFW 2.3 on both VMWare Server 1 and 2 and it has no problems.

On VMware check you virtual networks. If you have more than 1 NIC, you shouldn't use automatically bridged, it gives you a random NIC.
On VMWare Server, go to Host->Virtual Network Settings->Host Virtual Network Mapping
Define VMNet2 as your first NIC, and VMNet3 as your 2nd.

Now, on your virtual machine assign VMNet2 to your first virtual NIC, and VMNet3 to your second. Check that they are connected (powered on), sometimes it appears disabled.
Double check that your GREEN IP falls on the same subnet that your first NIC.
Start pinging. If doesnt reply try to swap VMNet2 & VMNet3 on your virtual machine.
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.078 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com