On 10/29/20 7:02 AM, D'Arcy Cain wrote:
Turns out it has nothing to do with virtualization. It never occurred to me to test that the host could access the Internet since I had no problem connecting and logging in. However, everything I described for the VM applies to the host as well. Here is my current setup.
OMG!!!I can't believe how simple the fix was. Kind of embarrassing except that the error was not mine.
To recap, my system has two networks, a public facing one and a private back channel. I put the public address on the public side and the private address on the back one. Simple. It is unless the person installing the hardware switches the ethernet cables. The surprising thing is not that it failed but that it worked at all.
The one system that this server could connect to was also a VM system albeit set up differently. It must have somehow routed the public address to the back channel into what the host thought was the public side.
The world makes sense again. -- D'Arcy J.M. Cain <da...@druid.net> | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 788 2246 (DoD#0082) (eNTP) | what's for dinner. IM: da...@vybenetworks.com, VoIP: sip:da...@druid.net Disclaimer: By sending an email to ANY of my addresses you are agreeing that: 1. I am by definition, "the intended recipient". 2. All information in the email is mine to do with as I see fit and make such financial profit, political mileage, or good joke as it lends itself to. In particular, I may quote it where I please. 3. I may take the contents as representing the views of your company if I so wish. 4. This overrides any disclaimer or statement of confidentiality that may be included or implied in your message.
OpenPGP_signature
Description: OpenPGP digital signature
