135
DHCP/BOOTP Problems
DHCP/BOOTP Problems
Messages:
host name too long
or
filename too long.
z
The Terminal Server can only accept host names of 14 characters or file names of 64 characters,
so verify that you are not attempting to pass a string that is longer than those maximums.
DHCP or BOOTP have been set up to configure my Terminal Server, but does not seem to have
done anything.
z
Check that the server DHCP/BOOTP service is set to on, if not set it to on and reboot.
z
Check that your BOOTP server is configured for your Terminal Server or that your DHCP server
has an active lease pool (scope) with at least 1 free IP address.
You observe TFTP errors when the Terminal Server boots, for example:
TFTP: File not found : filename
TFTP: Timed out
This has a number of causes, including:
z
The file names you specified to DHCP/BOOTP do not exist or are in the wrong place.
z
The server for any of the downloadable files in your bootfile has no TFTP server running.
z
Verify that lease data in your DHCP server manager is correct.
z
Reset or restart the DHCP server.
Language Problems
In a customised language, the text strings appear in the wrong place in the Menu, CLI, or
WebManager.
z
Check the original ASCII text file you used to translate to your customised language. The
sequence of the line much match exactly (be aware that comments don’t affect line sequence, but
can affect the actual line that the strings appear on). So, if you strip out all comments, if the
original file says line 1000 should be string
none
, then line 1000 (stripped of comments) should
be the translated version of
none
.
Long Reboot Cycle
Rebooting the Terminal Server takes a long time.
If you are not using DHCP/BOOTP, disable this within the Server Services; otherwise, the Terminal
Server waits to timeout for a request to DHCP/BOOTP.
