FS6200 Server System Implementation Guide - Public Support ...

• Microsoft Network Client
This feature is supported by two services: Workstation and TCP/IP NetBIOS Helper.
Microsoft Network Client enables users to share files, print, and log on to the network
by creating and maintaining network connections to remote servers using the SMB
protocol, and by providing support for the NetBIOS over TCP/IP (NetBT) service and
NetBIOS name resolution for clients on the network.
A set of firewall rules for file and printer sharing are enabled to enable the following
outbound connections:
- Ping requests for both IPv4 and IPv6
- NetBIOS Datagram transmission and reception (UDP 138)
- NetBIOS name resolution (UDP 137)
- NetBIOS Session Service connections (TCP 139)
- SMB transmission and reception (TCP 445)
Consequently, from the JProcessor environment, you can ping a remote computer or
map a drive to a share on a remote computer.
Note: Inbound Internet Control Message Protocol (ICMP) requests to the host of the
JProcessor environment are blocked by default. This restriction affects ping
commands, which are ICMP echo requests. As a result, ping commands from remote
computers cannot reach the Windows host of the JProcessor environment, not even
those sent from the MCP. Refer to “Enabling MCP Ping Commands through the
Intra-Platform Connection For JProcessors” in Section 4 of this guide for information
on how to add a firewall rule to enable inbound ICMP requests.
• Domain Name System (DNS) Client
This feature is supported by a single service: DNS Client.
DNS Client registers the host name of the JProcessor environment and enables you to
use computer names, in addition to IP addresses, when accessing other computers in
the network.
A firewall rule is predefined to open UDP port 53 for outbound DNS requests.
• Remote Desktop
Setting Up and Operating the JProcessor Specialty Engine
This feature is supported by three services: Remote Desktop Services, Remote
Desktop Configuration, and Remote Desktop Services UserMode Port Redirector.
You can make a Remote Desktop connection from your Operations Server to the host
of the JProcessor environment and vice versa.
To connect to a remote computer from the JProcessor environment, click Start, click
All Programs, click Accessories, and then click Remote Desktop
Connection.
Included in the JProcessor Security Policy is a predefined Remote Desktop firewall
rule for inbound connections. This rule opens TCP port 3389, which enables remote
connection. However, the scope of the Remote Desktop firewall rule has been
modified to restrict inbound remote connections, allowing connections only from the
following IP addresses on the management LAN:
8222 3694–000 6–3