Starting with AMT version 6, AMT has IPv6 support. There are some differences between IPv4 & IPv6. First, IPv6 is disabled by default. The quickest way to check for this, and enable IPv6 on 1 system is to use the WebUI.
The second difference is that AMT does *not* share IPv6 addresses with the host OS. So, you'll need to be sure you're connecting to on of AMT's IPv6 address, and not the host's. The webUI will also show you AMT's IPv6 addresses.
Check those the above, and try again. If you're still having trouble, let me know if you are using TLS, if you're connecting by FQDN vs IP address, if you're using digest or Kerberos to authenticate, and what version of SCS you are using.
Thanks Jake, that explains a lot of the issues we have been having. I'll share the solution I came up with if you or anyone else is interested.
I wrote a dos batch file that prompts the user for the FQDN. They punch that in and then behind the scenes the batch file does a ping hostname -4, so I can get the IPv4 address. Then I add that entry into the hosts file, then launches VNC viewer from the commandline with the hostname. At that point VNC is forced to use the IPv4 address and everything communicates correctly. Then when the VNC session is over, it restores their host file back.
Not the prettiest solution, but it does work so I'm happy!
Thanks again for the information - it was very helpful :-)
Here's the code:
set /P INPUT=Full Hostname (ie. host.domain.com): %=%
set _ping_cmd=ping -n 1 %INPUT% -4
FOR /f "tokens=2 delims==" %%G IN ('%_ping_cmd% ^|find "]"') DO (
REM echo Result is %%G
copy c:\Windows\System32\drivers\etc\hosts c:\Windows\System32\drivers\etc\hosts.bak
echo %%G %INPUT%>>c:\Windows\System32\drivers\etc\hosts
"c:\program files\realvnc\vncviewerplus\vncviewerplus.exe" %INPUT%
copy c:\Windows\System32\drivers\etc\hosts.bak c:\Windows\System32\drivers\etc\hosts