Quantcast
Channel: WampServer - WampServer English
Viewing all articles
Browse latest Browse all 3177

Dazed and Confused... (no replies)

$
0
0
Gracious Moderators,

I am out of ideas and I humbly request for some guidance and suggestions. I have recently installed the 64bit version of WAMP 3.2. on the VM workstation Pro 12. The host and client specs are as follows:

VM # 1 - The host:
1) Windows 7sp1 Utlimate x64
2) Bridged NAT at 192.168.1.105
3) Installed all VC_Redist and confirmed by your little app.
4) Disabled Firewall
5) IIS disabled via crtl panel/uninstall app/…
6) I get a beautiful green icon at the task bar.
7) Setup database ‘demosite’ language ‘Collation.’
8) Setup/install Wordpress account
9) Setup a generic test blog site.
10) Setup virtualhost (This is where stuff starts to get interesting….)
a. demotest.test
b. C:\wamp64\www\wordpress\
11) Edit vhost.conf to ‘Require all granted’ under demotest.test entry

VM # 2 The client:
1) Debian 10 buster
2) Bridge NAT at 192.168.1.108
3) Launched terminal ‘ping 192.168.1.105’….responds well.
4) ‘Ping demotest.test’ …nothing.

I must be missing something really simple. Break out the Google-foo…search and search… Combing through this forum….maybe corrupt hosts file? Okay, recreate host file…. Maybe browser block? Okay, reset VM# 1 repeat install but use different browser. Still no access. So for giggles, I edit the vhost.conf and change ‘Require local’ under ‘localhost’ entry to ‘…grant all.’ Restart DNS…back to VM # 2, but enter the ip in the browser instead and I can now pull up the WAMPSERVER homepage! WTH! Awesome I think, I must be on to something….but still not sure what. While on the homepage (still on VM #2) I double-click on the ‘demotest.test’ link….nothing…. what am I missing here? I almost forgot to mention that my intent is to use VM #2 to access publications from VM # 1.. Thanks for your time and attention.

Viewing all articles
Browse latest Browse all 3177

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>