Re: Firewall client
From: Jim Harrison [MSFT] (jmharr_at_online.microsoft.com)
Date: 12/24/04
- Next message: Jim Harrison [MSFT]: "Re: FTP dir-list problems by using Firewall Client ISA 2000"
- Previous message: Jim Harrison [MSFT]: "Re: Proxy 2.0 Autoconfig Issue"
- In reply to: Phil Cook: "Firewall client"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 24 Dec 2004 09:32:37 -0800
Most likely, it's a name resolution issue.
You can determine this with the following commands:
(try to resolve the ISA name)
ping isaserver -n 1
..if this succeeds, the client can resolve the ISA name. If not, fix this first
(try to resolve the automatic discovery entry in DNS/WINS)
ping wpad -n 1
..if this succeeds, the client can resolve the automatic discovery name. If not, add a "wpad" record to your DNS / WINS
-- Jim Harrison [ISASE] Read the help, books and articles! This posting is provided "AS IS" with no warranties, and confers no rights. "Phil Cook" <philcNOSPAM@grainsystems.com> wrote in message news:9b19r0d4qnfbvctkjrkfua7hfj4mga9agj@4ax.com... I have a site to site vpn set up using pptp. I cannot get the 2004 firewall client to run on the machines at the remote site and connect to the 2004 isa server even though I have a rule allowing all traffic between the remote and the local office. Anyone have an idea why this is not working or what I could look for?
- Next message: Jim Harrison [MSFT]: "Re: FTP dir-list problems by using Firewall Client ISA 2000"
- Previous message: Jim Harrison [MSFT]: "Re: Proxy 2.0 Autoconfig Issue"
- In reply to: Phil Cook: "Firewall client"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading