Welcome to ISAserver.org

WinXP and ISA FWC hang on next day reboot

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 Firewall] >> Firewall Client >> WinXP and ISA FWC hang on next day reboot

Page: [1]

Message

<< Older Topic Newer Topic >>

WinXP and ISA FWC hang on next day reboot - 8.Sep.2004 6:11:00 AM

Guest

I have a network with Win2000 SP4 domain and ISA 2000 Server SP2 in Indegrated Mode. The clients are WinXP SP1. The clients obtain the IPs via DHCP.

After FWC installation on any WinXP computer he follow problem arises:

1) Just after FWC installation all work fine.
2) On next day reboot the WinXP computer is loading VERY long. It seems as "NO DNS available" scenario. If I disable FWC - the loading is fine again. If I enable the FWC AFTER loading - all work fine.
-----------
The question: what can I do to provide smooth WinXP loading?
----------
PS: The Win2000 clients with FWC are working fine at the same network.

Post #: 1

Featured Links*

RE: WinXP and ISA FWC hang on next day reboot - 9.Oct.2004 9:22:00 AM

Guest

nO IDEAS?

(in reply to Guest)

Post #: 2

RE: WinXP and ISA FWC hang on next day reboot - 10.Oct.2004 2:22:00 PM

spouseele

Posts: 12782
Joined: 1.Jun.2001
From: Belgium
Status: offline

Hi aleks2,

make sure you run ISA SP2 and you re-install the Firewall client from the ISA share.

HTH,
Stefaan

(in reply to Guest)

Post #: 3

RE: WinXP and ISA FWC hang on next day reboot - 11.Oct.2004 12:38:00 PM

Guest

>>make sure you run ISA SP2
Surely

>>and you re-install the Firewall client from the ISA share.
Have been done. Twice...
-----------
No result.

Addition:
If the ISA IP is used instead of ISA FQDN - all is fine. And at next day reboot is fine too...

(in reply to Guest)

Post #: 4

RE: WinXP and ISA FWC hang on next day reboot - 11.Oct.2004 8:05:00 PM

spouseele

Posts: 12782
Joined: 1.Jun.2001
From: Belgium
Status: offline

Hi aleks2,

... then you should investigate your name resolution. I suggest you take a Sniffer or Ethereal trace of the client startup sequence to find out what is really happening on the wire.

HTH,
Stefaan

(in reply to Guest)

Post #: 5