B
Troubleshooting
74
Installation Suggested
Solution
During installation of EFW NIC
on Windows 95, receive
message: “A required .DLL file
WS2_32.DLL, was not found.”
Your Windows 95 system has not been upgraded for Windows Socket 2. To host an embedded
firewall, Windows 95, must be updated for Windows Socket 2 and year-2000 compliance. These
updates can be found at: http:// www.microsoft.com/windows95/downloads/contents/
wuadmintools/s_wunetworkingtoolsw95sockets2/default.asp. Cancel the installation, apply these
updates and then try the installation again.
During installation of EFW NIC
with the Windows Active
Desktop running, the
installation hangs
Temporarily turn off Windows Active Desktop and re-run the installation.
When starting the Policy
Server, nothing seems
to happen
Check the Monitor/video setting and ensure the system is configured for 256 colors or higher and
screen area 800 x 600 or higher. Some default windows video drivers do not meet these specifications
so you may need to install new video driver.
Unable to start or stop the
Policy Server
Remove or stop MySql before installing EFW. After EFW is installed, you should not run a stand-alone
copy of MySql.
Cannot tell whether a NIC has
EFW installed
To determine whether EFW has been installed on a NIC, see “Determining Whether EFW is Installed
on a NIC” on page 44.
EFW NIC is inoperable after
installing diagnostics
Installing the standard 3Com system diagnostics after installing EFW on a NIC makes the NIC
inoperable. For instructions on restoring the NIC, see “Maintaining EFW NICs” on page 42, and then
follow the steps below.
1
To gain diagnostic capability on an EFW NIC once the NIC is operational again, uninstall EFW from
this NIC (see “Uninstalling EFW” on page 23).
2
Install the diagnostics.
3
Re-install EFW on this NIC.
NOTE:
If you have diagnostics installed on the NIC before you install EFW, you retain the diagnostics
capability after the EFW installation.
You applied a keying diskette
to a different NIC than the one
for which it was created
Below are the results you expect and recommended actions for different situations. Decide on the
case that applies to you and take the recommended action. In all cases, do not abort the keying
diskette operation, simply allow it to complete and then boot into Windows.
■
Case 1:
NIC status: NIC to which you applied the keying diskette was not manually registered at the time
you rebooted into Windows after applying the diskette.
Expected operation: This NIC automatically registers with the policy server.
Recommended action: If you do not want this NIC to be part of this EFW domain, you should
delete it from the Management Console. If you do want this NIC to be part of this EFW domain,
you may simply move it to the Device Set you want it in, and use the keying diskette again on the
correct NIC. Both NICs start with the same keying information, so reusing keying diskettes in this
way is not recommended as a normal mode of operation. However, since keys are changed
immediately upon first contact with the Policy Server, it is not a significant security risk as an
exceptional case.
■
Case 2:
NIC status: NIC to which you applied the keying diskette was manually registered at the time you
applied it, but you had not created a keying diskette for it
Expected operation: The NIC makes first contact with the Policy Server and you see its record in
the Policy Server updated to show it's security status as “Registered-Secured.”
Recommended action: Since you intended to have this NIC in your domain, you can leave it as is.
You may then simply use the same keying diskette again on the correct NIC.
■
Case 3:
NIC status: NIC to which you unintentionally applied the keying diskette was manually registered
at the time you applied it, and you had created a keying diskette for it.
Expected operation: The NIC may or may not successfully make first contact with the Policy
Server.
Recommended action: If the NIC did not make first contact with the Policy Server, delete the
manually registered copy of this NIC from the console. After you have done this, then the NIC
should automatically register, as you are now in the first case above. You now no longer need the
keying diskette that was made for this NIC. You can reuse the keying diskette for the intended
NIC as noted under case 1.
