Comments
Sort by recent activity
If I change <SecureRemoting>False</SecureRemoting>
on client machine, will I be able to connect to repository on different domains including the same domain where the client is or shall I need to change the setting on the client again?
Thanks / comments
If I change <SecureRemoting>False</SecureRemoting>
on client machine, will I be able to connect to repository on different domains including the same domain where the client is or shall I need to c...
Is there anything else that could help with this problem? / comments
Is there anything else that could help with this problem?
I'm still working on it. It is very strange. / comments
I'm still working on it. It is very strange.
SQL Server service is running on the server,
I can ping the server,
and the port 7398 is open.
Everything looks ok.
What credential will be used when connecting to the Response service on a different domain? Should I see a login screen or something?
Thanks for help / comments
SQL Server service is running on the server,
I can ping the server,
and the port 7398 is open.
Everything looks ok.
What credential will be used when connecting to the Response service on a differe...
Hi Daniel,
Can you confirm that I’m doing the right thing. I have DOMAIN1 and Response Repository installed on SERVER1 on DOMAIN1. On DOMAIN2, I have SQLSERVER2. I created DOMAIN2\sql_demo domain windows login account on DOMAIN2 which is local administrator on SQLSERVER2.
My question is: Can I connect from Response Repository (DOMAIN1) to SQLSERVER2 (DOMAIN2) using operating DOMAIN2\sql_demo domain windows login account to monitor system part of the server without trust links between domains?
It is confusing as previously you said that SQL Response requires that the repository and the SQL Server be on the same domain (Posted: Mon Mar 16, 2009 3:11 pm), and later you said that If I’m running the Alert Repository on Windows Server 2003 or later, I should be able to specify the windows account to be used in the server properties. This does not require trust links between the domains (Posted: Wed Apr 15, 2009 3:33 pm).
Thanks for your help / comments
Hi Daniel,
Can you confirm that I’m doing the right thing. I have DOMAIN1 and Response Repository installed on SERVER1 on DOMAIN1. On DOMAIN2, I have SQLSERVER2. I created DOMAIN2\sql_demo domain...
Hi Daniel,
Thanks for help - I'm just trying to setup SQLResponse for 10 servers on 3 different domain.
Are you saying I should be able to specify the windows account to be used in the server properties to connect to Windows Server on a differnet domain without trust links between domains?
Does it mean that if I'm running Alert Repository on Windows Server 2003 on DEV domain, I should be able to connect to SERVER2 on DEV2 domain using for example SERVER2\WindowsLoginAcount1 or DEV2\WindowsLoginAcount2 without trust links between domains?
Please let me know if it makes sense?
Thanks for help / comments
Hi Daniel,
Thanks for help - I'm just trying to setup SQLResponse for 10 servers on 3 different domain.
Are you saying I should be able to specify the windows account to be used in the server prope...
I spoke to few people and we all think it is a strange requirement that repository and the SQL Server must be on the same domain. This is completly out of the SQL Server concept as SQL Server alows connection to SQL Servers from different domains.
It looks like your developers have a "small" problem here (using DCOM)?
How do you expect DBAs to monitor SQL Servers on multi domain enviroement using SQLResponse? Not professional enough for me for next licence renewal. / comments
I spoke to few people and we all think it is a strange requirement that repository and the SQL Server must be on the same domain. This is completly out of the SQL Server concept as SQL Server alows...
Is it possible to disable SQLResponse Alert to connect to monitored server using windows login account for collecting Windows server information? I prefer to collect only information about SQL Server and in that case I can use only one Alert Repository for all SQL Servers accross multi domains as SQL Authentication is working fine accross multi domain? / comments
Is it possible to disable SQLResponse Alert to connect to monitored server using windows login account for collecting Windows server information? I prefer to collect only information about SQL Serv...
Thank you for your time and quick replay. Even in that case, new firewall policies will need to be created which we do not really want. Our current policy is that only SQL Server ports are open for communication from one central point. Everything else is disabled so we need really to monitor all SQL Servers from one central machine which has access to all SQL Server using only ports assigned to SQL Servers. Does it make any sense? Security is still the most important factor…
Thanks again for help. / comments
Thank you for your time and quick replay. Even in that case, new firewall policies will need to be created which we do not really want. Our current policy is that only SQL Server ports are open for...
Thanks Priyasinha,
That's great news. When can we expect V 3.0 release? We have already bought SQL monitor licences but for that reason we are also considering another SQL Monitoring product.
Regards / comments
Thanks Priyasinha,
That's great news. When can we expect V 3.0 release? We have already bought SQL monitor licences but for that reason we are also considering another SQL Monitoring product.
Reg...