If I'm not sure whether I can connect to a host at a low level, I start with a ping command, then if that succeeds, move to higher-level protocols. I think the error message is indicative in this case, but where it isn't, I find the above procedure useful.
On 4/20/18, 04:40, "Blind-sysadmins on behalf of Andrew Hodgson" wrote:
Hi,
If you get a 404 it tells me that a web server is listening there and the NATting may be working. I would look at your Apache logs to see if the request is hitting the server you believe it should be hitting, and if so then what the issue is on that server in Apache itself which is stopping the default document from coming up.
Andrew.
________________________________________
From: Blind-sysadmins [blind-sysadmins-bounces@lists.hodgsonfamily.org] on behalf of David Mehler [dave.mehler@gmail.com]
Sent: 20 April 2018 04:54
To: blind-sysadmins
Subject: [Blind-sysadmins] accessing a natted vm
Hello,
I've got VMware workstation I think it's 12 or 13 running on win10
x64. I've got several Linux guests all natted. I'd like to access
running services on those guests. When I go to for example
192.168.237.133 attempting to pull up the default apache page I get a
404 site not found. I checked on the guest the apache is running and
there is no firewall active on the guest.
Any suggestions welcome.
Thanks.
Dave.
_______________________________________________
Blind-sysadmins mailing list
Blind-sysadmins@lists.hodgsonfamily.org
https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________
Blind-sysadmins mailing list
Blind-sysadmins@lists.hodgsonfamily.org
https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
