Welcome to ISAserver.org
Forums |
Register |
Login |
My Profile |
Inbox |
RSS
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Strange Integrated Auth Issues...
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login | |
|
Strange Integrated Auth Issues... - 18.Jul.2005 11:23:00 AM
|
|
|
Cov
Posts: 22
Joined: 18.Jul.2005
From: UK
Status: offline
|
Hi All,
I'm having a pretty strange problem happening here.
My setup is as follows:
Win2003 Standard SP1, ISA 2004 Standard SP1, Surfcontrol 5 (All updates).
I have 1 external interface and 1 internal interface, and roughly 50 users connecting to the ISA server for web access as SecureNAT clients.
Everything works correctly when I set the authentication to not required on the internal network, and the HTTP/Etc protocol to allow all users.
Now when I set it the authentication to Integrated and required on the internal network, and set the protocol filter to "ISA Users" (A security group I set up in the AD which includes all users who require internet access), it works for maybe 10 minutes, then boom, it dies.
I can see the user names in the Monitoring/sessions, Surfcontrol correctly filters based on user name, and so on. And then it just stops.
You can enter ANY user name/password combination (domain\username, user@work etc) and it just asks for it again.
In the event logs on the ISA Server I see all of the connection attempts as Logon/Logoff errors (event ID 537). A sample:
Logon Failure: Reason: An error occurred during logon User Name: Blah Domain: (my domain) Logon Type: 3 Logon Process: NtLmSsp Authentication Package: NTLM Workstation Name: Blah Status Code: 0xC000005E Substatus Code: 0x0
If I switch the authentication off again then access works for everyone, until I turn it on and then it works for 10 minutes and dies again.
I checked up the status code, and tried setting the ISA server to "Trusted for delegation" in the AD, but it still failed after a while.
I attempted to use RADIUS for the authentication, however it does not seem to work correctly/at all? It does work for VPN clients.
Soooo... what do I try now? Is this a hardware issue possibly, or something wrong with the way I have set up the ISA server?
IĈm really stumped, and appreciate any help/suggestions.
Thanks!  [ July 18, 2005, 11:24 AM: Message edited by: Cov ]
|
|
|
|
RE: Strange Integrated Auth Issues... - 18.Jul.2005 11:36:00 AM
|
|
|
isawader
Posts: 420
Joined: 27.Apr.2005
Status: offline
|
I would suggest that you unchceck "require authentication" for the Internal Network and keep the integrated. Install firewall client on all workstations and configure browsers as webproxy (set them to use HTTP/1.1 for proxy). Remove the "All Users" on the Access rule allowing HTTP/HTTPS and add user group needing web access.
|
|
|
|
RE: Strange Integrated Auth Issues... - 18.Jul.2005 11:39:00 AM
|
|
|
isawader
Posts: 420
Joined: 27.Apr.2005
Status: offline
|
Oops! forgot you have surfcontrol. Since I primarly use ISA to control all of our outbound access, I don't use surfcontrol.
|
|
|
|
RE: Strange Integrated Auth Issues... - 18.Jul.2005 12:49:00 PM
|
|
|
ClintD
Posts: 1833
Joined: 26.Jan.2001
From: Keller, TX
Status: offline
|
0xC000005E (the Status Code) is "STATUS_NO_LOGON_SERVERS"
What DNS Servers do you have configured on the ISA Server's External and Internal interfaces?
|
|
|
|
RE: Strange Integrated Auth Issues... - 18.Jul.2005 1:30:00 PM
|
|
|
ClintD
Posts: 1833
Joined: 26.Jan.2001
From: Keller, TX
Status: offline
|
The problem isn't Kerberos - it's your DNS configuration. Remove any reference to external DNS Servers on your ISA Server and this will be resolved.
Have your internal DNS Server use Root Hints or Forwarders to resolve external names (don't forget the access rule on ISA to allow DNS from the DNS Server to External).
|
|
|
|
RE: Strange Integrated Auth Issues... - 18.Jul.2005 3:26:00 PM
|
|
|
ClintD
Posts: 1833
Joined: 26.Jan.2001
From: Keller, TX
Status: offline
|
It depends on how you had ISA setup for Access Rules on your old install. I would say you were just living on borrowed time on your ISA 2000 install. This is the way that I've always configured ISA and is the way Tom suggests as well.
The problem is the DNS Client service of Windows which ISA utilizes in addition to it's own cache.
The DNS Client service will prioritize DNS Server based on the response time and number of responses it receives for queries. So in your scenario, your Internal DNS Server was being used initially, but after a period of time, the ISA Server wouild send queries for external names to your ISPs DNS Servers and get a quicker response. The DNS Client service would move that server to the top of the DNS list but at the same time, this would cause queries for your Internal AD DNS namespace to fail.
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|