Publication Date: 2019-07-18 | Views: 1422 | Downloads: 0 | Author: anliku | Document ID: EKB1000004559
In the networking of Figure 1 or Figure 2, the Web-based Network Management System (NMS) cannot be accessed.
As shown in Figure 1, the is connected to the PC through the LAN to establish the local configuration environment.
As shown in Figure 2, the remote PC serving as the client is connected to the through the WAN to establish the remote configuration environment.
Ping the IP address of the Web-based NMS to be accessed on the PC. If the Web-based NMS cannot be pinged through, it indicates that there is no reachable route. In this case, check the setting of the IP address of the local PC or the interface on the .
If there is no IP address in the information that is displayed, enable the Web-based NMS and bind the Web-based NMS to an IP address.
Run the telnet ip-address service-port command on the SVN3000 to check whether the port is enabled on the device between the PC and the SVN3000. If connections can be established, it indicates that the port on the device between the PC and the SVN3000 is enabled. Otherwise, enable the port on the device between the PC and the SVN3000.
Parameter ip-address indicates the IP address of the device between the PC and the SVN3000.
Parameter service-port indicates the port number that the Web-based NMS uses.
Cause one: There is no reachable route.
Cause two: The Web-based NMS is not bound to an IP address or the port number is incorrect.
Cause three: The devices between the PC and the SVN3000, such as border firewalls, disable the port of the Web-based NMS.