You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can run container fine and install & run chrome normally. But when I try to navigate to our LAN server (located in 192.168.0.1) connection is rejected. A NMAP scan from inside the the container shows dns is correctly result but that ip redirects to local instead of remote machine:
# nmap 192.168.0.1
Starting Nmap 7.40 ( https://nmap.org ) at 2018-08-27 09:19 UTC
Nmap scan report for xxxxxxxxxx.xxxxxxxxx.local (192.168.0.1)
Host is up (0.000036s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
111/tcp open rpcbind
5800/tcp open vnc-http
5900/tcp open vnc
Which service is taking the 192.168.0.1 ip? Ifconfig doesn't show any device
Sorry for leaving this post here. The problem is related to my docker installation that is doing some weird stuff with my vpn, lan & other. Running container in our servers network worked fine.
Thanks for your help and this useful image
I can run container fine and install & run chrome normally. But when I try to navigate to our LAN server (located in 192.168.0.1) connection is rejected. A NMAP scan from inside the the container shows dns is correctly result but that ip redirects to local instead of remote machine:
Which service is taking the 192.168.0.1 ip? Ifconfig doesn't show any device
The text was updated successfully, but these errors were encountered: