This is my first post, I usually check this website often for knowledge. I've been using ISA for the past 2 years and really enjoy it, but I am at a loss for the problems which I've recently encountered and was hoping that some of the experts might be able to help.
I have a 3 server ISA 2006 enterprise setup. (1) CSS domain member (2) NLB array members joined to a domain.
Recently I lost one of my Array members. I figured that since everything was backed up in ADAM that all I would need to do is setup the server and rejoin the array. However when ISA setup begins and I point it to the CSS and Array, setup begins and installs and gets to configuring. Then a message pops up telling me that "isa setup failed while writing internal network information to isa server storage" and then rolls back the installation.
I then tried to disable NLB and change the ip of the (1) alive array member to the "virtual ip" so that everyone can continue to utilize the network, at that point the CSS can not connect to the array member (no big deal), I just want to get my dead array member back up and running and then change the ip of the other array member back to the original and then re-enable nlb. I get the same message during isa setup that setup failed writing to the css. I finally changed the live array member intra array ip to the current ip and it is now communicating with the css.
Can anyone please tell me how I can bring back my dead array member? I just want to install a fresh copy of ISA and join the array, and then re enable nlb.
This is the main problem that keeps me stumped. "isa setup failed while writing internal network information to isa server storage"
Tried deleting it and it was a no go. Now I'm to the point where I gave the server a new name, we'll say the original was ISAServer, the new name is ISAServer1, I still can not add it. I am in the process of running Microsoft update, don't know how this would affect installing ISA and having it accepted into the array, but I'm pretty much getting to the end of my ideas on this one.
ok, I have discovered my particular issue. Basically, I have 4 nics in each server, one is for our T1 and the other "3" are each connected to a seperate subnet. When initially configuring the server, all 3 internal nics were part of the internal network. when I tried to enable nlb, it would only allow me to enable it for the entire "internal" network and not each adapter as I would have liked. Therefore I removed all the adapters from the internal network and created a seperate network for each and enabled NLB for each. When installing ISA on the new server, setup would ask me which network was "internal" so I obviouisly picked the "3" networks that are internal, even though in the array they are not part of internal. I took one of the networks "the main one" and moved it into "internal" on the array, when I reran setup on the new server, it did not ask which network to use for internal and setup completed successfully.
I hope this post helps someone else who might run into this same issue.
Now another question, when enabling NLB, do you enable it on just the Internal network?
Posts: 4663
Joined: 30.Jul.2002
From: United Kingdom
Status: offline
You normally enable it on all networks apart from the intra-array network (if you are using one) to ensure you get bi-directional affinity for traffic...
Yes, that much I am aware of, but when you have 3 seperate NICs in the "Internal" network, you can only enable NLB for the entire "Internal" network, not for each adapter. Thats why I created a seperate network for each adapter. This way I could enable NLB for each adapter independently.
My question is, Is it common practice to have multiple NICs in the "Internal' network and to enable NLB on the "Internal" network? If so, do you provide ip's for the additional NICs in the "Additional Virtual IP's" section off the dialog box?