The ultimate solution to this issue was to add in the fully qualified server name to the Hosts file in C:\Windows\System32\drivers\etc. This allowed the workstation to pickup the TDoD Application Server name and communicate with it.
To diagnose it was a Hosts file entry that was needed, pinging from the Client's workstation to the TDoD Server host iwith a none fully qualified name worked. It failed when using a fully qualified name. This lead to following:
Steps to Diagnose:
First, ping the fully qualified host name forcing IPv6 communication)
Per the help file below, -6 was used to force IPv6 communication.
C:\>ping
Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
[-r count] [-s count] [[-j host-list] | [-k host-list]]
[-w timeout] [-R] [-S srcaddr] [-4] [-6] target_name
Options:
-t Ping the specified host until stopped.
To see statistics and continue - type Control-Break;
To stop - type Control-C.
-a Resolve addresses to hostnames.
-n count Number of echo requests to send.
-l size Send buffer size.
-f Set Don't Fragment flag in packet (IPv4-only).
-i TTL Time To Live.
-v TOS Type Of Service (IPv4-only. This setting has been deprecated
and has no effect on the type of service field in the IP Header).
-r count Record route for count hops (IPv4-only).
-s count Timestamp for count hops (IPv4-only).
-j host-list Loose source route along host-list (IPv4-only).
-k host-list Strict source route along host-list (IPv4-only).
-w timeout Timeout in milliseconds to wait for each reply.
-R Use routing header to test reverse route also (IPv6-only).
-S srcaddr Source address to use.
-4 Force using IPv4.
-6 Force using IPv6.
ping -6 fully.qualified.hostname
Ping request could not find host fully.qualified.hostname. Please check the name and try again.
Next, ping just the hostname forcing IPv6 communication
ping -6 hostname
Pinging fully.qualified.hostname [####:ab#:#####:ab#:####] with 32 bytes of data:
reply from ####:ab#:#####:ab#:#### : time=20ms
reply from ####:ab#:#####:ab#:#### : time=27ms
reply from ####:ab#:#####:ab#:#### : time=27ms
reply from ####:ab#:#####:ab#:#### : time=27ms
Next, add to the Hosts file located in this folder
C:\Windows\System32\drivers\etc
The entry looks like this in the Hosts file
####:ab#:#####:ab#:#### fully.qualified.hostname hostname
After entering the above entry into the Client Machine's Hosts file, all communication with regards to the TDoD Server started working.