Cannot access website from LAN

[Allihopp]

Hi everyone.
My organization has a ESXi server with virtual machines, and on one of them there are docker containers, inside one of those containers is a website.
Yesterday everything was working fine, but today, when we moved the server to Cisco (891f router) network, the website is not acessible from LAN, even though from WAN everything works finetw, pinging the domain name responds with local IP, if that's important.
What could cause such a thing?

[paul driver]

Hello
Then the most simplistic solution is to use domainless nat (no inside/outside) if your rtr supports it.

interface GigabitEthernet8
no ip nat outside
ip nat enable

interface Vlan1
no ip nat inside
ip nat enable

no ip nat inside source list 100 interface GigabitEthernet8 overload
no ip nat inside source static tcp 192.168.0.200 3389 X.X.X.X 19500 extendable
no ip nat inside source static tcp 192.168.0.200 80 X.X.X.X 19580 extendable
no ip nat inside source static tcp 192.168.0.200 19596 X.X.X.X 19596 extendable
no ip nat inside source static tcp 192.168.0.191 80 X.X.X.X 80 extendable
no ip nat inside source static tcp 192.168.0.191 45201 X.X.X.X 45201 extendable
no ip nat inside source static tcp 192.168.0.191 45202 X.X.X.X 45202 extendable
no ip nat inside source static tcp 192.168.0.191 45203 X.X.X.X 45203 extendable

ip nat source list 100 interface GigabitEthernet8 overload
ip nat source static tcp 192.168.0.200 3389 X.X.X.X 19500 extendable
ip nat source static tcp 192.168.0.200 80 X.X.X.X 19580 extendable
ip nat source static tcp 192.168.0.200 19596 X.X.X.X 19596 extendable
ip nat source static tcp 192.168.0.191 80 X.X.X.X 80 extendable
ip nat source static tcp 192.168.0.191 45201 X.X.X.X 45201 extendable
ip nat source static tcp 192.168.0.191 45202 X.X.X.X 45202 extendable
ip nat source static tcp 192.168.0.191 45203 X.X.X.X 45203 extendable

[risotab661]

If you are experiencing difficulties accessing a website from a Local Area Network (LAN), there could be several reasons for this issue. Here are some steps you can take to troubleshoot the problem:

Check Network Connectivity:
Ensure that your LAN has a stable internet connection. Test the connectivity by accessing other websites or using online tools like ping or traceroute to check for any network issues.

Firewall Settings:
Check the firewall settings on your network. Sometimes, firewalls may block access to certain websites. Make sure that the firewall is not blocking the specific website you are trying to access.

DNS Configuration:
Verify the Domain Name System (DNS) settings on your network. Incorrect DNS configurations can prevent access to websites. You can try using alternative DNS servers (such as Google's public DNS or OpenDNS) to see if it resolves the issue.

Proxy Settings:
If your LAN uses a proxy server, ensure that the proxy settings are configured correctly. Incorrect proxy configurations can lead to issues accessing websites.

Web Filtering and Content Filtering:
Check if there are any web filtering or content filtering systems in place on your network. These systems may block access to certain websites based on content categories.

Browser Issues:
Try accessing the website using a different web browser to rule out any browser-specific issues. Clearing the browser cache and cookies might also help.

Hosts File:
Check the hosts file on the local machine to ensure that there are no entries redirecting the website to a different IP address.

Router Configuration:
Examine the router settings to ensure that there are no restrictions or filters in place that could be preventing access to the website.

Website Status:
Confirm that the website itself is accessible from other locations. It's possible that the issue is with the website rather than your LAN.

Contact IT Support:
If you are unable to resolve the issue, it's advisable to contact your IT support or network administrator for further assistance. They can analyze the network configuration and address any issues specific to your LAN setup.