technical document configuring windows 2003 service pack 1 ... fileon the windows server 2003 sp1...

10
Technical Document Page 1 of 10 Configuring Windows 2003 Service Pack 1 for use with RemoteWare Servers, Portable Systems, Clients, and Workstations After applying Windows 2003 SP1, RemoteWare Administrators will need to add entries in the Windows Firewall Exception List on all RemoteWare Servers, Portable Systems, Clients, and Workstations. The following ways to add entries to the Windows Firewall Exception list are covered in this document: Windows Firewall Notification and Manual Configuration. For details on other methods refer to Microsoft’s documentation. Windows Firewall Notification This is implemented by a user with Administrator rights and requires that the user accept the incoming connection by unblocking the port for the application. This is described below for the components that require unblocked ports: RemoteWare Client, Fxd (for RemoteWare Multicast Client), PcAnywhere and RemoteWare Portable. RemoteWare Client A Windows 2003 SP1 RemoteWare Client will display a Windows Security Alert dialog when receiving an incoming connection from the RemoteWare Server for the first time (see below). In order for the RemoteWare Server to continue to communicate to the Client, the user should choose the Unblock option. Technical Document This adds the RemoteWare Kernel Application to the Windows Firewall Exception list and inbound calls to the Client will be accepted.

Upload: lycong

Post on 01-May-2019

220 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Technical Document Configuring Windows 2003 Service Pack 1 ... fileOn the Windows Server 2003 SP1 RemoteWare machine, go to Start, Settings, and Control Panel. Double click on Windows

Technical Document

Page 1 of 10

Configuring Windows 2003 Service Pack 1 for use with RemoteWare Servers, Portable Systems, Clients, and Workstations After applying Windows 2003 SP1, RemoteWare Administrators will need to add entries in the Windows Firewall Exception List on all RemoteWare Servers, Portable Systems, Clients, and Workstations. The following ways to add entries to the Windows Firewall Exception list are covered in this document: Windows Firewall Notification and Manual Configuration. For details on other methods refer to Microsoft’s documentation. Windows Firewall Notification This is implemented by a user with Administrator rights and requires that the user accept the incoming connection by unblocking the port for the application. This is described below for the components that require unblocked ports: RemoteWare Client, Fxd (for RemoteWare Multicast Client), PcAnywhere and RemoteWare Portable. RemoteWare Client A Windows 2003 SP1 RemoteWare Client will display a Windows Security Alert dialog when receiving an incoming connection from the RemoteWare Server for the first time (see below). In order for the RemoteWare Server to continue to communicate to the Client, the user should choose the Unblock option.

Technical Document This adds the RemoteWare Kernel Application to the Windows Firewall Exception list and inbound calls to the Client will be accepted.

Page 2: Technical Document Configuring Windows 2003 Service Pack 1 ... fileOn the Windows Server 2003 SP1 RemoteWare machine, go to Start, Settings, and Control Panel. Double click on Windows

Technical Document

Page 2 of 10

Below is an example of the Windows Firewall Exception list.

If the Client is running as a service, the Exception entry will appear as Client Communications. Remote Control / pcAnywhere When running Remote Control / pcAnywhere from the RemoteWare Server or Workstation, the Client will be prompted to unblock the pcAnywhere host. Selecting Unblock from the Windows Security Alert options will add pcAnywhere Host to the list of Windows Firewall Exceptions.

Page 3: Technical Document Configuring Windows 2003 Service Pack 1 ... fileOn the Windows Server 2003 SP1 RemoteWare machine, go to Start, Settings, and Control Panel. Double click on Windows

Technical Document

Page 3 of 10

Below is an example of the Windows Firewall Exception list.

Page 4: Technical Document Configuring Windows 2003 Service Pack 1 ... fileOn the Windows Server 2003 SP1 RemoteWare machine, go to Start, Settings, and Control Panel. Double click on Windows

Technical Document

Page 4 of 10

RemoteWare Portable RemoteWare Portable requires a Windows Firewall Exception entry for RemoteWare Server Socket Protocol. The Windows Security Alert dialog will appear on the RemoteWare Portable machine when attempting a connection to a Client. Unblock the application to allow it to function correctly.

Page 5: Technical Document Configuring Windows 2003 Service Pack 1 ... fileOn the Windows Server 2003 SP1 RemoteWare machine, go to Start, Settings, and Control Panel. Double click on Windows

Technical Document

Page 5 of 10

Selecting Unblock from the Windows Security Alert options will add RemoteWare Server Socket Protocol to the list of Windows Firewall Exceptions. .

cument Note: When running RemoteWare Portable on Windows 2003 SP1, if the pcAnywhere Host port on the RemoteWare Client is not unblocked promptly on the Security Alert dialog box, pcAnywhere will stop functioning and will display an, “Unable to attach to the specified device,” error message.

Page 6: Technical Document Configuring Windows 2003 Service Pack 1 ... fileOn the Windows Server 2003 SP1 RemoteWare machine, go to Start, Settings, and Control Panel. Double click on Windows

Technical Document

Page 6 of 10

To resolve this issue, add pcAnywhere host to the Windows Firewall Exception list on the RemoteWare Client. Multicast RemoteWare Multicast requires that the application Fxd be added to the Windows Firewall Exception list on the RemoteWare Client in order for Multicast to function correctly. When the Security Alert dialog appears, choose to unblock the application Fxd.

Page 7: Technical Document Configuring Windows 2003 Service Pack 1 ... fileOn the Windows Server 2003 SP1 RemoteWare machine, go to Start, Settings, and Control Panel. Double click on Windows

Technical Document

Page 7 of 10

Manual Configuration This is implemented by the user and requires manually selecting the program to add to the list. On the Windows Server 2003 SP1 RemoteWare machine, go to Start, Settings, and Control Panel. Double click on Windows Firewall and click on the Exceptions tab. Choose Add Program, click on browse, and select the application to add: For the RemoteWare Server, add <RemoteWare install drive>\RWS\system\SOC_XNET.exe For Multicast on RemoteWare Server, add <RemoteWare install drive>\RWS\NodeSys\Fxds.exe

Page 8: Technical Document Configuring Windows 2003 Service Pack 1 ... fileOn the Windows Server 2003 SP1 RemoteWare machine, go to Start, Settings, and Control Panel. Double click on Windows

Technical Document

Page 8 of 10

For the RemoteWare Client, add <RemoteWare install drive>\RWS\NodeSys\Win32\RWKernel.exe

Page 9: Technical Document Configuring Windows 2003 Service Pack 1 ... fileOn the Windows Server 2003 SP1 RemoteWare machine, go to Start, Settings, and Control Panel. Double click on Windows

Technical Document

Page 9 of 10

For Multicast on a RemoteWare Client, add <RemoteWare install drive>\RWS\NodeSys\Fxd.exe and <RemoteWare install drive>\RWS\NodeSys\Fxds.exe For pcAnywhere, add <RemoteWare install drive>\Program Files\Symantec\pcAnywhere\Awhost32.exe

Page 10: Technical Document Configuring Windows 2003 Service Pack 1 ... fileOn the Windows Server 2003 SP1 RemoteWare machine, go to Start, Settings, and Control Panel. Double click on Windows

Technical Document

Page 10 of 10

For Portable, add <RemoteWare install drive>\RWS\system\SOC_XNET.exe