This is actually pretty common and any manager worth his spit aught to be able to tell the difference between "Effort" and "Duration" estimates and should have a rough idea of what percent of your time is targeted at the project.
For example, if you said it would take you 240 hours to complete the project (effort), and I know that you're only going to be able to put about 50% of your time towards the project, that the total duration is likly going to be around 12 weeks.
If I really need that project done in 8 weeks, it means I've got to find ways to get 50% of your non-project time removed from your plate. If that means getting someone else on the team to look at the network issue or finding ways to mitigate the impact of the move on you, so be it, but I, as a manager, need to find a way to get you up to 75% of your time as project time.
This is actually pretty challenging. By default, under best circumstances, assume that any average employee is only going to have 90% of their time available. The other 10% goes to checking email, answering phone calls, bathroom breaks, etc... Typically, I like to estimate 80%, especially for people who have to bounce between projects or are on user-centric projects as there will inevidibly be delays and thrashing.
Even with that 80%, you're going to lose some portion of it to meetings. Heck, most folks have atleast 2 hours of meetings a week for status updates, tech reviews, performance evals, planning, etc... Each two hours of meetings is another 6 1/4% off that 80% number.
So as another Sr Dev/Jr Manager individual, I'd say keep making sure that your manager is aware that your estimates are for Effort, not duration, and make sure he/she is knoledgable about your schedule and other responsibilities.
-Rick