G
ATEWAY
C
ONTROLLER
S
ERIES
U
SER
M
ANUAL
VALUEPOINT NETWORKS, INC. ALL RIGHTS RESERVED
P
AGE
130
OF
135
As illustrated above, the communication path could be broken at several stages. The
various OS provided network diagnostic tools, such as ping.exe or tracert.exe, can
be employed to find out TCP/IP-related communication problems.
Note: If two NICs are installed and operating on a client com puter, TCP/IP m ay not work
properly due to incorrect entries in the routing table. Use the W indows Device Manager to
disable unnecessary NICs. The m ost comm on configuration that causes this problem is when
the Ethernet and W iFi LAN Cards are both enabled on a laptop at the sam e tim e.
4 . 1 .
T C P / I P
S
E T T I N G S
P
R O B L E M S
If the client is associated, check for client TCP/IP problems
•
The Controller does not respond to ping from the client computer.
o
Disable any unused NICs on the client computer.
o
Is Wireless Client or Layer-two isolation enabled on the Controller, or an
intervening AP?
Disable Isolation features to access local APs or other hardware
on the LAN.
o
Check whether the IP address of the client computer and the IP address
of the AP are in the same IP subnet.
Turn on Auto-IP to allow clients with invalid static IP Addresses
to connect.
Enable DHCP on the Controller and client.
•
The DNS server(s) do not respond to ping from the client computer.
o
Verify that the Controller WAN port is connected to the ISP by checking
the Status page in the Controller Web GUI.
o
Verify that the client is authenticated by the Controller, or that the client
has opened a HTTP Session (using their web browser) if using Automatic
Authentication.
