Wavecom W40PC, Руководство пользователя

Страница: 49 / 264

WAVECOM Decoders v6.15 W40PC, W41PC, W51PC Install & Uninstall
•
41
W51LAN with third party software (DCOM required)
The W51LAN can be used from third party software (like shoc RSM available from
www.shoc.ch) like a standard W51PC. For use and installation follow the instructions of the
third party software.
W51LAN Stand alone (DCOM not required)
Connect a monitor, keyboard and mouse to the W51LAN. For software updates you can
connect a USB-CD ROM to the USB connector ion front of the unit..
Hyper-Threading
Currently Hyper-Threading is not yet supported by WAVECOM decoders. If you have
problems, then disable it.
DCOM configuration for firewalls
Note:
A paper regarding the setup of DCOM is available at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/dndcom/html/msdn_dcomfirewall.asp
DCOM's dynamic port allocation feature offers great flexibility in that programmers and
administrators alike are free from the burden of having to configure (or hard code) applications
to specific ports, free from resolving conflicts between multiple applications attempting to use
the same port(s), and so on. Unfortunately, because DCOM (by default) is free to use any port
between 1024 and 65535 when it dynamically selects a port for an application, it is rather
"firewall unfriendly" out of the box. Configuring your firewall to leave such a wide range of
ports open would present a serious security hole. Microsoft's developers realized this and have
implemented a feature that allows you to restrict the range of ports that DCOM will use to
assign to applications.
Here is a rundown of the transport protocols that DCOM will use depending on the
client/server platform:
Platform Protocol
Microsoft Windows NT 4.0 <-> Windows NT 4.0 UDP
Microsoft Windows 2000 <-> Any TCP (*)
Microsoft Windows 95 or Windows 98 <-> Any TCP
DCOM for UNIX <-> Any TCP
The Windows NT 4.0 implementation of DCOM uses UDP wherever it can because
benchmarks show that it can outperform TCP in certain scenarios. Unfortunately, it is very
difficult to make UDP applications work through firewalls without exposing your network to
unnecessary risks. Before continuing, be sure you make TCP the default protocol on all
Windows NT servers by moving the "NCACN_IP_TCP" value to the top of the list in the
DCOM Protocols named value of the
HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc
registry key using regedt32.exe. To
eliminate a 30-45 second delay when connecting to TCP only servers, the same change should