Application Perf Mgmt (BAC / BSM) Practitioners Forum
Showing results for 
Search instead for 
Do you mean 

SiteScope was unable to connect to the remote server

Trusted Contributor

SiteScope was unable to connect to the remote server

Hi Experts,

 

SiteScope version: 10.14

OS: Windows 2003 server

 

I am not able to add Windows server 2003 to monitoring.Its giving below error.

SiteScope was unable to connect to the remote server.Reason : Could not retrieve counter values for :Timestamp_PerfTime,Frequency_PerfTime,Timestamp_Sys100NS

 

I am using WMI as connection method.

 

Remote registry ,server and WMI services are running fine on the remote server.

 

I am able to ping remote server and RDP.

 

port 135 is open to the remote server from SiteScope server.

 

Regards,
Janardhan
#Be the change, you want to see#
10 REPLIES
Advisor

Re: SiteScope was unable to connect to the remote server

Port 137 or 139 required to be opened for sitescope from the remote server

Regards'Arjun
Trusted Contributor

Re: SiteScope was unable to connect to the remote server

port 139 is for NetBIOS. I want to use WMI,for which 135 is the port.
Regards,
Janardhan
#Be the change, you want to see#

Re: SiteScope was unable to connect to the remote server

if you can't get data from counters check on the server they are getting updated, maybe on the remote server is no data. in some cases when you try to open the remote counter you need to chage the monitor method.

Honored Contributor Honored Contributor

Re: SiteScope was unable to connect to the remote server

 

Yes, the first call by WMI (DCOM) uses port 135, and then is dynamically assigned through negotiations. These negotiated random ports run between 1024 and 65000. For this to work in my enviornement I requested firewall rules for all the high ports 1024-65k. SiteScope couldn't communicate via WMI until I had those firewall rules added. Of course if you have no firewalls between SiteScope and the Remote servers then you have no worries.

 

Regards,

 

David

 

 

Trusted Contributor

Re: SiteScope was unable to connect to the remote server

Spoiler
 

 

Thanks David.

 

Port 139 is also open . I am able to add the physical servers without any issue with port 135 open.

 

I am facing this issue on Windows VM's .Even though port 135 and 139 are open ,I am not able to get any counters from them .I added them in remote servers successfully ,but not getting any data for CPU ,memory or Process monitors.

Regards,
Janardhan
#Be the change, you want to see#
Valued Contributor

Re: SiteScope was unable to connect to the remote server

Hi Janardhan

 

I am also experiencing the same problem , How did you resolve the problem

 

Regards

Bilal Aman

Honored Contributor

Re: SiteScope was unable to connect to the remote server

Was this issue resolved? I am facing the same issue.

 

Regards,

Sujith

Close the thread if your issue is resolved to make the thread meaningful and complete. Do show gratitude to people who helped you by assigning points.
Valued Contributor

Re: SiteScope was unable to connect to the remote server

Hi Sujith

 

I was able to get the issue Resolved . Problem is with Win32_Perf Calsses are not avaialble or corrupted  due to which  it creates a problem  

 

If had many such issues and had multiple solution , Please find the solutions mentioned in the attachement

 

 Hope this helps

 

Regards

Bilal Aman

 

Honored Contributor

Re: SiteScope was unable to connect to the remote server

Thanks much Aman. Appreciate your help. But none of the solution worked for me. In my case remote server is windows server 2003 so commands are little different :). I could not try solution #2 which is for .MOF files as I did not find these on remote server.

 

Regards,

Sujith

Close the thread if your issue is resolved to make the thread meaningful and complete. Do show gratitude to people who helped you by assigning points.
Valued Contributor

Re: SiteScope was unable to connect to the remote server

Sujit

 

Did you try to use wbemtest to validate you cannot see perfos classes ?

 

for windows 2003 solution 3 should help , Also check the Perf OS registry to check if that is disabled

 

Check the PerfOS Registry  if it is disabled enable it(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfOS\Performance)   

 

Regards

Bilal Aman