No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Can’t access to internal network server after started the network expansion

Publication Date:  2012-11-02 Views:  191 Downloads:  0

Issue Description

Open the SSL VPN authentication interface, and after passed the authentication, in the condition that it has opened network extension service, when starting network expansion it cannot access internal network server. The virtual IP acquired normally.

Alarm Information


Handling Process

1, login SVN3000 gateway, ping internal network server, if can't ping, check whether I internet is accessible at first;
2 login SVN3000 management interface, enter virtual gateway network extended "client routing ways configure" page, if it is manual mode, please make sure the IP address of internal network server or its own segment has been added to the routing network segment list.
3 please check whether the internal network server has the return route to return the network expansion virtual IP address. If it hasn’t, can in internal network server add the static routing point to virtual IP address, or add a default route back to SVN.
4 please check whether SVN3000 has configured the default route. If not, add a default routing point to gateway.
5 if SVN3000 and internal network server are directly connected to the same firewall’s different interface, please make sure the domain packet filter of the domain which the two interfaces located in is opened.

Root Cause

If the configuration is correct, and the client can acquire the internal network’s virtual IP normally, but still can’t access to the internal network, this should be caused by the acquired internal network’s virtual IP has no routing in the network. 


Carefully configure according to the operation instructions, to guarantee the network routing.