Advertisement

11.01.2007 at 10:33AM PDT, ID: 22932906
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

WINS using wrong NIC on dual NIC Windows2003 server

Tags: server, wins, nic, dual, wrong
I have one Windows2003 Server called SERVER1 with 2 NICS:

NIC#1 - LAN - 192.168.3.201
NIC#2 - WAN - 99.99.99.202

There is only one server and it's running DHCP,DNS,AD and RRA(VPN).

DHCP, DNS and ActiveDirectory all seem to be working fine.
VPN works fine through NIC#2.
WINS works fine only when NIC#2 is disabled. But if I enable NIC#2 for the VPN, then WINS tries to use 99.99.99.202  

I uninstalled/reinstalled WINS and it is still trying to use the NIC#2.
I uninstalled WINS, disabled NIC#2, installed WINS, and it was fine.  MMC shows that WINS is connecting sucessfully to SERVER1 [192.168.3.201]

But when I enabled NIC#2 then it shows:
[+] SERVER1 [192.168.3.201]
but when I hit the [+] it changes to:
[X] SERVER1 [99.99.99.202]  (X) Cannot find the WINS server

I tried deleting the SERVER1 [99.99.99.202] then ADding it again, using the IP address 192.168.3.201
and again it shows
[+] SERVER1 [192.168.3.201]
but when I hit the [+] it changes to:
[X] SERVER1 [99.99.99.202]   (X) Cannot find the WINS server



>ipconfig /all
Windows IP Configuration
   Host Name . . . . . . . . . . . . : SERVER1
   Primary Dns Suffix  . . . . . . . : XXXX.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : XXXX.local

Ethernet adapter LAN - Internal:
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit Server Adapter
   Physical Address. . . . . . . . . : 00-XX-XX-XX-XX-01
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.3.201
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.3.1
   DNS Servers . . . . . . . . . . . : 192.168.3.201
   Primary WINS Server . . . . . . . : 192.168.3.201

Ethernet adapter WAN - External:
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Linksys EG1032 v3 Instant Gigabit Desktop Network Adapter Driver
   Physical Address. . . . . . . . . : 00-XX-XX-XX-XX-02
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 99.99.99.202
   Subnet Mask . . . . . . . . . . . : 255.255.248.0
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Disabled

WINS is messed. It thinks that the WINS server is 99.99.99.202 so it fails.




As soon as I enable NIC#2, WINS thinks that is the one it should use, so it fails.

Why is WINS still thinking that SERVER1 is on NIC#2 ?  How can I force it to use NIC#1 ?




DNS and WINS look absolutely fine.  WINS sees the server as 192.168.3.201 (NIC#1) correctly.

disable NIC#2 and WINS goes back to 192.168.3.201 and works fine.
I enable NIC#2 and WINS goes back to 99.99.101.202 and  fails.


This is driving me nuts!


Start your free trial to view this solution
Question Stats
Zone: Networking
Question Asked By: mark_goodall
Solution Provided By: TheCleaner
Participating Experts: 2
Solution Grade: A
Views: 34
Translate:
Loading Advertisement...
11.01.2007 at 10:37AM PDT, ID: 20194935

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
11.01.2007 at 11:45AM PDT, ID: 20195398

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
11.01.2007 at 11:54AM PDT, ID: 20195491

Rank: Sage

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
11.01.2007 at 12:40PM PDT, ID: 20195961

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
 
Loading Advertisement...
20080236-EE-VQP-29 / EE_QW_2_20070628