Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 727
  • Last Modified:

Web server with two IP addresses registers VIP first instead of physical IP in WINS

Hello,

I have web farm composed of two web servers. Web server #1 registers correctly in DNS as well as in WINS. In other words, when I look at the WINS database and locate the Active Registration for this server, I see the physical IP address listed and not the VIP. If I drill into the properties of this records, I will see two IP addresses listed; #1 physical IP and #2 VIP. However, for the second web server, the active registration in WINS shows the other way around. The active registration shows the VIP instead of the physical IP address. This second server registers fine in DNS. I believe this is causing a problem for this server when it comes to WINS resolution. I have a monitoring tool that keeps getting errors (RPC server is unavailable). When I research this issue, it points me to name resolution.

How can I correct the WINS active registration to replect the correct IP address order? I've tried to tombstone the active registration on the WINS owner server and then do nbstat -RR on the client. However, the record doesn't update as expected.

Network Info:
2 AD sites
2 DC/GC servers per site
2 WINS servers per site (service installed on DCs)
2 DNS servers per site (service installed on DCs)

Your help is much appreciated. Thanks.
0
bndit
Asked:
bndit
  • 2
1 Solution
 
TheCleanerCommented:
When you say VIP, in my world that is a virtual IP on a router or firewall.  Is that what you are referring to, or are you talking about a secondary IP on the NIC internal to the web server?  Is the web farm using clustering or NLB or similar?
0
 
bnditAuthor Commented:
I'm so sorry for the delayed response to this question. I made some chances to my pfofile and my smtp address was incorrect....in any event, I apologize for the inconvenience as I normally respond quickly.

As far as this question is concerned, the root-cause of the problem was access denied due to the client's missing computer account on the DNS record. In part, this issue was due to the fact that this client's DNS record was registered by a different computer account (DHCP server) since the DHCP server is setup to update both A and PTR records. Thus, everytime the client tried to register its PTR record, the access is denied. The solution was to modify the DHCP server option and use a service account to update the DNS records.

As for the VIP, it is an IP address shared by multiple nodes on a secondary NIC using NLB.

TheClearn, I'm awarding half the points for your reply. Thank you for the effort.
0
 
bnditAuthor Commented:
Found solution to problem.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now