Talk:169th Field Artillery Brigade

Dead link
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://www.ausa.org/programs/torchbearer/Documents/TB_Fires_2009LOWRES_300909.pdf
 * In 169th Fires Brigade (United States) on 2011-05-25 01:54:40, 404 NOT FOUND
 * In 169th Fires Brigade (United States) on 2011-06-01 19:09:51, 404 NOT FOUND

--JeffGBot (talk) 19:10, 1 June 2011 (UTC)

Dead link 2
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://www.cong.army.mil/highground/news/Articles/2007/Aug/169Home/ceremony.asp
 * In 169th Fires Brigade (United States) on 2011-05-25 01:54:49, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 169th Fires Brigade (United States) on 2011-06-01 19:10:02, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 19:10, 1 June 2011 (UTC)

Dead link 3
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://www.coloradoguard.army.mil/169fires.html
 * In 169th Fires Brigade (United States) on 2011-05-25 01:54:49, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 169th Fires Brigade (United States) on 2011-06-01 19:10:38, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 19:11, 1 June 2011 (UTC)