Need Help Solving Netlogon Errors

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello--

We have a server on our network running Windows Server 2000 w/ SP4. It is a
web server and a terminal server. We host our website and about 2 other
websites from the same server.

There are multiple static IP addresses on the NIC card for the different
websites. We have two domain controllers on our LAN both work great and pass
all of the dcdiag tests I throw at them. I am just assuming this is a DNS
issue, as the verbiage in the event errors has to do with not being able to
communicate with the domain controller.

The web server that we are having problems with is getting event IDs of 5783
and 5719 every day--including times before our production hours start.

If anyone has any insight that might help us with what could be the cause
and how we might be able to solve this issue, I would sincerely appreciate it.

Thanks,

Stephen
 
razor said:
Hello--

We have a server on our network running Windows Server 2000 w/ SP4.
It is a web server and a terminal server. We host our website and
about 2 other websites from the same server.

There are multiple static IP addresses on the NIC card for the
different websites. We have two domain controllers on our LAN both
work great and pass all of the dcdiag tests I throw at them. I am
just assuming this is a DNS issue, as the verbiage in the event
errors has to do with not being able to communicate with the domain
controller.

The web server that we are having problems with is getting event IDs
of 5783 and 5719 every day--including times before our production
hours start.

If anyone has any insight that might help us with what could be the
cause
and how we might be able to solve this issue, I would sincerely
appreciate it.
Click to expand...

Do all your machines use only the DCs' IP addresses for DNS, only?
 
razor said:
Yes.
Click to expand...

Can you post the full data from these events?

Also, some test you may try on this server are:

netdiag /v
dcdiag /n:<ADDNSDomainName> /e /v
 
Sure--

For event ID 5783:
"The session setup to the Windows NT or Windows 2000 Domain COntroller
\\pwr-dc1.pwar.com for the domain PWAR is not responsive. The current RPC
call from Netlogon on \\PWARDELLIIS to \\pwr-dc1.pwar.com has been cancelled."

(On the above, pwr-dc1 is our DC and DNS server and is running on Windows
Server 2003 Enterprise. PWARDELLIIS is the problem server.

For event ID 5719:
"No Windows NT or Windows 2000 Domain Controller is available for domain
PWAR. The following error occurred: There is currently no logon servers
available to service the logon request."

Hope that helps.

sd
 
razor said:
Sure--

For event ID 5783:
"The session setup to the Windows NT or Windows 2000 Domain COntroller
\\pwr-dc1.pwar.com for the domain PWAR is not responsive. The current
RPC call from Netlogon on \\PWARDELLIIS to \\pwr-dc1.pwar.com has
been cancelled."

(On the above, pwr-dc1 is our DC and DNS server and is running on
Windows Server 2003 Enterprise. PWARDELLIIS is the problem server.

For event ID 5719:
"No Windows NT or Windows 2000 Domain Controller is available for
domain PWAR. The following error occurred: There is currently no
logon servers available to service the logon request."
Click to expand...

Is there a firewall between the Web server and the DCs?

What information did you get from the netdiag and DCdiag?
 
The server is inside the firewall, where the DNS and DC server is--so, no
there is no firewall between them.

On the dcdiag, all passed. I did not run a netdiag test. Which one should I
run?

sd
 
razor said:
The server is inside the firewall, where the DNS and DC server
is--so, no there is no firewall between them.

On the dcdiag, all passed. I did not run a netdiag test. Which one
should I run?
Click to expand...

netdiag /v

Post ipconfig /all
 
OK--here's is what we get. The netdiag does not look good.

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator>netdiag /v
[FATAL] Failed to get system information of this machine.

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

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : pwardelliis
Primary DNS Suffix . . . . . . . : pwar.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : pwar.com

Ethernet adapter Broadcom NetXtreme Gigabit Ethernet Adapter - onboard 1:

Connection-specific DNS Suffix . : pwar.com
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
Physical Address. . . . . . . . . : 00-06-5B-F1-ED-23
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.3.59
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.3.10
DNS Servers . . . . . . . . . . . : 192.168.3.10
192.168.3.5
Lease Obtained. . . . . . . . . . : Wednesday, March 01, 2006
5:46:31 PM

Lease Expires . . . . . . . . . . : Thursday, March 09, 2006 5:46:31
PM

Ethernet adapter Broadcom NetXtreme Gigabit Ethernet Adapter - onboard 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
#2
Physical Address. . . . . . . . . : 00-06-5B-F1-ED-24
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.3.222
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.3.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.3.112
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.3.200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.3.47
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.3.2
DNS Servers . . . . . . . . . . . : 192.168.3.10
192.168.3.5

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

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : pwardelliis
Primary DNS Suffix . . . . . . . : pwar.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : pwar.com

Ethernet adapter Broadcom NetXtreme Gigabit Ethernet Adapter -
onboard 1:

Connection-specific DNS Suffix . : pwar.com
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
Physical Address. . . . . . . . . : 00-06-5B-F1-ED-23
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.3.59
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.3.10
DNS Servers . . . . . . . . . . . : 192.168.3.10
192.168.3.5
Lease Obtained. . . . . . . . . . : Wednesday, March 01, 2006
5:46:31 PM

Lease Expires . . . . . . . . . . : Thursday, March 09, 2006
5:46:31 PM

Ethernet adapter Broadcom NetXtreme Gigabit Ethernet Adapter -
onboard 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
#2
Physical Address. . . . . . . . . : 00-06-5B-F1-ED-24
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.3.222
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.3.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.3.112
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.3.200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.3.47
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.3.2
DNS Servers . . . . . . . . . . . : 192.168.3.10
192.168.3.5
Click to expand...

This is going to be a routing nightmare, both NICs are on the same subnet.
Not sure why you have it set up this way or why you even have NIC1 enabled
or what it is connected to, please explain.
 
--it was set to manual and hadn't started. I started it and ran the netdiag
command again. Here are the results--sorry, kind of long:

AIT
TCP pwardelliis:2023 pwr-dc1.pwar.com:microsoft-ds
ESTABL
ISHED
TCP pwardelliis:2296 pwr-dc1.pwar.com:1025
TIME_W
AIT
TCP pwardelliis:2971 pwar-sql.pwar.com:ms-sql-s
ESTABL
ISHED
TCP pwardelliis:3099 pwar-sql.pwar.com:ms-sql-s
ESTABL
ISHED
TCP pwardelliis:3224 pwar-sql.pwar.com:ms-sql-s
TIME_W
AIT
TCP pwardelliis:3226 pwar-sql.pwar.com:ms-sql-s
TIME_W
AIT
TCP pwardelliis:3227 pwar-sql.pwar.com:ms-sql-s
TIME_W
AIT
TCP pwardelliis:3389 stephend.pwar.com:1942
ESTABL
ISHED
TCP pwardelliis:3981 pwar-sql.pwar.com:ms-sql-s
TIME_W
AIT
TCP pwardelliis:4119 pwar-sql.pwar.com:ms-sql-s
ESTABL
ISHED
TCP pwardelliis:4120 pwar-sql.pwar.com:ms-sql-s
TIME_W
AIT
TCP pwardelliis:4124 pwar-sql.pwar.com:ms-sql-s
ESTABL
ISHED
TCP pwardelliis:4125 pwar-sql.pwar.com:ms-sql-s
ESTABL
ISHED
TCP pwardelliis:4229 pwardelliis.pwar.com:26755
LISTEN
ING
TCP pwardelliis:4647 pwar-sql.pwar.com:ms-sql-s
ESTABL
ISHED
TCP pwardelliis:4648 pwar-sql.pwar.com:ms-sql-s
ESTABL
ISHED
TCP pwardelliis:4649 pwar-sql.pwar.com:ms-sql-s
ESTABL
ISHED
TCP pwardelliis:4651 pwar-sql.pwar.com:ms-sql-s
ESTABL
ISHED
TCP pwardelliis:netbios-ssn pwardelliis.pwar.com:18638
LIS
TENING
TCP pwardelliis:microsoft-ds pwaor-91f1d388d.pwar.com:1651
ES
TABLISHED
TCP pwardelliis:microsoft-ds callcenterw.pwar.com:2265
ES
TABLISHED
TCP pwardelliis:microsoft-ds spare_desktop.pwar.com:1270
ES
TABLISHED
TCP pwardelliis:1581 pwardelliis.pwar.com:26774
LISTEN
ING
TCP pwardelliis:1581 backup.pwar.com:netbios-ssn
ESTABL
ISHED
TCP pwardelliis:1586 pwardelliis.pwar.com:10403
LISTEN
ING
TCP pwardelliis:1586 terminalserver.pwar.com:netbios-ssn
ESTABL
ISHED
UDP pwardelliis:epmap *:*
UDP pwardelliis:snmp *:*
UDP pwardelliis:microsoft-ds *:*
UDP pwardelliis:1027 *:*
UDP pwardelliis:1044 *:*
UDP pwardelliis:1265 *:*
UDP pwardelliis:1568 *:*
UDP pwardelliis:1645 *:*
UDP pwardelliis:1646 *:*
UDP pwardelliis:1702 *:*
UDP pwardelliis:radius *:*
UDP pwardelliis:radacct *:*
UDP pwardelliis:3002 *:*
UDP pwardelliis:3456 *:*
UDP pwardelliis:3618 *:*
UDP pwardelliis:2418 *:*
UDP pwardelliis:2543 *:*
UDP pwardelliis:4745 *:*
UDP pwardelliis:4746 *:*
UDP pwardelliis:isakmp *:*
UDP pwardelliis:netbios-ns *:*
UDP pwardelliis:netbios-dgm *:*
UDP pwardelliis:isakmp *:*
UDP pwardelliis:netbios-ns *:*
UDP pwardelliis:netbios-dgm *:*
UDP pwardelliis:isakmp *:*
UDP pwardelliis:isakmp *:*
UDP pwardelliis:isakmp *:*
UDP pwardelliis:isakmp *:*


IP Statistics

Packets Received = 3,284,270
Received Header Errors = 0
Received Address Errors = 14
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 0
Received Packets Delivered = 3,293,088
Output Requests = 3,098,230
Routing Discards = 0
Discarded Output Packets = 0
Output Packet No Route = 0
Reassembly Required = 0
Reassembly Successful = 0
Reassembly Failures = 0
Datagrams successfully fragmented = 0
Datagrams failing fragmentation = 0
Fragments Created = 0
Forwarding = 1
Default TTL = 128
Reassembly timeout = 60


TCP Statistics

Active Opens = 55,395
Passive Opens = 24,044
Failed Connection Attempts = 1,037
Reset Connections = 10,126
Current Connections = 85
Received Segments = 2,880,404
Segment Sent = 2,972,192
Segment Retransmitted = 15,021
Retransmission Timeout Algorithm = vanj
Minimum Retransmission Timeout = 300
Maximum Retransmission Timeout = 240,000
Maximum Number of Connections = -1


UDP Statistics

Datagrams Received = 410,794
No Ports = 610,949
Receive Errors = 0
Datagrams Sent = 109,766


ICMP Statistics

Received Sent
Messages 670 670
Errors 0 0
Destination Unreachable 0 0
Time Exceeded 2 2
Parameter Problems 0 0
Source Quenchs 0 0
Redirects 0 0
Echos 313 313
Echo Replies 355 355
Timestamps 0 0
Timestamp Replies 0 0
Address Masks 0 0
Address Mask Replies 0 0


Bindings test. . . . . . . . . . . : Passed
Component Name : Broadcom Advanced Server Program Driver
Bind Name: Blfp
Binding Paths:
Owner of the binding path : Broadcom Advanced Server Program Driver
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Broadcom Advanced Server Program Driver
Lower Component: Broadcom NetXtreme Gigabit Ethernet

Owner of the binding path : Broadcom Advanced Server Program Driver
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Broadcom Advanced Server Program Driver
Lower Component: Broadcom NetXtreme Gigabit Ethernet #2


Component Name : Network Monitor Driver
Bind Name: NM
Binding Paths:
Owner of the binding path : Network Monitor Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Network Monitor Driver
Lower Component: Broadcom NetXtreme Gigabit Ethernet

Owner of the binding path : Network Monitor Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Network Monitor Driver
Lower Component: Broadcom NetXtreme Gigabit Ethernet #2

Owner of the binding path : Network Monitor Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanbh
Upper Component: Network Monitor Driver
Lower Component: WAN Miniport (Network Monitor)


Component Name : NDIS Usermode I/O Protocol
Bind Name: Ndisuio
Binding Paths:
Owner of the binding path : NDIS Usermode I/O Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS Usermode I/O Protocol
Lower Component: Broadcom NetXtreme Gigabit Ethernet

Owner of the binding path : NDIS Usermode I/O Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS Usermode I/O Protocol
Lower Component: Broadcom NetXtreme Gigabit Ethernet #2


Component Name : Point to Point Tunneling Protocol
Bind Name: mspptp
Binding Paths:

Component Name : Layer 2 Tunneling Protocol
Bind Name: msl2tp
Binding Paths:

Component Name : Remote Access NDIS WAN Driver
Bind Name: NdisWan
Binding Paths:
Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: Direct Parallel

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (PPTP)

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (L2TP)

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanasync
Upper Component: Remote Access NDIS WAN Driver
Lower Component: RAS Async Adapter


Component Name : Message-oriented TCP/IP Protocol (SMB session)
Bind Name: NetbiosSmb
Binding Paths:

Component Name : WINS Client(TCP/IP) Protocol
Bind Name: NetBT
Binding Paths:
Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom NetXtreme Gigabit Ethernet

Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom NetXtreme Gigabit Ethernet #2

Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : Internet Protocol (TCP/IP)
Bind Name: Tcpip
Binding Paths:
Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom NetXtreme Gigabit Ethernet

Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom NetXtreme Gigabit Ethernet #2

Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : Client for Microsoft Networks
Bind Name: LanmanWorkstation
Binding Paths:
Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Message-oriented TCP/IP Protocol (SMB session)

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom NetXtreme Gigabit Ethernet

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom NetXtreme Gigabit Ethernet #2

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : Wireless Configuration
Bind Name: wzcsvc
Binding Paths:

Component Name : Steelhead
Bind Name: RemoteAccess
Binding Paths:

Component Name : Dial-Up Server
Bind Name: msrassrv
Binding Paths:

Component Name : Remote Access Connection Manager
Bind Name: RasMan
Binding Paths:

Component Name : Dial-Up Client
Bind Name: msrascli
Binding Paths:

Component Name : File and Printer Sharing for Microsoft Networks
Bind Name: LanmanServer
Binding Paths:
Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: Message-oriented TCP/IP Protocol (SMB session)

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom NetXtreme Gigabit Ethernet

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom NetXtreme Gigabit Ethernet #2

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : Generic Packet Classifier
Bind Name: Gpc
Binding Paths:

Component Name : NetBIOS Interface
Bind Name: NetBIOS
Binding Paths:
Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom NetXtreme Gigabit Ethernet

Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom NetXtreme Gigabit Ethernet #2

Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : QoS RSVP
Bind Name: RSVP
Binding Paths:

Component Name : WAN Miniport (Network Monitor)
Bind Name: NdisWanBh
Binding Paths:

Component Name : WAN Miniport (IP)
Bind Name: NdisWanIp
Binding Paths:

Component Name : Direct Parallel
Bind Name: {841DB5C4-8775-4E71-8108-B0C912D54F70}
Binding Paths:

Component Name : WAN Miniport (PPTP)
Bind Name: {E35DC782-D77D-4386-A5A7-763A1B058AC8}
Binding Paths:

Component Name : WAN Miniport (L2TP)
Bind Name: {E6D3F369-1A8C-487A-8255-1AAD3719EC6A}
Binding Paths:

Component Name : RAS Async Adapter
Bind Name: {0608CF7E-BC83-49A4-9D96-72614D2D8098}
Binding Paths:

Component Name : Broadcom NetXtreme Gigabit Ethernet #2
Bind Name: {B07620C3-12BF-45D8-9CBC-D68417769453}
Binding Paths:

Component Name : Broadcom NetXtreme Gigabit Ethernet
Bind Name: {EA34CB1D-4963-43D6-92FD-671F04605FDD}
Binding Paths:



WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Passed
IPSec policy service is active, but no policy is assigned.

IPSec Statistics

Oakley Main Modes : 0
Oakley Quick Modes : 0
Active Associations : 0
Soft Associations : 0
Authenticated Bytes Sent : 0
Authenticated Bytes Received : 0
Confidential Bytes Sent : 0
Confidential Bytes Received : 0
Offloaded Bytes Sent : 0
Offloaded Bytes Received : 0
ReKeys : 0

Authentication Failures : 0
Negotiation Failures : 0
Packets not decrypted : 0
Packets not authenticated : 0
Invalid Cookies Rcvd : 0
Acquire fail : 0
Receive fail : 0
Send fail : 0
GetSpiFail : 0
KeyAddFail : 0
KeyUpdateFail : 0

Active Acquire : 1
Active Rcv : 0
Active Send : 0
Total Acquire : 0
TotalGetSpi : 0
TotalKeyAdd : 0
TotalKeyUpdate : 0
Inactive Associations : 0
Dead Associations : 0
Pending Keys : 0
Key Flushes : 0
Key Additions : 0
Key Deletes : 0

Phase 1 offers count is 4
OFFER #1:
PFS : No, Encryption : 3DES, Hash : SHA1, Group : Medium (2)
Quickmodes per MainMode : 0, Lifetime Seconds : 28800
OFFER #2:
PFS : No, Encryption : 3DES, Hash : MD5, Group : Medium (2)
Quickmodes per MainMode : 0, Lifetime Seconds : 28800
OFFER #3:
PFS : No, Encryption : DES, Hash : SHA1, Group : Low (1)
Quickmodes per MainMode : 0, Lifetime Seconds : 28800
OFFER #4:
PFS : No, Encryption : DES, Hash : MD5, Group : Low (1)
Quickmodes per MainMode : 0, Lifetime Seconds : 28800

Current Phase 1 SAs:
No SAs.


Current Phase 2 SAs:
No SAs.




The command completed successfully

C:\Documents and Settings\Administrator>

Kevin D. Goodknecht Sr. said:
razor said:
OK--here's is what we get. The netdiag does not look good.

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator>netdiag /v
[FATAL] Failed to get system information of this machine.
Click to expand...

Start the remote registry service.
http://support.microsoft.com/kb/287735/en-us
Click to expand...
 
We don't even need the 2nd NIC enabled. It was configured with the Dell
Poweredge 2650 server from Dell as a bridge for checksum offload, etc.

We tried to speak to Dell tech support and Broadcom (the NIC card
manufacturer) and finally gave up as they were non-responsive.

Broadcom said we should be able to have one NIC as static and one dynamic
for IP addresses with no problems, but then would not support us when we
started getting errors in the event log.

Would you recommend we disable one NIC?

sd
 
razor said:
--it was set to manual and hadn't started. I started it and ran the
Click to expand...

You need to export the output from the Netdiag to a text file, not all of
the tests I want to see are here.

Netdiag /v >C:\netdiag.txt
 
razor said:
We don't even need the 2nd NIC enabled. It was configured with the
Dell Poweredge 2650 server from Dell as a bridge for checksum
offload, etc.

We tried to speak to Dell tech support and Broadcom (the NIC card
manufacturer) and finally gave up as they were non-responsive.

Broadcom said we should be able to have one NIC as static and one
dynamic for IP addresses with no problems, but then would not support
us when we started getting errors in the event log.

Would you recommend we disable one NIC?
Click to expand...

Yes, I can't see a reason you need multi-homing NICs. Especially if they are
on the same subnet.
 
OK--we're off until Monday, so I'll run it then, and paste the text file
reults.

I really appreciate your help on this.

sd
 
Back
Top