| harrisgeospatial unreachable... [message #94182] |
Thu, 16 February 2017 08:06  |
astroboy.20000
Messages: 39
Registered: August 2012
|
Member |
|
|
hello,
For the last couple of weeks whenever I do a websearch on IDL,for example
"IDL decompress dicom" I get alot of search results that point me to www.harrisgeospatial.com, which is not a surprise since Harris bought Exelis about 18 months ago. I know that, since I hired on at Exelis/Harris six weeks ago.
Nothing happens when I click the link, eventually I get the following message:
This site can't be reached
www.harrsigeopspatial.com too look long to respond.
I'm using Chrome. With IE the error says I should make sure www.harrisgeospatial.com exists.
Not sure what would happen with Safari or Firefox but I'm guessing nothing good.
This is sort of a hoot.I talked to someone in Boulder and I'm not the only person who's having problems. If I was running Harris someone would have lost their job.
|
|
|
|
|
|
| Re: harrisgeospatial unreachable... [message #94184 is a reply to message #94182] |
Thu, 16 February 2017 08:36  |
Helder Marchetto
Messages: 520
Registered: November 2011
|
Senior Member |
|
|
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
On Thursday, February 16, 2017 at 5:06:37 PM UTC+1, M Q wrote:
> hello,
>
> For the last couple of weeks whenever I do a websearch on IDL,for example
> "IDL decompress dicom" I get alot of search results that point me to www.harrisgeospatial.com, which is not a surprise since Harris bought Exelis about 18 months ago. I know that, since I hired on at Exelis/Harris six weeks ago.
>
> Nothing happens when I click the link, eventually I get the following message:
>
> This site can't be reached
> www.harrsigeopspatial.com too look long to respond.
>
>
> I'm using Chrome. With IE the error says I should make sure www.harrisgeospatial.com exists.
>
> Not sure what would happen with Safari or Firefox but I'm guessing nothing good.
>
>
> This is sort of a hoot.I talked to someone in Boulder and I'm not the only person who's having problems. If I was running Harris someone would have lost their job.
|
|
|
|
| Re: harrisgeospatial unreachable... [message #94187 is a reply to message #94184] |
Fri, 17 February 2017 05:51 |
astroboy.20000
Messages: 39
Registered: August 2012
|
Member |
|
|
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.
|
|
|
|
|
|
| Re: harrisgeospatial unreachable... [message #94189 is a reply to message #94187] |
Fri, 17 February 2017 07:35 |
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 synmptom 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.
|
|
|
|
| Re: harrisgeospatial unreachable... [message #94190 is a reply to message #94187] |
Fri, 17 February 2017 07:38 |
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.
|
|
|
|
|
|
|
|
| Re: harrisgeospatial unreachable... [message #94202 is a reply to message #94195] |
Tue, 21 February 2017 13:27 |
astroboy.20000
Messages: 39
Registered: August 2012
|
Member |
|
|
On Friday, February 17, 2017 at 1:07:36 PM UTC-5, fawltyl...@gmail.com wrote:
> On Friday, February 17, 2017 at 6:44:41 PM UTC+1, M Q wrote:
>
>> H:\>tracert www.harrisgeospatial.com
>>
>> Tracing route to www.exelisvis.com [10.10.10.29]
>> over a maximum of 30 hops:
>>
>> 1 1 ms 1 ms 1 ms 10.38.7.1
>> 2 <1 ms <1 ms <1 ms ushrn1-1-fws001.net.harris.com [192.124.3.65]
>> 3 * * * Request timed out.
>> 4 * * * Request timed out.
>> 5 * * * Request timed out.
>> 6 * * * Request timed out.
>> 7 *
>
> I don't understand this at all. 10.*.*.* addresses are private, they are used only on local networks:
>
> NetRange: 10.0.0.0 - 10.255.255.255
> CIDR: 10.0.0.0/8
> NetName: PRIVATE-ADDRESS-ABLK-RFC1918-IANA-RESERVED
> NetHandle: NET-10-0-0-0-1
> Parent: ()
> NetType: IANA Special Use
> OriginAS:
> Organization: Internet Assigned Numbers Authority (IANA)
> RegDate:
> Updated: 2013-08-30
> Comment: These addresses are in use by many millions of independently operated networks, which might be as small as a single computer connected to a home gateway, and are automatically configured in hundreds of millions of devices. They are only intended for use within a private context and traffic that needs to cross the Internet will need to use a different, unique address.
>
> Seems like a DNS problem.
>
> regards,
> Lajos
I finally contacted someone at Harris who's familiar with this problem. It turns out that there's an internal firewall that prevents people in the building from accessing www.harrisgeospatial.com. I can get an exemption, or, I'm told I can take my laptop to the Starbucks next door and I'll be able to access the website with no trouble at all.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
