3<B3@>@7A3
Appendix B: Troubleshooting a Remote Console Connection
No Clients In the Console
The following are some common reasons why clients fail to appear in the console.
1. Windows XP clients may have the XP firewall turned on.
With SP1, the firewall must be turned off. With SP2, either the firewall must be turned off or the ports
being used must be added to the
Exceptions
tab. Deep Freeze requires both TCP and UDP protocols;
therefore, one exception should be added for each.
2. The console and clients do not contain the correct network settings.
If the console is set up to run under port 7725 and the clients are using port 7724, they will not be able
to see each other. Also, if the workstations are configured for LAN/WAN, the IP must be equal to the
IP of the machine where the console is running.
3. Something on the network is blocking the port used between the console and the
clients.
If a server, router, or switch on the network is not allowing the port to get through, the clients will not
be seen. By default, 7725 is the port being used.
4. The workstations are configured to run under LAN settings but the console exists on a
different subnet.
The default LAN setup works as long as all the machines running the workstation and console exist
on the same subnet. However, if a VLAN is being run, or if there are several subnets where the clients
exist, the workstation install must be configured to run under the LAN/WAN settings.
5. The workstations were created under a different customization code than the
console.
When the Deep Freeze Configuration Administrator is first run, a prompt for a
Customization Code
appears. This code is very important as it encrypts the software. This means that any workstations created
are encrypted with this customization code. If a console was created using another administrator that
was installed with a different customization code, it cannot see workstations created under the original
code. The workstations and console must be created under a configuration administrator installed
using the same exact customization code.
6. The network usage is quite high and may be preventing packets from getting through
to the console.
The clients send a packet to the console every 30 seconds. The console also broadcasts to the clients to
let them know it is listening. If a packet does not get through, the client is not reported to the console.
Using a Server Service helps resolve these types of issues.
7. The client has no route to the host.
Something is blocking communication or the machines are not physically connected. The clients are
unable to send packets to the Console/Remote Console because there does not seem to be a route to
the host. Attempting to ping the IP of the console/Remote Console does not seem to work. To resolve
this issue, make sure the two machines can connect to each other.
