Forum Discussion
Pool member of an 445 VS can't access VIP when itself is the active member
There seem to have been a couple posts about this but the solutions aren't working for me. I'm having this issue on both 10.x and 11.x
I have a VS of IP:445 and 2 members on :445 setup as priority groups so that only 1 is active and the other "standby"
The nodes are dual purposed, and they themselves need to access this file share via the VIP. When I access the VIP from the "standby" node of the 445 pool, it works fine (connection hits the other node), but when I access the VS on the "active" node, it shows a dialog stating username or password is incorrect while prompting for new credentials. So I can't access the file share via the VIP when it's connecting to itself.
I have automap enabled (the standard for us...LTM's are on a stick) and the rest of the VS settings are default.
I thought this was working fine at some point, so maybe this is an OS issue (Win2012r2) vs. LTM but I'm using LTM so I'm hoping to find a solution here.
Anyone know what's going on?
- SurgeonRet. Employee
Hmmm, it depends if your back end server allows such sort of connection. If there are packets are leaving big-ip on the server side and there is no response from your server then contact your server vendor
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com