For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Steve_85547's avatar
Steve_85547
Icon for Nimbostratus rankNimbostratus
Aug 22, 2008

Sharepoint nightmares

Hello I was just wondering if anyone could take a look at the following symptoms and provide me a suggestion or idea:     1. I have a virtual server serving up a 4-node 2007 Sharepoint clu...
microsoft
partner
Steve_85547's avatar
Steve_85547
Icon for Nimbostratus rankNimbostratus
Oct 06, 2008

Posted By hoolio on 08/26/2008 6:56 AM

 

 

Hi Steve,

 

 

Is the problem with web access or fileshares? Have you been able to capture a tcpdump of a failure? It sounds like there might be some kind of look up being performed on the servers which times out. I've done a few Sharepoint implementations for customers and not seen this issue. We typically use standard VIPs with client SSL, HTTP, OneConnect with a mask of 255.255.255.255, and cookie insert persistence set to ~30min.

 

 

The deployment guide doesn't cover fileshare access. To allow it, you'd need to configure a VIP on port 445 with a TCP profile. This post might also have some related info for fileshare access delays (Click here).

 

 

I'm surprised that F5 Support wasn't able to help you resolve this issue. What was the result of the case?

 

 

For point 2, do you have a persistence profile added to the VIP? Can you try source address to start with and then move to something more complicated if that fixes it?

 

 

Aaron

 

 

 

Aaron,

 

 

Thanks for the reply. It has been a while and I still am having issues. I will look at that other post.

 

 

Here is the latest on my 2 issues:

 

 

1. My VIP for this is an IP (*) VIP allowing all ports and the nodes behind it are also IP (*).

 

 

2. I have made it a little further with this one. I can introdude a 2nd node but unless I use desination address persistence, and requests continue to go to one node, everything fails (404 authentication errors). I am not using SSL. I am using standard VIPs, HTTP, NO OneConnect because the doc says not to if we are using NTLM, and cooke persistence (with the one server of course).

 

 

I guess my questions are these at this point...

 

 

1. Is it wrong to configure VIPs, pools, and node for IP?

 

 

2. Is it possible to get load balancing to work with destination address affinity (sticky) persistence? Because every time I configure sticky, everything goes to one node. Even after the clients clear their cache.

 

 

Thanks to all who respond and offer suggestions...

 

 

Steve