I seen a number of posts on this, and followed a few support docs on this matter, but I'm utterly stuck now, nothing seems to be working for me.
It's the usual scenario, I've got a windows 2003 VPN server sat on the private lan of our ASA 5510 firewall, and I'm trying to get my Windows XP / 7 laptops to connect to it.
Within the ASDM:
1) Created Public Server for protocol 1723
2) Created Public Server for protocol GRE
3) Both public servers created have the same public and private addresses
4) The above created the Static Route from Public to Private in the NAT section of the firewall config
5) The above also created 2 firewall rules on the outside interface for both 1723 and GRE
When trying to connect I get the following entry in the debug log.
6 Aug 06 2010 17:09:37 302013 220.127.116.11 1045 ChamberVPN-Internal 1723 Built inbound TCP connection 1889195 for outside:18.104.22.168/1045 (22.214.171.124/1045) to inside:ChamberVPN-Internal/1723 (XXX.XXX.XXX.XXX/1723)
but nothing further.
The server doesn't show any attempt at a connection so I'm guessing I'm missing something on the firewall now.
Also on the inside interface there is a temp rule:
This should allow any outbound traffic as far as I'm aware..
Any help would be greatly appreciated.
Asa logs shows that connection is ended because of "syn timeout". That means asa doesn't get any response from the Windows Server. In that point we need to clarify some points.
1 - Does your vpn server have correct default gateway or route which is inside interface of your asa fw.
2 - Is it possible to start packet capture on Windows Server. By this we can get data flow information beetween client and server. And we can be sure that Windows Server is getting vpn request.