http://coderscooler.com/2011/08/08/ms-sql-create-failed-for-user-error-during-database-restore/
Had problems getting the user permissions to populate when I restored the db on a new server
Had to run this script to get each one to work
And a very useful link on opening the right ports
http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx
Dont forget also UDP on 1434 and the profile needs to be one or all of Domain/Private/Public. I found it would only work if I had public set which leads me to believe I have a network problem to fix. I set the IP address scope very tight to avoid any problems.
UPDATE – I found that the public ip addresses being open was not a good idea at all and I should have been using private ones. This will limit the risk of outsiders using the open ports, reduce the latency and also reduce the billed bandwidth. It is still worth locking down the range of private ips that can access those ports