General discussion

  • Creator
    Topic
  • #2140385

    LAN / Apache troubleshoot -newbie

    by sk124 ·

    Tags: 

    Hi, this is my scenario (everything is within my LAN):

    BEFORE

    I have my MariaDB in machine 192.168.1.209; I access the MariaDB using windows client DBeaver and works fine.

    I had a working ubuntu machine 192.168.1.209 and my Perl scripts could be executed in my local windows browser (192.168.1.xxx) as http://192.168.1.209/p/index.pl

    I also have windows pc clone of p folder in c:/inetpub/wwwroot/p and works fine in browser http://127.0.0.1/p/index,pl (my local ip connects to MariaDB in 192.168.1.209)

    CHANGE DONE

    I did a LAN-to-WAN to hide all my private info (pc, servers etc) from IoT.

    One of the Router 1 (192.168.1.1) LAN is connected to Router’s 2 WAN (192.168.2.1). All my IOT’s are connected to Router 1 and private PC’s, servers etc is connected to Router 2.

    AFTER

    Now the IP of the MariaDB & Apache Server machine has changed from 192.168.1.209 TO 192.168.2.109. It is still within my LAN.

    I pointed my DBeaver to new IP and my mariadb connects fine.

    My local ip http://127.0.0.1/p/index,pl (mariadb pointing to new ip 192.168.2.109) works fine.

    However http://192.168.2.109/p/index.pl
    does not work and I get a message as follows in the browser:

    This site can’t be reached
    192.168.2.109 took too long to respond.
    Try:

    Checking the connection
    Checking the proxy and the firewall
    Running Windows Network Diagnostics
    ERR_CONNECTION_TIMED_OUT

    Please note that perl is working fine in 192.168.2.109 (no issues)

    From a newbie perspective this something to do with networking or apache2 or both. Not sure, can experts point me how I go about troubleshooting.

    Thanks much
    sk

You are posting a reply to: LAN / Apache troubleshoot -newbie

The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our Community FAQs for details. All submitted content is subject to our Terms of Use.

All Comments

Viewing 0 reply threads