Well, it looks like we might have gotten to the bottom of it.
We had a service running that was an artifact from something that had been tried a while back.
VboxVMService was still installed and running.
As soon as we killed that, BINGO!, we were able to get in.
I hope this helps somebody :)