Forum Discussion
Okay, so a few questions:
-
Are you using an HTTPS monitor?
-
If you attempt to use cURL with IP and port instead of hostname, does it work?
The next step might be to ssldump on the server side to see what's inside that monitor request and response. For this you'll need to copy the server's SSL private key to the BIG-IP and use the following command:
ssldump -k [path to server's private key] -AdNn -i 0.0 port 443 and host [IP of server]
This should allow you to see inside the SSL traffic between the BIG-IP and server (assuming you're using RSA for key exchange). If you can do this, you should be looking for the client (BIG-IP) GET request, which will probably have a "Basic" Authorization header, followed by a 401 from the server, followed again by another request with an NTLM Authorization header. If the response to that is another 401 or you don't see the second request, then you know it's an auth problem with the monitor.