Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
Community Member

VPN Concentrator 3005 Issue

While connected thru vpn client 5.0 with any of the profiles configured on this concentrator box we are not able to connect to our sharepoint server on port 80.

Server works fine with LAN Connections. If configured with 88 or anyother port for the application, the connections works fine with the VPN. The problem occurs only with port 80.

I am able to reach the server on port 80, but somehow my return traffic is not coming back..Pls fine the output of my request.

H:\>wget sharepoint

--12:17:15-- http://sharepoint/

=> `index.html'

Resolving sharepoint...

Connecting to sharepoint||:80... connected.

HTTP request sent, awaiting response... Read error (Connection reset by peer) in



--12:17:25-- http://sharepoint/

(try: 2) => `index.html'

Connecting to sharepoint||:80... connected.

HTTP request sent, awaiting response... ^C


Connection path:-

C:\>pathping sharepoint

Tracing route to sharepoint[]

over a maximum of 30 hops:

0 host




Computing statistics for 75 seconds...


We dont have any Client FW Config/Access Restrictions on any of the ports. FYI. With the VPN Connection, we are able to access our other http servers without any issues. It happens only with this specific sharepoint server and that too it started happening from last night (we didnt have any changes)..

Cisco Employee

Re: VPN Concentrator 3005 Issue

Hello Raja,

Are you using IPSec over UDP or IPsec over TCP?

If using IPSec over TCP- What port are you using?

Do you see any kind of errors on the VPN concentrator when you try to access the sharepoint through port 80?

Is there any filter applied to the VPN group that the user is connecting with?

Did you take a sniffer trace on the sharepoint server itself to see if the packets reach the sharepoint server and there is a return packet to the client.?



Community Member

Re: VPN Concentrator 3005 Issue

Hello Gilbert,

IPSEC over UDP. Filters checked..After sniffing the packets from the Sharepoint server we found that it is the problem with the load balancer which is in between the concentrator and the Server. If we bypass the Loadbalancer, the connection gets trhu..strange..not sure why loadbalancer handles the traffic only for that source, that port (http) with issues.

CreatePlease to create content