Darn!! I keep forgetting Garmin uses strange communications!!

Perhaps some tech-savvy members with Garmin units could use an application like Wireshark (www.wireshark.org) to see what port(s) the map updater uses. (I'd offer to help, but I have a TomTom.)

All you really need to ask them is which port they are using and whether the communications are TCP, UDP, or both. Once you find out the port, you should be able to go into the router and set an exception for that port. Once the exception is set, you should then be able to communicate.

Of course, this also assumes that business-grade routers work the same as commercial-grade units. My commercial-grade Belkin wireless router doesn't have this problem whatsoever.

On one hand, I do not see anything in the list that Garmin should be using.

On the other hand, nothing in that list appears to be dangerous.

They are file sharing programs, and instant messaging programs. I can see how businesses may not want you to download anything you have not paid a license for (and might possibly contain viruses). I can see businesses perhaps not want employees to waste company time doing instant messaging with friends.

I don't see why you need to have any of those items in your router's blocked list if you are in a typicalhome network setting. Unless you have family members who are downloading illegally and you are getting warnings from your internet provider.

I'll check what ports an update requires...if my unit requires one. I have an $800 firewall in my basement. The same brand my company uses. I do this to keep up with the firmware changes and new features in the new releases. Netgear is garbage... (opinion...)

I took a quick look with Wireshark and it looks like it's limited to TCP traffic on port 80 to www.garmin.com.

The traffic starts out with a standard DNS query (port 53) for www.garmin.com, which in this particular case resolves to 184.31.62.235. Then it's all port 80 traffic from there as far as I could tell.

The port numbers on my side increment normally - starting at 3152 and ending at 3159, which interestingly is listed as navegaweb-port. I think this is purely coincidental, as other network traffic unrelated to the Garmin WebUpdater which preceeds it follows the same sequence (the last unrelated traffic was on port 3151 on my side).

So I'm not sure what the problem is that you're having, unless you're having this problem during the actual update portion of the transaction - something I can't check for you since I did an update recently and therefore none is required at the moment.

You've gotten me pretty curious now though, I'll be watching this thread with interest.

- Phil

If it's not the port(s) then it may be the traffic. Some higher-end firewalls and routers can perform Stateful Packet Inspection (SPI) to see if the contents of the packets look like "real" traffic for that port. So for traffic on port 80 they would be expecting to see requests like...

GET / HTTP/1.1
{etc}

...and responses like...

HTTP/1.1 200 OK
{etc}

If the Garmin updater is using port 80 but not using "standard" commands and responses for HTTP then that could cause SPI-enabled routers or firewalls to block the connection.

Here's more info on the "blockage"....

Happens starting 3-4 minutes into the download...
Garmin App up till the 3-4 min time does show decreasing download times.... I never determined how much data is downloaded before the Router (Versitleguy -- You're correct, it is SPI related) disconnects the Ethernet connection (It reports as Local only)..... 3-4 min into download, and at that time, the Garmin App Download completion time goes from a decreasing to an increasing amount... I've seen it report as high as DAYS to completion, if I walk away and haven't removed the blocks....

My work around is to disable all of the blocks.

Garmin, after two phone calls and one email, will not respond to the requests...... Shame on them!

It seems that each time I find an update, I'm in a time crunch (and forget about the blocks).... And by the time I remember them, and un-block everything, I'm out of time for "Testing"....

I keep saying Next Time I'll un-block only half, and eventually determine which it is.... if it's only one of them.... but that will take LOTS of Time....

I was using the Update once software,

Thanks I'll be watching this thread, too!! !