This content has been marked as final. Show 3 replies
I can think of numerous reasons it might fail in an LPAR environment.
First recommendation is that from inside the LPAR you validate that as the LPAR's root you can see what you think is there and can ping what you think is pingable.
My guess is that you are in for a surprise.
Windows: CLUVFY Fails with TCP Check PRVF-7617 Due to Case of Node Names [ID 1286394.1]
PRVF-7617: TCP connectivity check failed for subnet [ID 1335136.1]
Thank you that article explains what was wrong.