Forum

Sorry, no blocks found against those IP addresses.

Possibly.  It appears an automated block was applied at about 1417 local time yesterday.  I've cleared that block, so you should have access again.

I did a quick check.  Most recent block logged was at 16:06 local time on 3/25. None in place currently for your IPv4 address range.

Jacques, the trigger for the block was frequent calls to the file_search utility, and the search generated errors. Luckily, this type of block is reset the next day.

Paul

Jacques, we're checking on this. A temporary block went in place, and was cleared this morning. We haven't identified what triggered the block as yet.

Paul

Jun,
A check shows no blocks at our end.  We saw successful accesses from xx.xxx.xx.xx on 2/8/2019.

Paul

Marco,
Chris checked into this and did not find any blocks in place at our site. He did see traffic from xx.xxx.xx.xx today.

Jun,

I checked our firewall logs and have not seen any blocks for those IPs since 12/23.  The problem may be upstream of our servers. Unfortunately we are subject to a partial government shutdown, so our normal ways of looking into the problem from our end are unavailable.  Sorry.

I did a check of the firewall and logs.  There is no sign of a block against any IP 172.16.202.* in December or November.  I tried the command line shown, and it was successful in downloading a file to a system here at GSFC.  I'm sorry, but I'm not sure what is causing your ti...

Ge,

Thanks for letting us know about your problem. We have checked through the system and made some adjustments. Please try again at your convenience.

Paul