Netdiag

[Premierkrm]

Why am I getting Netcard queries failed?

Computer Name: PCTCRM
DNS Host Name: PCTCRM.premiercomputing.com
System info : Microsoft Windows Server 2003 (Build 3790)
Processor : x86 Family 6 Model 11 Stepping 1, GenuineIntel
List of installed hotfixes :
Q147222


Netcard queries test . . . . . . . : Failed
GetStats failed for 'HP NC3163 Fast Ethernet NIC'. [ERROR_INVALID_FUNCTION]
[FATAL] - None of the netcard drivers provided satisfactory results.



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Failed
NetCard Status: UNKNOWN

Host Name. . . . . . . . . : PCTCRM
IP Address . . . . . . . . : 90.0.0.245
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 90.0.0.1
Dns Servers. . . . . . . . : 90.0.0.246
127.0.0.1


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{64A06481-7D3B-4831-BA3B-05EE8F5002CE}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{64A06481-7D3B-4831-BA3B-05EE8F5002CE}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{64A06481-7D3B-4831-BA3B-05EE8F5002CE}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Passed
Secure channel for domain 'PREMIER' is to '\\greatplains.premiercomputing.com'.


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


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


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

 

[netometer]

Hi!
I think that the message:
"[FATAL] - None of the netcard drivers provided satisfactory results"
means that your driver is not working fine.
There is a new driver for Windows Server 2003 on hp.com - version 8.0.21.0 published on 16 Aug 05:

http://h18007.www1.hp.com/support/files/networking/us/locate/69_5895.html

Download and try this new driver.
Good Luck!

NetoMeter

http://www.netometer.net

 

[ITPangaeaArchitect]

if not the driver...then a problem with the tcp/ip stack, bindings, or provider
1. network connections window
2. advanced menu..choose advanced settings
3. adapters and bindings tab ensure your NIC is at top of list, and that file and printer sharing for MS networks and Client for MS Networks is in the bottom "bindings for <connection> box...ensure both of these also have tcp/ip listed and that tcp/ip is at the top of the list of protocols....
4. provider order tab ensure that the netowrk providers order is either "MS Terminal Services, MS Windows Netowrk, and then Web Client Network" -OR- "MS Windows Network, MS Terminal Services, then Web Client network"

if that all checks out continue on



....if not a DC...remove the NIC (or uninstall in device mgr)...get the newest NIC driver as mentioned...reboot and click cancel when prompted to install the NIC if you did an uninstall....go into regedit and wack the interface is in HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces

take heed here as there will be 3 subkeys to the interfaces key even if only 1 NIC is installed....teh "dead" subkeys will have only the settings for DefaultGateway, DontAddDefaultGateway, EnableDeadGWDetect,EnableDHCP,IPAddress,SubnetMask,and UseZeroBroadcast....your actual interface will have much more information...for example...RawIPAllowedProtocols, Lease, LeaseObtainedTime, LeaseTerminatesTime, etc.


Could also try a new NIC with the newset drivers

If the above do not work, you may need to attempt to reinstall TCP/IP completely in the system:
I beleive this command should do it...but seems like theres additional steps I'm forgetting:
1. Install another protocol, such as netbeui (not available on 2003 but can use XP files to get it on there)
2. run "netsh int ip reset c:\ipreset.txt"..this should reset tcp/ip
-OR-
2. reinstall NIC (or new NIC) with newest drivers, install another communications protocol so you don't bone yourself, uncheck and remove tcp/ip on ALL NICs and other communications devices inside of My Network Places properties (network connections window)..this includes RRAS adapters, wireless adapters, etc....reboot, then readd the tcp/ip protocol to each item.


-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there

 

[ITPangaeaArchitect]

As a side note for something else that was put out by MS that could cause what you are seeing potentially:

If you are running Windows 2003 with SP1....you MUST have 898060 installed (this will save you sooo many headaches its not funny)

Windows 2003 RTM or earlier...you MUST ensure you have the latest build of 893066 installed.

Both of these are publicly downloadable...just query 898060 or 893066 at google.com and it will give you the links you need...there was a broken 893066 we put out...what it did that was extremely bad is dropped the TcpWindowSize to something like 64b (could be kb..but pretty sure networking said bytes)...and we also changed some other behavior that stuck us...main one was tcpwindosize though...

-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there