Re: Failed to detect ISA Server 2006 in FWC
- From: "Phillip Windell" <philwindell@xxxxxxxxxxx>
- Date: Thu, 3 Apr 2008 15:34:30 -0500
The one best to help you with this in the Public Groups is probably Jim
Harrison. I haven't seen him for a few days, but I'm sure he'll be back
around.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"dfosbenner [MCSE]" <dave@xxxxxxxxxx> wrote in message
news:DAA0B11D-77D5-46BD-BECF-9B3DD12022F7@xxxxxxxxxxxxxxxx
This is a real stumper, I've blown 2 days on it so far.
I have two ISA servers, OLD is ISA 2004, NEW is ISA 2006. NEW will
replace
old. NEW is ready to go live, I am doing some final testing, and have run
into a problem with Firewall Client configuration.
FWC Auto Discovery in one subnet is configuring users to use OLD ISA
instead
of NEW. There are three subnets. Subnet A & B are both in DOMAIN1, same
domain as both ISA servers. Subnet C is in DOMAIN2. All subnets use the
same ISA server to get to the internet.
Subnets A & B in DOMAIN1 automatically detect the new ISA server NEW. I
am
using WPAD in both DNS and DHCP to point to NEW. In Subnet C, however,
when
I click Detect Now in the Firewall Client, it still points to OLD.
Auto Discovery is turned on for both ISA Servers right now. If I go to
Configuration, Networks, Internal, Auto Discovery tab, and I uncheck the
box
"Publish automatic discovery information for this network" on OLD, and
then I
retry the Detect Now, I get "Failed to detect ISA Server" on SubnetC.
All name resolution of WPAD in Subnet C points to NEW, and I cannot figure
out how the Discovery is still pointing them to OLD !!!
To summarize so far - Subnets A & B in DOMAIN1 are finding NEW, but Subnet
C
in DOMAIN2 won't find NEW.
In Subnet C, I can "ping wpad", and it gets replies from NEW, so I know
the
WPAD is setup. Also, in the Firewall Client, I can enter NEW in the
"Manually specified ISA Server", and click Test, and it finds it. I have
been through DHCP, DNS, & WINS on all subnets multiple times.
So my issue is, why can't clients on Subnet C automatically find NEW?
--
David Fosbenner
MCSE NT/2000/2003
.
- References:
- Failed to detect ISA Server 2006 in FWC
- From: dfosbenner [MCSE]
- Failed to detect ISA Server 2006 in FWC
- Prev by Date: Failed to detect ISA Server 2006 in FWC
- Next by Date: EventID 21284
- Previous by thread: Failed to detect ISA Server 2006 in FWC
- Next by thread: RE: Failed to detect ISA Server 2006 in FWC
- Index(es):
Relevant Pages
|
