Troubleshooting – External Sametime app and Java issue

Mac OS Mojave 10.14.5
IBM Notes 10.0.1 in Basic Mode (recent upgrade from 9.0.1. standard)
Java version JRE 8 version 191
Sametime App – external to IBM Notes client

Trying to resolve requisite Java for Sametime app to install and function

Troubleshooting steps
-Note: I’m not going to proceed further with this, as I got IBM Notes 10.0.1. FP2 to work in Standard mode and embedded Sametime works.
-I think the key with the legacy external Sametime Application for Mac is to ensure you have the Legacy Java 6 installed — that would have originally come from Apple. This was before Apple handed off Java to Oracle (or was it Sun beforehand?). Either way, Apple now points you to Oracle for Java.
-As of 20190803, IBM/HCL is strategically bundling Java JRE/Eclipse installers within their IBM Notes 10.0.1. installers (suggest also installing FP2). I believe this is a core fix. I also read a rumor that Oracle was planning on charging for Java JRE.

Troubleshooting – Mac OS Mojave, URL link opening application

Mac OS Mojave 10.14.5.
IBM Notes 10.0.1 for Mac 64-bit
Preferences, Locations, Web Browser, Safari,
Click on URL in email — opens a seemingly random application (not Safari)

Lessons Learned

-After a recent Apple OS Update (to 10.14.5), there was a conflict between Apple OS, Java/Eclipse, and IBM Notes 9.0.1. — NSD crashes.
-In order to create an interim stable environment, the trick was to add UseBasicNotes=1 within the Notes Preferences file. This is called being in Notes Basic Mode. This also tells me that there was an underlying conflict with Java JRE — we have 8 version 191.
-Issue with being in Basic Mode was that when I clicked on a URL in IBM Notes, instead of opening the configured, it was opening some other third party application – PersonalBrain. Not sure why this was happening, but the temporary answer was to uninstall PersonalBrain. Then, the URL links worked again.
-In order to get IBM Notes 9.0.1. for Mac to properly function, as of 20190803, the suggestion is to ensure you have IF17 (Interim Fix) installed
-In order to get IBM Notes 10.0.1. for Mac to properly function (which is what we currently had upgraded to), as of 20190803, the suggestion is to ensure you have FP2 (Fixpack 2) installed. Note: IBM Notes 10.0.1. with FP2 now includes the Java JRE, so you don’t need to have it pre-installed – I believe this is a crucial fix by IBM.
-After FP2 was installed, and the UseBasicNotes-1 was removed, PersonalBrain was installed
-Now everything works

Firewall and DNS configurations (Domino Server) within ESXi VM

FQDN of IP address – DA-OJAI-VM (Windows Server 2016 Test – Domino 10)
-A Record and PTR Record must point to the correct IP address for the server
-nslookup is useful to confirm that the A and PTR records are configured correctly in your DNS is an old friend for various interrogations of IP addresses, etc
-Now that’s fixed, and the inbound rule for ICMP was set to Profile Public, I can now ping to the FQDN and it resolves correctly to the server’s IP address

Network settings within Server 2016
-Originally configured to Private, and changed to Public
-I think that was the primary reason I was unable to get the Domino Server online

IBM Domino Port 2050 for Console
This document explains how Domino Server Controller can fail to startup without Pot 2050 configured correctly.

-Originally, problem was that Domino Console would give an error about port 2050, which would affect both accessing console and also getting Domino running
-Now that Network security is Public (vs Private), added a rule to allow inbound TCP for port 2050
-Now, when I do netstat -a from Server terminal, I get: TCP listening for Port 1352 and my server’s external IP address listening for port 2050
-During troubleshooting, I had opened up the Public Profile firewall too much, so turning off Inbound connections “allow” – so I’m required to have specific rules. Before changing firewall, shutdown Domino. Changed public firewall to block (default) incoming. Confirmed rule for 1352 (added the internal address) and rule for 2050. Started IBM Domino Service; went into Domino Console and added password; netstat -a looks good for 1352 and 2050.

IBM Domino Port 1352

IBM Domino Console and embedded password – somewhat related to security…
-Would be nice to not have to manually enter this each time.

Allowing Ping from outside to the server
-To enable inbound rule of allowing ICMP packets, select ‘Inbound Rules’. Find out and right click on ‘File and Printer Sharing (Echo Request –ICMPv4-In’), select Enable Rule. That will allow incoming ping requests in Windows 2012 R2/2016 server and respond to them without completely disabling firewall service.
-I think what I was overlooking was that under “Advanced” the Profile was set to Private, and I needed to add Public
-That freakin’ immediately resolved doing a ping from the outside to the server
-I can also ping externally to the FQDN, which resolves correctly to server IP Address

SSH connections to VMware ESXi Host

Desired Outcome:
While the VMware Web Client, when I purchase a basic license of VMware (including vCenter) is really good, I’ve heard, I need a means of accessing the VMware host using SSH.

Action Support:

-MacOS has a built in SSH functionality for accessing remote hosts

-Enabled SSH within the ESXi host
-Used the Mac’s built in terminal for SSH vs some downloaded application

/etc/init.d/usbarbitrator status (returns usbarbitrator is running)
esxcli hardware usb passthrough device list (returns a timeout)

Note: Maybe the USB passthrough is not quite enabled

vmware -v (Returns VMware ESXi 6.7.0 build-10302608)
lsusb (Returns nothing)

Note: When not using SSH, my best practice is to back into the host and disable it.

Edit Settings in VMware not loading (resolved)


On Vmware ESXi 6.7, I think I had opened up SSH and was playing with various things like VMRC (downloading mac app, etc).

End result was that there were a slew of attempted log-ins, and also Edit Settings on the VM was not loading.


-Disable SSH, which stopped the log-ins
-Shutdown all VM’s
-Put the host into Maintenance mode – this is best practice
-Restarted the ESXi host
-Took host out of maintenance mode — If you forget, then the VM’s don’t load completely, especially the networks
-Edit settings are now OK