Welcome to ISAserver.org

Roaming ISA Client

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Web Proxy] >> Web Proxy Client >> Roaming ISA Client

Page: [1]

Message

<< Older Topic Newer Topic >>

Roaming ISA Client - 11.Jan.2008 9:33:51 AM

sullivac

Posts: 23
Joined: 29.Jun.2005
From: Boston
Status: offline

Hi -

I figure this should be an easy one since it would be a fairly common scenario......

ISA 2006 on LAN where root W2K3 AD domain is located.
ISA 2006 at branch office where child domain is located.
L2TP VPN tunnel between the two ISA servers.
Each location has its own DNS servers authoritative for its own domain.
The child domain DNS server forwards to the parent domain DNS.
Each domain's DNS has a WPAD record appropriate for the local ISA.

Clients have 2006 version of the FW Client installed, including a few Vista machines with the newest version, which works with that OS. All of these clients are able to access resources across the VPN tunnel on the remote domain/network.

The problem: A laptop Web Proxy client visits the remote location and is unable to access sites on the Internet. I hoped that the FWC on a laptop that belongs to domain A would auto-configure for the ISA server on the domain B LAN. Instead it seems that the FWC becomes inactive. Even if I manually enter the name for the local ISA server, I can't access Web sites, from what I can recall.

Is there an article someone could point me to that addresses this scenario? Am I missing something important? Let me know if more information is needed.

Thanks.

Post #: 1

Featured Links*

RE: Roaming ISA Client - 13.Jan.2008 12:17:47 AM

sullivac

Posts: 23
Joined: 29.Jun.2005
From: Boston
Status: offline

I should have posted this when I was on the remote network to better report the problem....
As it turns out, the "visiting laptop" can access the Internet, but the browsers are very slow. They are using the local ISA to access the Internet, but when they attempt to resolve WPAD via DNS, they append their own DNS suffix, which of course points them to the wrong ISA when on that remote network.

For this reason, I'm wondering if using DHCP instead of DNS for WPAD would solve the problem.

(in reply to sullivac)

Post #: 2