..and years of satellite service means - what - exactly? I've met plenty of folks with "lots of years of <pick a subject> behind me" - none of which prepares them for the current effort. I've been trying to offer you support, but it's been like chasing a caffeine-powered three-year-old around the back yard. The problem you originally related deals with intra-array authentication and you've been all over NLB, file permissions, NICs and FSM knows what else. If this is indicative of your troubleshooting techniques during your years in the satellite business, it bodes ill for the remaining process. We'll break it down into steps: 1. Log on to your problematic ISA Server using an account which has local administrator privileges 2. Start | Run | cmd 3. Type 'Cd "%ProgramFiles%\microsoft isabpa"' (use the double-quotes since the path has spaces) 4. Type 'isabpapack +repro' (no quotes) 5. Follow the instructions 6. Respond with a link to the resulting data Note: Do NOT clear out your event logs prior to running this utility; there is important data that can help solve this issue. From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Bogdan Florin Sent: Tuesday, February 13, 2007 9:11 AM To: isalist@xxxxxxxxxxxxx Subject: [isalist] Re: ISA Intra Array Authentification Dear Jim, I have years of satellite business in my back, if you can offer me support kindly I appreciate but if you have intentions to disconsider my knowledge please don't do it. I follow your exact steps as below. I realize that there is a bit of a language barrier here and this is why I'm trying to be patient, but you just don't want to follow instructions. Do this (special attention to 3-4): 1. Get ISABPA from MS downloads B> I download it ! 2. Extract it to the ISA where the events are found B> I install the program on PROXY2 ISA 3. Read the instructions which cover operating ISABPAPack in repro mode B> I read nothing, I only install and RUN selecting all tests. 4. Follow those instructions B> I wait till test complete. 5. Respond with a link to the data that was created on the desktop B> here you have a new link after I fix the MTU problem. http://web.bizarnet.ro/IsaBPA.scan2.200702131837570206.data.htm For each issue reported by ISABPA, there is a recommended solution. The error: the upstream chanining credentials alrt was signaled 1 time. Events that triger the alert: ISA Server can not connect to 192.168.254.1 (proxy1) because the server require authentification either for chaining or for intra array authentification. However authentification failed because the specified credentials was incorect. Check authentification credentials and try again. Than I click at your recomandation on "tell me more about this issue and how to solve it" and than a Help page opwn and this guide me to open the Alert panel and look at it. I done this long time ago .. and not solve anything. Follow those steps outlined in each problem report, or if you don't care about that particular issue, ignore it. B> I care very much to see the Array working and I do not understand yet why it is not working using the Computer account. I do not know if it is importange but both ISA Web proxy logs into a local SQL database (each Isa have his own SQL installed) wich a further transferred periodicaly to a masterserver who analize the traffic. I belive this have nothing to do with the Intra Array authentification. For instance, if the connectivity verifier alert is due to you cycling the test server, you can ignore it. You *do* need to fix the MTU issue. B> in this positive spirit please be kind and guide me furhter since personaly I have no ideea what is going on. May be I shuld setup ISA services to work on the behalf of some domain account not local system like now ? All mail to and from this domain is GFI-scanned.