comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » harrisgeospatial unreachable...
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: harrisgeospatial unreachable... [message #94190 is a reply to message #94187] Fri, 17 February 2017 07:38 Go to previous messageGo to previous message
Jim  Pendleton is currently offline  Jim Pendleton
Messages: 165
Registered: November 2011
Senior Member
On Friday, February 17, 2017 at 6:51:39 AM UTC-7, M Q wrote:
> On Thursday, February 16, 2017 at 11:36:17 AM UTC-5, Helder wrote:
>> Hi,
>> I think this might have to do with differences in the link protocol: http vs. https.
>> If I type in your search I get the following two first hits:
>> http://www.harrisgeospatial.com/docs/ExpandedDICOMFunctional ity.html
>> https://www.harrisgeospatial.com/docs/FILE_UNZIP.html
>>
>> The unsecure version (http) opens immediately. The secure version (https - ssl certificate) takes ages, but eventually opens. Opened once, it's then much quicker the second time around.
>> Both tested with google Chrome from Germany.
>> The site is certified by DigiCert.
>>
>> By the way, there is probably a typo in the error you got:
>> This site can't be reached
>> www.harrsigeopspatial.com too look long to respond.
>>
>> The address "harrisgeo..." is misspelled.
>>
>> Just expanding on Lajos answer. The authority section is:
>> :~$ host -v www.harrisgeospatial.com
>> ...
>> exelisvis.com. 172799 IN NS dns1.exelisinc.com.
>> exelisvis.com. 172799 IN NS dns2.exelisinc.com.
>>
>> ;; ADDITIONAL SECTION:
>> dns1.exelisinc.com. 172799 IN A 151.190.40.10
>> dns2.exelisinc.com. 172799 IN A 151.190.254.251
>>
>> So maybe they have a problem with these servers (dns1 and dns2).
>> They respond well to traceroute...
>>
>> Cheers,
>> Helder
>>
>>
>
> Thanks, this is good information. However, my point is that the link to harrisgeospatial that pops up on a google search for anything to do with IDL doesn't work. Hopefully someone at the company will read these posts and fix the problem.




This symptom sounds like your local admin has blocked or blacklisted the route. From the same node, can you run tracert from your OS command line to "www.harrisgeospatial.com" to see if it's blocked before it hits an external site?

Jim P.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: k-mean clustering idl
Next Topic: Point within country boundary

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 14:00:23 PDT 2025

Total time taken to generate the page: 0.00353 seconds