Re: XP x64 Client won't connect to domain with ISA client installe

Disable the RPC Filter until you're joined to the domain. And if worse comes to worse, give your XP x64 client a DHCP reservation, and then create a custom ISA rule for that client IP address.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Stuart" <Stuart@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:3F4C99FC-4083-4D3C-BE39-71910C4882D5@xxxxxxxxxxxxxxxx
I just got around to installing ISA server 2004 w/SP2. That did not change
my symtoms at all. I still can't get on the domain with the 64bit ISA client
installed on my XP x64 Pro client. Does anyone have an idea??

"Stuart" wrote:


Thanks for the replies guys.
Chris, that is the version of the client that I have.
Charlie, I've got ISA Server 3.0.1200.365 SP2. Which I think is ISA 2000?
The client software claims compatability with ISA 2000. Is that not really
the case?

Thanks,
Stuart

"Charlie Russel - MVP" wrote:

> You don't specify which version of ISA server you are running. But if > you
> are at less than ISA 2k4 SP2, you need to update to it.
>
>
> -- > Charlie.
> http://msmvps.com/xperts64
>
>
> "Stuart" <Stuart@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:C334031D-1A27-462D-B2D3-9462023DAC4D@xxxxxxxxxxxxxxxx
> >I have a new client computer with XP x64 installed. I tracked down > >the 64
> > bit isa client and installed it. It works until I reboot the client > > and
> > then
> > I can't get it to connect to the domain.
> >
> > I get event ID 5719, Source NETLOGON, on the client
> > ------------------------------------------------------------------------------
> > "This computer was not able to set up a secure session with a domain
> > controller in domain PES due to the following:
> > There are currently no logon servers available to service the logon
> > request.
> > This may lead to authentication problems. Make sure that this > > computer is
> > connected to the network. If the problem persists, please contact > > your
> > domain
> > administrator."
> > ----------------------------------------------------------------------------------
> > I can then unistall the client and get back on the domain at next > > boot.
> >
> > Any ideas????
> >
> > Thanks
> > Stuart
>

.

Relevant Pages

  • Re: Outbound VPN
    ... Your SBS client cannot establish PPTP VPN through ISA 2004. ... Chapter 6: ISA Server 2004 VPN Deployment Kit: Configuring the ISA Server ... 2004 Firewall for Outbound PPTP and L2TP/IPSec Access ...
    (microsoft.public.windows.server.sbs)
  • Re: Problems access certain web site
    ... Please temporarily place a client computer directly connected to the ... Open the ISA Server Management, right click the ISA Server Name, and ... and then point to Monitoring Configuration | Logs ...
    (microsoft.public.windows.server.sbs)
  • RE: Web proxy returns Error code 502 (12202)
    ... Please open the ISA management console, navigate to Firewall Policy, click ... Microsoft ISA Server together with client certificate authentication: ... An ISA Server 2006 Web Proxy client receives error code 502 when a user ...
    (microsoft.public.isa)
  • Re: Firewall client not working but its session is visible in ISA-
    ... Most likely at a certain point, I rebooted the ISA or restarted the ... It's true I do not use the full capacity of the ISA server, ... if I re-enable the client I can "see" the internet again. ... at the session logs on the ISA server it reads "Firewall client" if the FW ...
    (microsoft.public.isa.clients)
  • RE: client install
    ... To make sure that all client computers will automatically discover ISA ... If you mean that the "Automatically detect ISA Server" is not working, ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.isa)
Loading