403 Error on NODE 2 of Network Load Balanced Server Farm
I followed the instructions located at:
http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/default.mspx
to set up two servers in a NLB to host the same content. Both servers have
Sharepoint Services installed and have been set up to use the same
configuration and content databases. The servers are using the same
application pool name and configuration. The web sites use the same IP
address and host header.
Everything works fine on Node 1 but when I try to connect to Node 2 I get a
403 14 error (unable to list directory contents). The SharePoint
administrator console shows that both systems are configured to use the same
content. Not sure of what to look at next...
.
Relevant Pages
- Re: Load balancing strange issue
... I often made a NLB cluster but never had this much problems configuring it. ... I updated the NIC drivers to the newest version today on both servers. ... >> Cluster configuration stabilized. ...
(microsoft.public.windows.server.clustering) - Network Load Balancing Problems
... We actually have the following configuration: ... + 03 Terminal Servers with Windows Server 2003 EE ... We dont have configured the full servers cluster, ... Terminal Server hosts to the NLB cluster. ...
(microsoft.public.windows.server.clustering) - Re: 403 Error on NODE 2 of Network Load Balanced Server Farm
... I followed the instructions under ... Configuring Two Virtual Servers to Host the Same Content ... >> application pool name and configuration. ...
(microsoft.public.sharepoint.windowsservices) - Re: Network Load Balance problem
... What normally happens is that the NLB console doesn't save the host list, witch is different from loosing configuration at NIC level. ... To save this configuration you use NLB console and choose save configuration hosts file. ... only problem is that when i close the NLB manager it is loosing all configuration, and when i reopen it again it says something on unicast etc...my hosts are all set as multicast and NLB protocol is bound on all servers so i dont know exactly what problem is. ...
(microsoft.public.windows.server.active_directory) - There are currently no logon servers available
... I recently added several Windows 2003 servers to my 2000AD. ... joined the domain fine and I can add domain users to resource ACL's however ... it will not resolve however pinging by only the host portion of the name it ... The redir is bound to 1 NetBt transport. ...
(microsoft.public.windows.server.active_directory) |
|
