Incorrect credentials or insufficient permissions

• 
  I forget that I'm using SA user to login in the database.

  berlington.barnett April 19, 2012 16:22

  - 0 +
• 
  Hi,
  
  Please have a look at this help page for details on what ports need to be open.
  
  The username format can be either 'domain\uesrname' or 'username@domain.com', where the username should ideally be a domain account.
  
  Cheers,

  RBA April 20, 2012 05:22

  - 0 +
• 
  Thank you for you answer, but the problem was that the software must be installed in the same network where database is and I did from a diferent network with a routed relation.
  
  I think that this situation must be documented for the future.
  
  Regards

  berlington.barnett April 20, 2012 10:07

  - 0 +
• 
  Hi,
  
  Apologies for the misunderstanding.
  
  You can use SQL Monitor from a remote location, although it will require around 10-15kB/s of bandwidth which is usually a non-issue for internal networks but can be noticeable over slow or constrained VPNs.
  
  As for permissions, you can specify 'builtin\administrator' with the admin password to monitor a remote machine that is off the domain.
  
  Alternatively, you can create local user accounts with the same name and password on the machine running SQL Monitor and the production server (workgroup style).
  
  It can be helpful in troubleshooting to test any credentials you'd like to use outside of SQL Monitor first. I.e. From the monitoring machine and try to access the admin share / remote registry / WMI of the monitored machine using the desired login details.
  
  I'll review the documentation and see if I can ensure this scenario is covered.
  
  Regards,

  RBA April 20, 2012 10:20

  - 0 +

Add comment

Please sign in to leave a comment.