×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello Pete,
Am 07.01.2022 um 00:04 schrieb Pete Helgren <pete@xxxxxxxxxx>:
*I* am the "network guys" you refer to.
No offense intended! Most people who write here work in, or with, big to very big companies. Rule of thumb is that responsibilities are rarely united in one person in these. And that network topologies can be very complex. So please excuse my crystal ball failing to put you into the right category. ;-)
I didn't realize that the HMC was delivering the web interface on port 2300.
I also stumbled upon this by chance. :-)
Also, this is a straight up, VMWare workstation installed on Windows 10. Based on what I see in the network settings for the VMWare Guest (vHMC) it's on a 192.168.47.1/24 network. The attributes of the vHMC network connection show that the IP is 192.168.47.129. It has a default gateway of 192.168.47.2
I'm not too used about VMware workstation. I'm working with ESXi, usually. Again, no offense intended, but VMware workstation is a low end "toy", intended towards SoHo environments, and end users. It partly provides functionality not being seen in ESXi, and vice versa. NAT to have closed down, "internal" and entirely virtual networks is one such feature.
The Network Connection setting show it's on a Custom: Specific virtual network (VMnet8 (NAT)) Frankly, I can't remember why some of these options were chosen or whether I should change them.
I remember that VMware workstation can create virtual networks, seeding IP configuration with a built-in DHCP server. Somehow this "magic" provides a default gateway, and NAT to your "real" network (connected to the host running VMware WS).
This means: You can access your network *from* anything within that 192.168.47.0/24 range, but not vice versa, because it's NATed. And since that network is entirely contained within the VMware workstation environment, you can't go anywhere. I don't know if you can define port forwards, but I strongly advise against this route. Just avoid NAT where possible, and make use of it where it's beneficial.
The easiest way is to move on: Disconnect the HMC association from the POWER machine. Get rid of that NATed network — including the 192.168.47.0 network, and use bridging to connect your physical 192.168.1.0/24 LAN directly to the VM. Reconfigure HMC as needed, and reconnect to the POWER box. With that you have access from everywhere to everywhere. Issue solved.
:wq! PoC
midrange.com
