IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Tivoli Monitoring Startup Center > Remote Execution and Access
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Windows Targets
Some RXA operations rely on VBScript and Windows Management Instrumentation (WMI) calls to execute scripts on Windows targets. If the Windows Scripting Host (WSH) or the WMI service is disabled on the target, or if VBScript is otherwise disabled, some WindowsProtocol methods will not work.
If you intend to access Windows targets using the SMB protocol over NetBIOS, which is determined by setSMBTransportType(), then port 139 or the port specified by setNetBIOSPort(), must not be blocked by firewalls or IP security policies. The Enable NetBIOS over TCP/IP must also be selected in the Control Panel settings for the machine's network connections properties (Control Panel → Network and Dial-Up Connections → <some connection> → Properties → Internet Protocol (TCP/IP) → Advanced → WINS → Enable NetBIOS over TCP/IP).
Consult the documentation for your firewall to determine that these ports are not blocked for inbound requests.
To determine if security policies are blocking these ports, click Start → Settings → Control Panel → Administrative Tools. Depending on whether your policies are stored locally or in Active Directory, the next steps are as follows:
- Locally stored policies: Administrative Tools → Local Security Policy → IP Security Policies on Local Computer.
- Policies stored in Active Directory: Administrative Tools → Default Domain Security Settings → IP Security Policies on Active Directory.
Examine the IP security policies and edit or remove filters that block the ports listed above. Table 1 lists the ports reserved for NetBIOS. Ensure that all ports currently used by RXA are not blocked.
NetBIOS Reserved Ports
Port number Use 135 NetBIOS Remote procedure call. At this time, RXA does not use this port. 137 NetBIOS name service. 138 NetBIOS datagram. At this time, RXA does not use this port. 139 NetBIOS session (file/print sharing). 445 CIFS (On XP and Win2K).
A utility program (testconn) is provided in the RXA .zip and JAR files. It can be used to determine whether a remote Windows target is configured to run Server Message Block protocol on top of NetBIOS (NetBIOS over TCP/IP) by using port 139, or whether the target is configured to run SMB on top of TCP/IP (without the NetBIOS layer) by using port 445. The target machine must have the Remote Registry service started (which is the default configuration) in order for RXA to connect to the target machine. A utility program (getregkey) is provided in the RXA zip and JAR files. It can be used to determine whether a Windows target (local or remote) has Remote Registry management enabled.
RXA requires access to the hidden remote administrative disk share for access to the system %TEMP% and other directories. Access to the Interprocess Communications share (IPC$) is also required for RXA to access remote registries. Before you access the Interprocess Communications share (IPC$), make sure the Server service is started (Control Panel → Administrative Tools → Services → Server). You can use the testconn.exe utility (in the \diagtools directory) to verify that the administrative share is accessible. RXA requires Simple File Sharing to be disabled. The next section details information specific to operating systems.
Parent topic:
Remote Execution and Access