Dear all,
Firstly, please excuse the cross-posting, we have gone live with our new
intranet infrastructure and I am hoping to get answers fast as we have
experienced a bit of a problem!
We are running 2 x Windows 2003 Server (R2), network load balanced, running
application center 2000 (sp2).
Our organisation uses FrontPage to enable our various (and copious)
departments to publish their information to our intranet. We had the same
setup running 2xWindows Server 2000 previously.
Since rolling out the new infrastructure we have noticed that we are unable
to publish via FrontPage to the cluster, the redirects in application center
just dont seem to work, if we change my request in the browser from
"intranet" which is pointing to a virtual ip address (for the nlb) I
continuously get prompted for credentials. If however I enter the server
name (UBHNT145) I can open the site without issue and publish.
Our only thought so far to get this to run is to set up a DNS entry for
"PublishIntranet" which would point specificially to the cluster controller
node (UBHNT145). This would still enable us to have the network load
balancing for "browsing" requests, but obviously means the redirects that
app center is supposed to be doing will simply be over ridden at a DNS
level.
We have applied a hotfix to app center which prior to doing that we were
unable to even see the nodes in app center, other than that its a vanilla
build (obviously all service packs/updates are currently applied).
As I mentioned, this was working quite happily with Windows Server 2000 (we
obviously didnt have the NLB then), so we are only experiencing this problem
since upgrading to the new o/s.
Has anyone else encountered this problem (and resolved it?), or can offer
any suggestions as to where to look at the problem?
Any information would be really appreciated, our organisation has
approximately 100 webmasters all wanting to work on their sites, and at
present we are unable to help them!
Thanks in advance for your time and help,
Regards
Rob Meade
|