on 11-01-2010 3:37 PM
Hello to the group.
Has anyone else run into this?
We are running several systems (SOLMAN, ECC, etc.) on Windows Server 2008 clusters. Each cluster has four network devices two of which are public facing and two are the heartbeat connections between the two cluster nodes. When we resolve the server names from each of the systems (from the windows command prompt) the names resolve correct to IP addresses of the public facing devices. But when we try to resolve the system name using NIPING, we get the address of the heartbeat network devices instead.
The issue this creates is the message server is resolving names to the wrong devices/addresses and thus, breaks the ability to use Logon Load Balancing.
I have searched the forums but have few ideas. Hints to forum entries or ideas are much appreciated.
Thanks!
Joe Haynes
SAP Basis
CaridianBCT
Edited by: Joe Haynes on Nov 1, 2010 1:22 PM
Hi Joe,
In that case I would check the bindings in the advanced network settings. The public facing IP should be the first in the list.
If it is not it is easy to change.
Regards,
Olivier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Please check
note 112266 section 5
regards,
John Feely
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Few things to check first:
1. What does "nslookup" show for the virtual hostname resolution? - private or public ip's for the hostnames?
2. NIPING usually checks the services file, does it have correct entries?
3. Also last but not the least, does your hosts file have the correct entries?
- Regards, Dibya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.