Event 2009 - ML530 NT4.0

[iscsiman]

I am seeing many Event 2009 errors under NT 4.o Server(SP6a), when I enable hyperthreading in the BIOS.
Changing this one setting before NT4 install fixes this issue...but obviously not a solution I want.

Windows 2000 Advance Server SP3 runs fine with hyperthreading. I understood that both OS's are "hyperthreading unaware".

I need NT 4.0 on this system.
Has anyone seem this issue?
Any ideas/solutions?

MS KB article says too many shares...but this is a fresh install (not upgrade) no shares, or login scripts.

TIA,
Ben

 

[diamondlod]

A 2009 error can actually be a bunch of things. (What? Microsoft give a non-specific error?? NOOOO!!!)

Determining what the problem is will relate to the details in the error log. Microsoft has a half-way decent kb article on it...

http://support.microsoft.com/default.aspx?scid=kb;en-us;165815

The only time I've ever run into a 2009 error, however, has been due to an incorrect setting in the TCP/IP parameters in regards to retransmission timeouts. NT4 can only handle 2,048 open ports at once, and if the server tries to open more than that, the server throws up 2009 errors and refuses all further connections.

If you have some more specifics, post them here and I'll try to help out.

 

[iscsiman]

Thank you for your reply.
I saw the kb article...this is my specific error code.
------------------------------------------
Error: 0x3eb (SRV_TABLE_SESSION)
This indicates that no more user IDs (UIDs) exist to satisfy this BlockingSessionSetupAndX SMB.
Monitor these performance monitor counters:
Redirector\Server sessions
Redirector\Server sessions hung

To help eliminate this problem, check for unneeded user sessions on the server. This may include mapped drives in logon scripts or applications that automatically map drives to particular servers.
-------------------------------------------

I checked Perf Mon and set the chart to 2000. Server sessions was maxed. Server sessions hung was 0.

We had a Compaq (#com/broadcom chip) GB PCI-X NIC in the system and on-board 10/100 NIC. As well as a test PCI board (placed in PCI slot). I had not shared any drives, or anything. This error came up right after fresh install. So no logon scripts or shares yet. I did not know any other way to elimate this.

My steps takes during install.
1. Change BIOS settings to Installed OS = NT 4.0
2. Install NT 4.0 Server
3. Install SP6a
4. Install IE 5.0 to get dll files needed to install (step5)
5. Ran Compaq update to get latest drivers for NT4.0

The problems went away when we disabled hyperthreading in the BIOS. This is for a test enviornment. So ideally, we would rather have hyperthreading turned on. I have heard that NT 4.0 and W2k are hyperthreading un-aware and it should be fine for both. The same test under W2k Adv Srvr went fine with no errors.

Even after this I could not load the Compaq NIC driver.
I switched to Intel GB NIC and all is OK now.
But I am concerned that hyperthreading could be enabled for the test, that there is something else I am missing in the BIOS or elsewhere.

Thank you for your time and comments on this.
-Ben

 

[diamondlod]

Did you try hyperthreading with the new Intel NIC, and did the same problem occur?

 

[iscsiman]

Not yet.
I hope to have the system available to me tommorrow, and I will try a few expiriments.
The first will be NT 4.0 with hyperthreading enabled and the test board out.
I will use the Compaq NIC.

If this produces the same error (2009), I will try the Intel NIC in place of the Compaq NIC.

If no error, add the test board with Compaq NIC.

Your words about the TCP/IP helped me concentrate more on the NIC.

Thanks,
Ben

 

[diamondlod]

Cool - I'll keep an eye on the thread, so let me know how it goes and I'll see what I can do to help.

 

[dequist]

Windows 2000 Advanced Server SP1 and up is hyper-threading aware, we have a few dozen DL580 G2's running without issue.

We have a PDC that is currently giving off 2009 errors on a DL380 G2, dual P3 1.26GHz. NT 4.0, SP6a + SRP. We have approximately 3000 users amongst different sites, whose logonservers are other BDC's, but for some reason about 1500 NT 4.0 workstations create a session to the PDC, even if it isn't the logonserver for that client. Any ideas why these sessions exist?

Thanks,
Dave

 

[sapmeier1]

hallo,
i also have this problem with a compaq server(NT4).
we have 4055 connected users in the server manager!
all this connection are without "connected users"(only computer name is displayed in the window)). this computer are w2k(sp3).
what can we do?
do you have any answer from dequist?
thanks a lot