In the Daily Scrum meeting, why is it so hard to get people to discuss with each rather than the Scrum Master (project manager in disguise)

The Daily Scrum is a very simple, and yet a very integral part of the Scrum process. The idea is to get the team to work with each other, and discuss the items that they have done, are going to be doing next, and any obstacles (impediments) in their path. These are 3 questions:
1. What tasks have you done since yesterday’s meeting?
2. What tasks are you going to get done today?
3. What impediments are blocking you?
However, there are many problems in this simple concept. Ideally, what would need to happen is that the team acts like an empowered group of people in charge of executing all the tasks for the Sprint cycle. Every day, they would get together for a short meeting, and discuss these 3 questions (without getting into 2 much detail). This is supposed to be like a discussion between team members, with each team member taking their turn to explain their activities to the other team members. This makes them feel empowered, and also feel that this is different from giving the status to a project manager.
However, I have seen most cases where this is not what happens. In the project, it is typically a manager who plays the role of a Scrum Master (and to further qualify, it would be the Project Manager or Program Manager) who plays the role of the ScrumMaster. For a person in this role, it is very hard to explicitly move away from turning this into a daily status meeting (since for a Project or Program Manager, this is a very handy meeting to get detailed status on a daily basis as to what is happening in the project). This entire feeling rubs off onto the team members, and they also feel that they are in fact reporting daily status to the project manager (in the shape of a Scrum Master). So what happens ?
Information that the team members share is done while addressing the Scrum Master rather than addressing the group, and it is the Scrum Master who then asks the questions. This inhibits the other team members from asking questions (including questions that would help them), and pretty soon everybody is talking to the Scrum Master only. The next effect is that the team members stop realizing any value to them of the Daily Scrum, and look for reasons to avoid it. I have seen this happen in 2 teams where the team members finally pushed back and got the Daily Scrum changed to happen only 3 times a week. I can be pretty sure that if this would continue, the next couple of Sprints may see the team members calling for the Scrum Master to get the current status directly from the team members rather than have a Daily Scrum meeting where they are expected to sit and hear other people talk about issues that seemingly don’t affect them.
How can this be addressed ? Unfortunately, this is something that the Scrum Master has to guide, in terms of ensuring that people do not start to address their Daily Scrum information to them, and instead address the team. In addition, the Scrum Master needs to realize that the primary aim of this role is to facilitate the discussion, and to ensure that impediments faced by the team are removed quickly.