Questions[asus](server)

I've got two identical intel CPUs in an Asus board with one stick of ram each. On power up, board immediately throws code 19 ("SB initialize before installed memory"). I've tested each CPU individually, as well as each stick of ram. When using a single cpu, the system boots fine with either one or two sticks of ram installed. The only time I have issues is when I install the second CPU. Am I missing something critical to dual-CPU builds that isn't done in single-CPU builds?

MB: ASUS Z10PE-D16

CPU: 2x Intel E5-1620V4 3.5Ghz, socket LGA2011V4, 140w

RAM: 2x Supermicro (sticker says Samsung) M393A4K40CB1-CRC4Q 32GB ECC DDR4 2400

PSU: FSP Twins Pro 700W

I'm trying update firmware that there is 1.08 to more recent, I look in site official but not gotch result, all versions are defined with "unsuccessful" in verifying the firmware image anyone can help me?

I tryed https://www.asus.com/Commercial-Servers-Workstations/Z10PAD8/HelpDesk_BIOS/ https://drivers.eu/Server%20Products/ASUS/ASMB8-iKVM

Using https://github.com/angristan/openvpn-install i have installed openvpn on AWS Lightsail Instance (Ubuntu 18.04 LTS). My server config file is as follows:

    port 33434
    proto udp
    dev tun
    user nobody
    group nogroup
    persist-key
    persist-tun
    keepalive 10 120
    topology subnet
    server 10.8.0.0 255.255.255.0
    ifconfig-pool-persist ipp.txt
    push "dhcp-option DNS 8.8.8.8"
    push "dhcp-option DNS 8.8.4.4"
    push "redirect-gateway def1 bypass-dhcp"
    dh dh.pem
    tls-auth tls-auth.key 0
    crl-verify crl.pem
    ca ca.crt
    cert server_VYtknmf1PC80WpTG.crt
    key server_VYtknmf1PC80WpTG.key
    auth SHA512
    cipher AES-256-CBC
    ncp-ciphers AES-256-CBC
    tls-server
    client-config-dir /etc/openvpn/ccd
    status /var/log/openvpn/status.log
    verb 3

And my client.ovpn is as follows:

client
proto udp
explicit-exit-notify
remote 35.173.69.115 33434
dev tun
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
verify-x509-name server_VYtknmf1PC80WpTG name
auth SHA512
auth-nocache
cipher AES-256-CBC
tls-client
setenv opt block-outside-dns # Prevent Windows 10 DNS leak
verb 3

I have added port '33434' UDP in Firewall rule of AWS instance.

I added a new profile in VPN Client section of the asus router and uploaded the client.ovpn file. And clicked activate and get follow message in the log.

May 15 22:29:43 vpnclient1[17419]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
May 15 22:29:43 vpnclient1[17419]: Socket Buffers: R=[122880->122880] S=[122880->122880]
May 15 22:29:43 vpnclient1[17419]: UDPv4 link local: [undef]
May 15 22:29:43 vpnclient1[17419]: UDPv4 link remote: [AF_INET]35.173.69.115:33434
May 15 22:29:43 vpnclient1[17419]: TLS: Initial packet from [AF_INET]35.173.69.115:33434, sid=61d9df2d 1f97bdd0
May 15 22:30:02 rc_service: service 17718:notify_rc restart_letsencrypt
May 15 22:30:43 vpnclient1[17419]: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
May 15 22:30:43 vpnclient1[17419]: TLS Error: TLS handshake failed
May 15 22:30:43 vpnclient1[17419]: SIGUSR1[soft,tls-error] received, process restarting
May 15 22:30:43 vpnclient1[17419]: Restart pause, 2 second(s)

Please suggest how to fix the issue. Thank you.

Guest Network prevents access to internal network. That's perfect.

However I have a server machine that is accessible externally. I have set up port forwarding to allow this. I can access the LAN IP within my network and the External IP: through LTE on my phone or at work. That's perfect.

Guest Network cannot access server through LAN IP. That's what I want.

Guest Network cannot access server through External IP:. This is my issue, I want access.

Is External IP: being resolved to LAN IP so Guest Network blocks it? Is there anyway I can allow access to the server on Guest Network by going to the out to the Internet and coming back in?

I upgraded my ASUS KFN32-D SLI/SAS motherboard to the latest BIOS version and swapped out the 2 dual-core procs with 2 quad core procs. After installing Server 2008 Datacenter onto the system I noticed that it was not connected to the network. I open device manager and see no network adapters. I have to go up to View -> Show hidden devices to even see the virtual WAN Miniport adapters.

This problem happens in Vista and Windows 7 (all x64). What is even stranger is it all works in x86 mode. What in x64 could be causing windows to not even detect hardware that works in x86? Is the boot manager possibly the culprit?