Boot Process Stuck; Global Performances; Single Client Running Slowly; Number Of Sectors Per Read/Write Request - Neoware e140 - Thin Client User Manual

Troubleshooting

Boot Process Stuck

Global Performances

Single Client
Running Slowly
Number of Sectors
Per Read/Write
Request
362 Global Performances
This problem is usually related to the Neoware Image Manager
Client component not being able to communicate with the Neoware
Image Manager server module. This can happen, for example, if the
server module is not actually running or if client drivers are using
NVD protocol v1 when the server module is using NVD protocol v2.
Make sure that the
mPXELdr.BIN
sending out comes from the same software package as your NVDD
server software.
This problem can also occur if the server is using a Gigabit Ethernet
adapter connected to a Gigabit Ethernet switch and the clients are
using 100MB/s Ethernet adapters. In order to correct this issue the
user should enable flow control on each Ethernet adapter and on the
switches as well (if available).
Depending on hardware and drivers, it has been reported that some-
times, the server and client NICs have problems talking together at
the speed rate required by Neoware Image Manager system, result-
ing in a lot of packets being lost.
To try to solve this problem you can decrease the maximum number
of sectors that a Neoware Image Manager client can request to read
or write in a single request. This is described in the next section.
The maximum number of sectors per read or write request is set
using an client driver parameter. By default, the maximum
NVD.SYS
number is 128. When reducing this parameter, the performances
may get better.
This parameter is handled by the following registry value in the cli-
ent registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Ser-
vices\NVD\sector_per_request
file that your TFTP servers are