Afar NX-2E1, Руководство оператора

Страница: 73 / 75

C-5
F5 - Reverse/Restore screen settings. Initially the screen displays white letters on black
background, but you can reverse it to black letters on a white background.
F6 - Increases the console window buffer. This introduces a side bar which enables the user to scroll
up and down. Available in Windows NT Only.
Troubleshooting & Updates
Common problems
1. Failed to open adapter
This usually happens when you haven't installed properly the WinPCap library, or you have
and older version of it. Please visit
http://netgroup-serv.polito.it/winpcap/ to get the latest
version. You should also make sure that your Ethernet adapters are working properly.
2. Cannot find gateway(s) even though they are running properly
Make sure that:
•
The ethernet cables are OK
•
You are getting connected to the right network segment (i.e. try all ethernet adapters)
•
You are using the right MAC address. The system tries to identify the adapter physical address
through some NetBIOS calls in the Win9X case, or some NDIS queries in the
WinNT/Win2000 case. If NetBIOS is not installed, the econ will probably use the wrong local
host MAC address. Also if there are more than one Ethernet adapter installed with the same
name, this might cause problem in the WinNT case.
Resolution: Use the command line argument to specify the correct physical local address. You
can see all the local physical address by executing the
ipconfig -all command. Example:
>econ -m 00:78:24:22:BA:4F
3. Find a gateway but not getting connected
Check if the maximum number of sessions has been reached. The maximum number of
sessions on the server side is limited to four, therefore you should NOT connect to the same
gateway multiple times if not absolutely necessary. When the number of sessions reaches the
limit the gateway will ignore any new discovery messages.
Another reason might be a unreliable RF link causing a high packet loss. Since during the
discovery phase there isn't any retransmission mechanism, it is quite possible that you
managed to "see" the gateway, but you weren't able to connect to it, because the connection
request packet was lost. In such case, try to connect again.