WINS is red X after deleting one NIC in Multihomed server

[chicagotech]

The client has a windows 2003 SBS running RWW and SharePoint. They asked to fixed the Activesync. I did. The problem now is the WINS. They used to have two NICs, using the same IP addresses. NIC1 is 192.168.1.2 DG 192.168.1.1, DNS/WINS 192.168.1.3 and NIC2 is 192.168.1.3., DG blank, DNS/WINS 192.168.1.3. After I disabled NIC2 and made NIC1 is DNS/WINS, the WINS is red X. Whenever I delete, it comes back with red X. I tried to reboot it, but still the same problem. How do you fix it?

[chicagotech]

Also the SBS has Event ID 1058 and 1030 logged after disabled the NIC2.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 2/12/2009
Time: 10:36:04 PM
User: NT AUTHORITY\SYSTEM
Computer: SERVER
Description:
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 2/12/2009
Time: 10:36:04 PM
User: NT AUTHORITY\SYSTEM
Computer: SERVER
Description:
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=mercurio,DC=local. The file must be present at the location <mercurio>. (Access is denied. ). Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[chicagotech]

Analysis
======
Because the IP address of the disabled NIC was DNS and WINS server address,
disabling it may cause problems. From the symptom of the issue, it appears
that DNS resource record for NIC1 192.168.1.2 is not correct in DNS which
causes problems. To verify and troubleshoot the problem, please follow the
steps below:

Suggestion
=========
Step 1:
First of all, please check the network settings of NIC1. To do so,
1. Click Start, point to Control Panel, and then double-click Network
Connections.
2. Right-click the local area connection, and then click Properties.
3. On the General tab, click to select the Client for Microsoft Networks
check box.
4. Click to select the File and Printer Sharing for Microsoft Networks
check box.
5. Click Internet Protocol (TCP/IP), and then click Properties.
6. Type the IP addresses of 192.168.1.2 in the Preferred DNS server box.
7. Click Advanced, and then click the DNS tab.
8. Click to select the Register this connection's addresses in DNS check
box, and then click OK three times.
9. Click the WINS tab, type the IP addresses of 192.168.1.2 in the WINS
address box.
10. Ensure Enabled NetBIOS over TCP/IP is selected.
11. Start a command prompt. To do this, click Start, click Run, type cmd,
and then click OK.
12. Type "net stop netlogon && net start netlogon" then press ENTER.
13. Restart the computer for your changes to take effect.

Step 2:
Check DNS database. To do so,
1. On the SBS, click Start, point to Administrative Tools, and then click
DNS.
2. Expand Your_Server_Name, expand Forward Lookup Zones, and then click the
forward lookup zone for your domain.
3. Look for the (same as parent folder) Host (A) record.
4. If the (same as parent folder) Host (A) record does not exist, follow
these steps to create one:
a. On the Action menu, click New Host (A).
b. In the IP address box, type the IP address of 192.168.1.2.
c. Click to select the Create associated pointer (PTR) record check box,
and then click Add Host.
d. When you receive the following message, click Yes:
(same as parent folder) is not a valid host name. Are you sure you want to
add this record?
5. Double-click the (same as parent folder) Host (A) record.
6. Verify that the correct IP address is listed in the IP address box.
7. If the IP address is in the IP address box is not valid, type the
correct IP address in the IP address box, and then click OK.
8. Alternatively, you can delete the (same as parent folder) Host (A)
record 192.168.1.3. To delete the Host (A) record, right-click (same as
parent folder), and then click Delete.
9. If the DNS server is a domain controller that is also a Routing and
Remote Access server, view the following Microsoft Knowledge Base article:
292822 (http://support.microsoft.com/kb/292822/ ) Name resolution and
connectivity issues on a Routing and Remote Access Server that also runs
DNS or WINS
10. Type ipconfig /flushdns at a command prompt, and then press ENTER.

[chicagotech]

I already did step 1 and 2 before I posted. Here are the results of ipconfig
/all and nslookup.


C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : server
Primary Dns Suffix . . . . . . . : mercurio.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : mercurio.local

Ethernet adapter Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
#2
Physical Address. . . . . . . . . : 00-14-22-7A-AD-A4
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.2
Primary WINS Server . . . . . . . : 192.168.1.2

C:\Documents and Settings\Administrator>nslookup
Default Server: server.mercurio.local
Address: 192.168.1.2

[chicagotech]

Thank you for your reply and I understand that you've already done the
steps in previous thread with no success. In this case, please try the
following steps and tell me the result:

1. Please check whether the following services are running:
TCP/IP NetBIOS Helper;
Remote Registry;
Remote Procedure Call(RPC).

2. If the problem persists, please full backup your server and re-install
the NIC(192.168.1.2):

Step 1: backup your system

Step 2: Find the GUID of the interface:
==========================
To determine the GUID value for an adapter corresponding to a LAN
connection in the Network Connections folder, do the following:

1. Open the Network Connections folder and note the name of the LAN
connection, such as "Local Area Connection."
2. Click Start, click Run, type regedit.exe, and then click OK.

3. Use the tree view (the left pane) of the Registry Editor tool to open
the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-1
1CE-BFC1-08002BE10318}

4. Under this key are one or more keys for the globally unique identifiers
(GUIDs) corresponding to the installed LAN connections. Each of these GUID
keys has a Connection subkey. Open each of the GUID\Connection keys and
look for the Name setting in the contents pane whose value matches the name
of your LAN connection from step 1.

5. When you have found the GUID\Connection key that contains the Name
setting that matches the name of your LAN connection, write down or
otherwise note the GUID value.

Step 3: Reinstall NIC
=============
1. Please download the latest version of the NIC card driver on the server.
2. Delete the following registry keys:

1) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Config
2)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Adapte
rs\ {Active GUID}
3)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interf
aces\{Active GUID}

Note: you can get the GUID from step 2.

4) Open the Device Manager; Uninstall the Network Card and reboot. When
the server comes up it will auto detect the NIC card and will install the
driver, if it does not, install the NIC driver manually.

To verify the NICs are installed correctly, please follow the steps:
1. Open Device Manager
2. Select Network Adapters
3. Click View on the menu and select Show Hidden Devices
4. Verify if RAS Async Adapter and WAN Miniport (PPTP) are installed
correctly

3. If after re-installation the problem persists, please check if the IPC$
share is missing. To do so, please use the command "net share" and verify
if IPC$ is listed.

[chicagotech]

We fixed the problem by disabling 192.168.1.2 and re-enabled 192.168.1.3.