beautypg.com

Troubleshooting portal, Symptom, Analysis – H3C Technologies H3C SecPath F1000-E User Manual

Page 42: Solution, Incorrect server port number on the access device

background image

41

ACL:NONE

Work-mode:stand-alone

VPN instance:vpn1

MAC IP Vlan Interface

----------------------------------------------------------------------------

000d-88f7-c268 3.3.0.1 0 GigabitEthernet0/1

Total 1 user(s) matched, 1 listed.

Troubleshooting Portal

Inconsistent Keys on the Access Device and the Portal Server

Symptom

When a user is forced to access the portal server, the portal server displays neither the portal

authentication page nor any error message. What the user sees is a blank web page.

Analysis

The keys configured on the access device and the portal server are inconsistent, causing CHAP message
exchange failure. As a result, the portal server does not display the authentication page.

Solution

Use the display portal server command to display the key for the portal server on the access

device and view the key for the access device on the portal server.

Use the portal server command to modify the key on the access device or modify the key for the
access device on the portal server to ensure that the keys are consistent.

Incorrect Server Port Number on the Access Device

Symptom

After a user passes the portal authentication, you cannot force the user to log off by executing the portal
delete-user
command on the access device, but the user can log off by using the disconnect attribute

on the authentication client.

Analysis

When you execute the portal delete-user command on the access device to force the user to log off,

the access device actively sends a REQ_LOGOUT message to the portal server. The default listening port

of the portal server is 50100. However, if the listening port configured on the access device is not 50100,

the destination port of the REQ_LOGOUT message is not the actual listening port on the server. Thus, the
portal server cannot receive the REQ_LOGOUT message. As a result, you cannot force the user to log off

the portal server.
When the user uses the disconnect attribute on the client to log off, the portal server actively sends a

REQ_LOGOUT message to the access device. The source port is 50100 and the destination port of the
ACK_LOGOUT message from the access device is the source port of the REQ_LOGOUT message so that

the portal server can receive the ACK_LOGOUT message correctly, no matter whether the listening port

is configured on the access device. Therefore, the user can log off the portal server.