Dang! I spoke too soon. I had connected to my server via "mstsc /console"
workstation and server. I logged off, hit the KVM switch to go directly to
but took an abnormally long time (65 seconds) to be serviced by the OS. This
problem is likely due to faulty hardware. Please contact your hardware
vendor for further assistance diagnosing the problem.
Post by Gregg Hill
I have had the same error with my newly built server. Sometimes when I
access the server, the hard drive light comes on for up to 75 seconds and
the server hangs for that time period. Once the hard drive light goes off,
everything is fast. Event Viewer shows the same error you get.
I could most easily duplicate the error by using Remote Desktop form my
workstation to access the server. It seemed to be OK unless I used "mstsc
/console" to connect. Then it would hang almost every time.
SBS 2003 Premium, no premium components installed yet, everything at SP1,
using the latest drivers from the manufacturers for NIC, video, modem, etc
Intel Pentium 4 3.0GHz CPU
MSI 865PE Neo3 motherboard, latest BIOS
3GB Apacer PC3200 DDR400 RAM
80GB Western Digital SATA hard drive WD800JD (I wanted to see if SATA
would be fast so I do not have to spend three times as much for SCSI)
D-Link 10/100 NIC on WAN side, connected to Netgear FR114P router/firewall
On-board Realtek 8110S 10/100/1000 NIC for LAN
NVIDIA GeForce4 MX420 AGP video card
MultiTech Systems MT5634ZPX-PCI modem
Adaptec 39160 SCSI for the tape drive (Sony AIT1)
Veritas Backup Exec 10 SP1
Symantec Antivirus Corporate Edition 184.108.40.2060
Symantec Mail Security for Exchange 4.6
Digging through Google came up with the two links mentioned in this
thread. The first one mentions "autodisconnect" being changed. That did
not help my system. The second resolved their problem by re-installing. I
want to know the root cause before I re-install.
I also found
which suggested stopping the NTFRS service, deleting the database file,
excluding the folder from AV scans, and restarting the service. I did that
yesterday morning and so far, so good, but it has only been a day.
Someone else suggested excluding the SYSVOL folder from antivirus scans. I
am holding off on that to see if the above steps fix the problem, just so
I know for sure what is the root cause.
The biggest difference between my current system and my previous system
are 3GB of RAM vs. 1GB in the old one, and the new hard drive is an 80GB
SATA, while the old one was an 80GB EIDE, both Western Digital. The old
system never had this error.
Post by Mike Lloyd-Jones
EventId gives no real clues, and I haven't seen this one before either
Can file replication be disabled in a single server environment ? (no
point fixing this issue if ntfrs not needed I guess)
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Have you reviewed http://www.eventid.net for that code?
I've not seen that error.
Post by Mike Lloyd-Jones
Since upgrading to SBS SP1 standard (with all the pre-requisite steps
followed as per
MS and smallbizserver) we are getting the following error in system event
Timeout (30000 milliseconds) waiting for transaction response from NtFRS
This seems to happen between 12 and 2 am, but nothing obvious running at
same time. Has definitely only started since service pack install, domain is
single server setup (does file replication service even need to be started?)