SOLVED: Installation Woes

[mres335]

Hello,

Yes, I have disabled DHCP on the router, but am not sure how to disable DNS?
Manual: http://setuprouter.com/router/telus/vsg ... l-1256.pdf

I now have a valid nslookup and am getting an IP form the HDA.

I can now ping the 'hda', the router, 8.8.8.8 and yahoo.com...but no access to http://hda/

I am using ESET NOD32...not sure what that is doing. I have disabled the protection, and no success.

By-the way, what is my home server's domain name..to apply the Vista Networking Issue fix?

Note: When I add "home.com" to the DNS, I then get the 141.8.224.183 address - so maybe not the correct DNS entry.

Thank you!

[bigfoot65]

I can now ping the 'hda', the router, 8.8.8.8 and yahoo.com...but no access to http://hda/

Can you access by IP address?

I am using ESET NOD32.

Is this antivirus software?

By-the way, what is my home server's domain name..to apply the Vista Networking Issue fix?

You set the home domain when you created the HDA profile on amahi.org. It defaults to amahi.net unless you changed it.

By-the way, what is my home server's domain name..to apply the Vista Networking Issue fix?

If you are using a Windows client, check that it's getting the DHCP lease and DNS from the HDA. To do so, from Windows Client command line do:

Code: Select all

ipconfig /all

If the IP address and/or DNS is not from the HDA, then that's your issue. Probably something related to your router settings.

Also, check that the web server is running on the HDA. From command line, do:

Code: Select all

sudo systemctl status httpd

If it's not running, try to start it:

Code: Select all

sudo systemctl start httpd

If there are errors, then recommend you do an OS update:

Code: Select all

sudo dnf update

Reboot and then check things again.

I have given you a few different things to try. One of them should solve your problem. Please let us know how it goes.

[mres335]

Hello,

When I checked the Web server status, I received the following message:
Active: Failed
Process: (code-exited, status-1/FAILURE)
Feb 16 14:24:00 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server.

I then attempted to start the Web server - knowing that it would more than likely fail, and it did!
Status: Job for httpd.service failed because the process exited with an error code. See "systemctl status httpd.service" and "journalctl - xe" for details.

I then performed the OS update as you suggested - AND ALL IS NOW WORKING!!

Note: I would really like to know how and why the Apache HTTP Server failed however. Any ideas?

By-the-way...thank you so very, very much for your assistance. It is very much appreciated.

[bigfoot65]

I then performed the OS update as you suggested - AND ALL IS NOW WORKING!!

Great news.

Note: I would really like to know how and why the Apache HTTP Server failed however. Any ideas?

I believe it's due to newer packages being installed vs the versions on the CD/DVD. The only way to fix it is to do an OS update.

By-the-way...thank you so very, very much for your assistance. It is very much appreciated.

No problem. Happy to assist.

Will mark this as resolved.

[mres335]

Hello,

Yes, please do!

And may all perform the same update.

Thank you so very much again!