They will eventually load, but they will take longer than the other Dashboard Reports.
This is expected behavior, because we don't pre-build the required datasets to run these two reports with a filter on client ip. While the Reporter database is configured with pre-built datasets, that allow all pre-defined reports to run as efficiently as possible, not all combinations, can be ready made in advance, especially when we add in our own filtering. In this case , the reports are running fine, but the user does need to wait a while Reporter builds the required sets on the fly to fill our the Report.
Look to this article for ideas on how to improve the performance of these, and other reports: