Installation guide

BlipNet Administrators Guide
74
Problem when connecting to LAN access service in BlipNet
Before going through this procedure please make sure that the correct configuration is used.
Either the “LAN Access”, the “LAN Access and Object Push Server” configuration or another
suitable custom configuration must be used. If the problem remains then the procedure to find
the problem depends on what the problem appears to be from the terminal side.
From the terminal side the following might happen:
1. The terminal cannot find the BlipNode in a device discovery.
2. The terminal cannot make a service search on the BlipNode.
3. The LAN access service is not available after making a service search.
4. The terminal cannot make a PPP connection.
The solutions to the different problems are listed below:
1.
If the terminal cannot find the BlipNode in a device discovery, it can be due to the
following reasons:
a. First make sure that the BlipNode you are trying to connect to is attached to
the BlipServer. It must be shown with black text and a blue BlipNode icon in
the BlipManager configuration view tree.
b. Then make sure that the BlipNode is in discoverability mode. This will be the
case if a proper standard configuration has been used. If a custom
configuration is used, see section Link Establishment - Customize.
2.
The terminal cannot make a service search on the BlipNode.Please check that the
Terminal is not set to "Never" in BlipServer Properties -> Terminals or to "Default" if
"Allow all Terminals to Connect" is de-selected. Also check the specific BlipNode is not
configured with a “BlipNode Disallowed Terminal List”, this might cause the problem.
Please see section BlipNode Properties - Allowed Terminals and section BlipServer
Properties - Terminals. for future details.
3.
The LAN access service is not available after making a service search.
Please make sure that the LAP access record is enabled, see section BlipNode
Services.
4.
The terminal cannot make a PPP connection. On some terminals a PPP connection is
automatically established after establishment of a LAN access session. The BlipNode
will try to retrieve an IP address to the terminal when the terminal tries to connect to
the LAN access service. If the DHCP allocation fails, the terminal will not be able to
make a successful LAN access connection. The DHCP allocation might fail due to the
following reasons:
a. Check if the DHCP allocation has failed due to a lack of IP addresses. Please
see section BlipNode does not connect to the BlipServer, item 4.b.
b. Please check whether the DHCP server supports broadcast or unicast to the
DHCP clients. For more information see the issues of DHCP configurations in
section BlipServer Properties - Advanced.