Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
HelloI think we have a problem getting traffic in the VPN tunnel routed across the ISA Server, but I'm stuck. Can you help please?The VPN Client3.5 makes a secure tunnel over the Internet with PIX506 (v.6.01) using Cisco VPN, and can ping the server ...
I use VPNClient3.0.1 to access PIX506 v6.0(1). I believe there are newer versions of these: what benefits would we gain by upgrading?If there are benefits, where do I obtain the upgrades?ThanksMichael
I can set up a VPN from Cisco VPNClient3.0 to PIX506 v6.0(1) and then telnet to a UNIX host on 192.0.0.128, but I cannot get a logon dialog to the WindowsNT Server on 192.0.0.65. The UNIX, NT Server, and PIX inside interface are all on the same LAN 1...
My VPN client 3.0.1 does not even connect to the PIX506 v6.0(1) at Phase 1. The client log shows:SENDING>>>ISAKMP OAK AG(SA, KE, NON, ID, VID, VID, VID) to 193.130.x.y (i.e. PIX outside)It tries 3 retransmissions, then says:Exceeded 3 IKE SA negotiat...
Reading these messages it seems that there are things that don't work yet. Is it possible for a VPNClient3 to get to a network protected with a PIX506 v6.0(1), with a Cisco2501 router between the PIX and the ISP's Kilostream line?Protocols 50 and 51...
Many thanks, but I can't find anything about PAT in the ISA Server. It does talk about server publishing to make internal servers available to outside: maybe I need to look at that!RegardsMichael
Its not "File Sharing" I changed, but "Client for Microsoft Networks". File sharing is to allow access to your client. I needed to allow my client to act as a client to a Microsoft Server. You probably must have networking installed to get the Client...
Ah-ha! I've just partially fixed it. The connectoid to the ISP did not have the Client for Microsoft Networking enabled (well you wouldn't normally want this to get to the Internet, so it is not enabled by default). Anyway, once enabled I get a logon...
When connected on the LAN it all works well. I can connect by name or IPaddress and get a logon dialog, and ping works with either. When connected through VPN I cannot connect with either ip or name ("The network path was not found"), but ping by IPa...
The client is Win2000Pro. It does have network access to the NT Server, and will give me the logon prompt with \\\ when accessing over the LAN. However, when using VPN (from home) I do not have LAN cable connected. The VPN works, I can ping the serve...
