Windows 2003 SP1 DC no Network Connectivity
ID: 10 Category: Server Status: Closed Views: 7757


Question:

Symptoms

 

No Local Area Connection in Network Connections

Cannot resolve DNS not even if listed in hosts file

Can or cannot ping via IP address

Strange characters when trying to ping

Destination host unreachable when pinging local subnet

Taking very long to boot

RPC service Hanging or not started

COM+ Events not started (needed for Local Area Connection)

 

Following Errors in System Log

 

Event Type:       Error

Event Source:    IPSec

Event Category: None

Event ID:           4292

Date:                12/10/2005

Time:                10:54:26 PM

User:                N/A

Computer:         DATA

Description:

The IPSec driver has entered Block mode. IPSec will discard all inbound and outbound TCP/IP network traffic that is not permitted by boot-time IPSec Policy exemptions. User Action: To restore full unsecured TCP/IP connectivity, disable the IPSec services, and then restart the computer. 

 

Event Type:       Warning

Event Source:    LsaSrv

Event Category: None

Event ID:           32777

Date:                12/10/2005

Time:                10:53:06 PM

User:                N/A

Computer:         DATA

Description:

The LSA was unable to register its RPC interface over the TCP/IP interface. Please make sure that the protocol is properly installed.

 

Event Type:      Error

Event Source:   SAM

Event Category:            None

Event ID:          12291

Date:                12/10/2005

Time:                10:53:06 PM

User:                N/A

Computer:        DATA

Description:

SAM failed to start the TCP/IP or SPX/IPX listening thread



Solution:

 

Solution:

 

Starting with SP1 on Windows 2003 the RPC service uses “NT Authority\NetworkService” to logon instead of a system account.  Put the RPC service temporarily to logon as System Account. Change all Exchange services to manual from automatic if Exchange is loaded and reboot.

 

 

Open regedit and export the following for a backup.

Hkey_local_machine\system\CurrentControlSet\Services\Winsock

Hkey_local_machine\system\CurrentControlSet\Services\Winsock2

 

Now delete the keys you just exported

 

Collapse all keys and highlight HKEY_LOCAL_MACHINE

Goto File>Load Hive

Browse to C:\Windows\Repair and select System

When asked for Key name call it “Test”

 

Export the following Keys

 Hkey_local_machine\Test\ControlSet001\Services\Winsock

Hkey_local_machine\Test\ControlSet001\Services\Winsock2

 

Open Exported keys in Notepad and edit the path to match the following

Hkey_local_machine\system\CurrentControlSet\Services\Winsock

Hkey_local_machine\system\CurrentControlSet\Services\Winsock2

 

Highlight the Test Hive he go to File>Remove Hive

 

Now double click on Exported and edited Reg files this will add the Registry Values.

 

Verify the Keys loaded correctly

 

Reboot machine

 

After reboot verify you can resolve DNS and have network connectivity.

If not loaded load Windows 2003 Support Tools.

 

Open Domain Controller Security Policy >

Local Policy>User Rights Assignments>Impersonate a client after authentication

add ASPNET, Administrators, SERVICE all are assigned these rights.

 

Open Regedit  to change the RPC service to logon as NT AUTHORITY\NetworkService again.

Hkey_local_machine\system\CurrentControlSet\Services\RpcSs   ObjectName

 

Reboot

 

Verify server is still functioning properly then change Exchange Services back to Automatic Startup and start the services.

 

Once everything is back to normal reboot one more time to verify functionality

 

 



Submitted: 12/11/2005


Modified: 12/11/2005 2:35:50 PM


Related Issues:
No related issue is available.

Generated by the Help Desk, Developed by Expinion.net