THAT is never stupid. It's the obvious things that people always miss. Thanks for the suggestion. Here is the output from the ping testing:
H:\>ping asptts
Pinging asptts.ccchsd.gov \[172.18.13.172] with 32 bytes of data:
Reply from 172.18.13.172: bytes=32 time<1ms TTL=125
Reply from 172.18.13.172: bytes=32 time<1ms TTL=125
Reply from 172.18.13.172: bytes=32 time<1ms TTL=125
Reply from 172.18.13.172: bytes=32 time<1ms TTL=125
Ping statistics for 172.18.13.172:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
H:\>ping 172.18.13.172
Pinging 172.18.13.172 with 32 bytes of data:
Reply from 172.18.13.172: bytes=32 time<1ms TTL=125
Reply from 172.18.13.172: bytes=32 time<1ms TTL=125
Reply from 172.18.13.172: bytes=32 time=1ms TTL=125
Reply from 172.18.13.172: bytes=32 time<1ms TTL=125
Ping statistics for 172.18.13.172:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
H:\>ping -a 172.18.13.172
Pinging asptts.ccchsd.gov \[172.18.13.172] with 32 bytes of data:
Reply from 172.18.13.172: bytes=32 time<1ms TTL=125
Reply from 172.18.13.172: bytes=32 time<1ms TTL=125
Reply from 172.18.13.172: bytes=32 time<1ms TTL=125
Reply from 172.18.13.172: bytes=32 time=1ms TTL=125
Ping statistics for 172.18.13.172:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms