Atatpi timeout error 2003 Server

[masinc1]

XP Pro Workstations connecting to 2003 server. Server has event 9 atapi time-out error on IDEport0.

Error occurs when one or more workstations are using the accounting software located on the server. The same operation performed on the server is fast and flawless. Once the atapi error presents, the workstation generally hangs repeatedly when in the accounting system, even for the most basic operation like login. There will be multiple atapi errors on the server, all coinciding with the time the workstation hung. The error never occurs if the user moves to the server. Have bypassed all internal cabling and connected a workstation directly to the server with no change in results. Have checked and changed internal cables on the server. IDEport0 is the DVD/CD.

 

[goombawaho]

So, for fun unplug the CD drive and see what happens. Can you even disable the IDE port in the BIOS? Try a new CD drive and new IDE cable.

Then start wondering if the motherboard is going bad. What is your disk subsystem (server hard drives and controller) setup?

 

[itsp1965]

What type of server is this. I remember that some SUN based AMD servers had a virtual ATAPI driver that would give me the same type of grief. Check device manager to see if there's something similar.

 

[masinc1]

Thnaks for the response.

I disconnected the IDE cable to the CD. The atapi error has not returned.but the workstations still hang intermittently. The server does not return any error messages for those hangs.

Intel motherboard w/2 Western Digital hard drives, SATA, Raid Array.

 

[goombawaho]

So, it's not really a server but more like a home-built/redneck server. Did you try to disable the IDE ports? Have you updated the BIOS? Have you run the Intel RAID verify/fix option within the Intel Rapid Storage Technology program? Does the status say "OK" for the RAID before you run the verify/fix?

Have you thought about maybe having a bad switch that the server and workstation are plugged into if you have just one switch? You have to work backwards from (everything on) the server to the server network cable to the network switches, to the computers themselves (cables, wall jacks, network card drivers). Dive in, there's lots to check.

With the network card drivers on the PCs, look to see if they are the same or different adapters in problem vs. non-problem PCs. Different driver versions if the same cards. Settings......

 

[masinc1]

Cabled one workstation to the server using a new Dlink switch - bypassing all internal cabling and the main switch. Still experienced hangs. Replaced the network card in the workstation - cabling direct to server w/new switch - still experienced hangs.

Will work on your other suggestions.

Thanks

 

[goombawaho]

Yeah, I kind of forgot that you said originally that you tried direct connection between server and workstation. Try some of the other things I mentioned. Did you make any changes to your server (updates, patches, accounting software updates) or to the workstations recently?

One more thing to try. After the workstation does it's thing (hanging), can you still ping the server by name and/or ip address from a CMD prompt? Can you ping from server to workstation the same way? Some how you have to get it down to a hardware issue or the accounting software.

 

[masinc1]

Pinging between server & workstations - either direction works fine. I have queried the software company. Because the accounting software operates instantaneously on the server they find no problem with their product. No updates or patches.

The server has 2 NICs on the motherboard, numbered 5 & 6. Looking at hidden devices finds NIC 1, 2, 3, 4 also.

Thanks for responding

 

[goombawaho]

If only one is plugged in, I don't see any issue with hidden or second adapter.