VDSB's Posts

I can finally have the SHD be able to see the vCenter, but it still can't connect to it properly as I get this error message when I try to connect and scan the vCenter: SSL Connection to target failed - Unexpected error while connecting to the target   Any clue on how to fix this?

NickDaGeekUK, dude, it helped a lot.  Now at least is sees the server... still can't connect to it because now I'm getting the error message:  SSL Connection to target failed - Unexpected error while connecting to the target   Thanks again for your help.  I am getting close to getting this thing working (me thinks  )

I think the links are very useful especially the first one. However, I have absolutely no knowledge on anythiing UNIX/Linux/Photon based and I have no idea what commands to run to be able to edit /etc/systemd/network/*.network file.  I can read it by using the cat command but how do I go about editing it.   So sorry guys, newb here  Thank you for your help.

When I do my NSLOOKUP on the server, it does resolve the name properly and yet, on the web interface it never wants to access it, I always get the same error messages as previously posted (see the images on the first post of this thread). My NSLOOKUP looks like this: nslookup 10.132.xx.60 60.xx.132.10.in-addr.arpa      name = vcenter67companyname.company.local When I do it the other way around: nslookup vcenter67companyname.company.local Server: 10.132.yy.33 Address: 10.132.yy.33#53 Name: vcenter67companyname.company.local Address: 10.132.xx.60 Where xx and yy are on different segments and VLANs. But if I don't specify the .company.local it won't resolve it, so I have to have the full FQDN for it to resolve. But in the end, it still doesn't work and SHD still cannot connect to it.