Talk about over kill. When rebuilding the indexes and you need to ensure that users aren’t using the database, simply put the database into single user mode.
Database reindexing can be completed while users are using the database, the will simply get error messages as the sessions timeout because the table is in use by the reindexing job.
Good answer for what should have been done, but not to the question asked !
I suspect the user was not really connected. If that is your only VPN device, and you shut the access on the Internet side, then there is no way that someone could remain connected. I suspect that the VPN session did not clear, so the connection between the concentrator and the database appeared to still be in place. If you had done a ‘clear sessions’ on the concentrator, the database session would also have dropped. Shutting the inside interface just did the same thing.
Just for good measure, check what you have acessible from the Internet, and confirm that there is no other VPN device, or anything that could be used to jump from there to the VPN concentrator. I don’t think there will be, but just do this review to make sure your security is tight.
Next time, follow Jdleon’s advice and make the change on the database, which IS a far better way to stop access, and stops local users as well. Also change the banner message on the Concentrator to say that this database is not available. That way VPN users can access anything else, like e-mail, and will not just get an error message because the VPN will not connect.