Can't access GUI or ping the server.
Added by Richard Vialoux about 1 year ago
Hey guys, I'm new to nexenta but I saw it being used at work and I just had to install it at home!
I'm pretty tech savvy, working in IT, but setting this up has been very frustrating.
So the machine is an HP ProLiant ML370 G4. I installed nexenta community off the disk to an 18GB SCSI, nothing fancy, I have a ton of drives to put into it, but I haven't been able to successfully set it up.
The system installed just fine and boots properly.
Configuring the system through the GUI is a pain.
The system's onboard gigabit NIC shows up as bge0. DHCP won't seem to find the proper settings and configuring manually doesn't work either. I tried two different working Cat5e cables to eliminate that question.
Not sure what I am doing, I shut the system down and installed a 2-port Intel gigabit PCI-X card.
Now when I boot up and go into "setup appliance init" I see bge0, e1000g0 and e1000g1, looks like the Intel NIC is working.
Now when I try do DHCP, it gets configuration details from my router:
192.168.2.100 and when I try the other port my router gives it 192.168.2.103, both subnet 255.255.255.0.
I leave the port at 2000 and HTTP... even if I try HTTPS I can't get it working.
Going to a web browser and going to http://192.168.2.100:2000/ (or https://192.168.2.100:2000/) does nothing.
The interesting thing is that I was troubleshooting and trying whatever I could, and I GOT IT WORKING! Was able to go through the initial setup procedure, and then upon reboot, again no longer able to access the GUI.
When I am at the box, I ping google.com and it replies: google.com is alive.
If I ping 192.168.2.1 (my router) I was getting an error every time. As I am writing this, when I ping 192.168.2.1 from the nexenta box it says it is alive. Something is working right I guess. When I go from another machine on the network and ping 192.168.2.100, it says request timed out.
DHCP finds my gateway, ip, subnet, and DNS servers properly.
I just tried setting it back to HTTP and went to the address and it doesn't see anything.
How was I able to do the setup? Why did it break it? How can we fix it? I really love the concept of nexenta, and I look forward to getting it working!
Replies
RE: Can't access GUI or ping the server. - Added by Richard Vialoux about 1 year ago
I hope it's not the cause of my problem, but my router is an Edimax Quad-WAN. I don't even use it for the multi-WAN, I used to have point-to-point wireless as my internet connection and finally (after 15 years) got highspeed internet via DSL to our rural home.. There was a 2 month overlap in our services so the router did a great job of utilizing both connections for the time, and I had bought the router a couple of years ago for other purposes. If I can find a generic router I can test it all over again, BUT how would that be the issue if I was able to set it up once already?
RE: Can't access GUI or ping the server. - Added by Richard Vialoux about 1 year ago
Sorry for the double-post, my internet keeps dying and I can't tell if I have submitted my post. When the "internet dies" my "internet" LED on the modem goes off, but I should still be able to access the nexenta box still, technically, everything is connected via a 24-port gigabit linksys switch.
I really wish I had a different router to test with. I feel like I am answering my own question and rambling aimlessly but maybe someone can shed some light.. .
RE: Can't access GUI or ping the server. - Added by Ralph P 10 months ago
Richard - did you get your system operational? If so, what was the resolution. I had a working system that has just stopped responding with the same symptoms.
Thanks.