Author Topic: Error = -1 (Read 5418 times)

Dwight Sunwall · « **on:** October 10, 2006, 11:10:09 AM »

hey, the GIS layers are great, the Wilderness boundaries especially. I was able to download the files just fine on my home computer. On my work computer I get a TopoFusion error = -1. What is that?

Krein · « **Reply #1 on:** October 10, 2006, 11:20:17 AM »

Best guess is that the request is being blocked by a firewall.

The GIS layers are downloaded from topofusion.com itself, not from Terraserver and OnEarth (sites that were likely permitted for the application to access).

-1 just means the download failed. I'll make the error message more informative and have it suggest a firewall problem.

« **Reply #2 on:** October 12, 2006, 06:17:33 PM »

Can you tell me which urls should be let through the firewall for full functionallity? I've opened:
topofusion.com
terraserver-usa.com
onearth.jpl.nasa.gov
I still have trouble receiving tiles much of the time and get messages from TopoFusion about trouble contacting the server and alerts from my router/firewall like this:
Message: SYN Flood to Host
Source: 192.xxx.xxx.xxx, 1200
Destination:65.54.135.103, 80 (from WAN Outbound)
that seem to corespond to the TopoFusion error messages. Thanks for any help - love the program!

Krein · « **Reply #3 on:** October 14, 2006, 07:11:20 AM »

Those three servers are the only ones needed by TopoFusion. TF.com is only needed to download the GIS layers.

That error message indicates an attack on your IP. See:

http://www.iss.net/securit....ult.htm

I have never heard of the tcp requests being sent by TopoFusion causing such an error. But it is possible there is a setting on your router that is too sensitive for this kind of thing.

Good luck.

Liquidmantis · « **Reply #4 on:** May 25, 2007, 12:16:43 PM »

I was getting this error too. My firewall was proxying the request and and denying it with the error "No URI Found". I added just a filtered, non-proxied HTTP rule for my machine and the download went through.

Liquidmantis · « **Reply #5 on:** May 25, 2007, 12:36:07 PM »

I was getting this error too. My firewall was proxying the request and and denying it with the error "No URI Found". I added just a filtered, non-proxied HTTP rule for my machine and the download went through.