I would agree with JeromeR that "it depends" (all good UX questions are answered that way :-). More detail about your audience, the situation, other elements of the page, etc. may change the answers you get.
I think a slider might be a good solution (depending), though if the user does not need the precision of additional text boxes to specific detailed values, I would think that might clutter things up - unless your users DO need that level of specificity.
I also agree with Vlad that hitting the server with every single change of the slider could be pretty onerous for the user (especially if fine granularity is needed), so some sort of "submit changes to my filter" might be a good control to add... especially if there are MANY filters to set.
That, however, will also depend on the amount of data that is being loaded with each new request: if each server hit will only pull down a small amount of data and be pretty quick, you might get away with a request for every adjustment. If the results will be large for any given request, however, and users are likely to need to make many adjustments, you might want to let them tailor the details before explicitly submitting the request.
I personally do NOT like using checkboxes for range-type values like this (if only because they tend to take up more space and put more cognitive load on the user due to more decisions), but as always, you will best know the context for this control.
So there you go: it depends. But maybe this gives you a little more to think about. Good luck!