Google Maps and Sonicwall NSA 2400
We have recently configured a system for our internal users that uses the Google maps API in order to show where our customers are in conjunction to our sales representatives. We added to our SonicWall the Address Object for Google Maps as a FQDN using '*.google.com' For some reason this doesn't appear to function and we get tons of alerts from the Sonicwall as well as the google maps pulls up rarely if ever.
I listed an excerpt from it in the Code pane below. Has anyone tried setting anything like this up? If so, I would welcome the tips on getting it going.
I listed an excerpt from it in the Code pane below. Has anyone tried setting anything like this up? If so, I would welcome the tips on getting it going.
04/02/2010 08:02:32.672 - Info - Dynamic Address Objects - Unable to resolve dynamic address object - 0.0.0.0 - 0.0.0.0 - FQDN=*.google.com
04/02/2010 08:03:33.048 - Info - Dynamic Address Objects - Removed host entry from dynamic address object - 0.0.0.0 - 0.0.0.0 - FQDN=*.google.com; Host=74.125.47.99
04/02/2010 08:03:33.048 - Info - Dynamic Address Objects - Added host entry to dynamic address object - 0.0.0.0 - 0.0.0.0 - FQDN=*.google.com; TTL=211; Host=74.125.67.99
04/02/2010 08:03:33.064 - Info - Dynamic Address Objects - Unable to resolve dynamic address object - 0.0.0.0 - 0.0.0.0 - FQDN=*.google.com
04/02/2010 08:04:33.384 - Info - Dynamic Address Objects - Unable to resolve dynamic address object - 0.0.0.0 - 0.0.0.0 - FQDN=*.google.com
04/02/2010 08:06:11.368 - Info - Dynamic Address Objects - Unable to resolve dynamic address object - 0.0.0.0 - 0.0.0.0 - FQDN=*.google.com
04/02/2010 08:07:11.688 - Info - Dynamic Address Objects - Removed host entry from dynamic address object - 0.0.0.0 - 0.0.0.0 - FQDN=*.google.com; Host=74.125.67.99
fbcbloodcenter
try maps.google.com instead of *.google.com ?
ASKER
That is just the website for it. They use tons of servers like mh2.google.com kh4.google.com etc etc etc
try this: it looks like all of their map servers are on a 74.125.x.x subnet. it's probably safe to say google owns at least the enitire class B subnet here. Instead of using a name that must be resolved create a new address object (range) 74.125.0.0-74.125.255.255 or something similar. You can be a liitle more restrictive but this should at least let you know if it will work like that.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.