How to determine which device is sending bad packets to server?

We have an older version of Microsoft Dynamics Navision on our network. Over the past few weeks it's been reporting an error - error 18 in module 244, multiple times/day, in the Windows 2003 server event log. Research on this error points to a network issue, possibly CRC, or some other related situation where bad packets are sent to the Navision server.

However, I haven't found a good way to determine which device (we have 100+ users) is sending the bad packets. I've replaced the NIC and cable on the server, and that didn't help. I've installed Wireshark, and I've tried looking for anything odd around the time the log entries are recorded, but I'm new to it and I don't know what to look for specifically, as nothing stood out.

Thanks.
ruhkusAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

KimputerCommented:
You have more problems here. Mainly because you don't know what you're looking for. I actually, highly doubt you would find it even IF you knew the problem with more details.
That's because right now, you think it's about "sending bad packets". This alone will help absolutely no one. Are those TCP packets ? On which port do they arrive. Even then the next question would be, how do you detect a bad packet from a good packet. I highly doubt you would find it in Wireshark with any filter you write.
A better solution would be to update your software. Proper software should not error when bad packets are sent. And proper software shouldn't send packets (so update both server and clients).
If you can't, there's nothing more you can do then methodically disconnect groups of PC's and see how it behaves, and continue untill you have positive results (and then divide that group again until you have the "culprit").
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ruhkusAuthor Commented:
We're actually moving to a new server with a new version of Navision software in a few months (data cleanup alone will take awhile). However, this means nothing to the 80 or so staff that rely on this program daily until then.

But yeah, I have no real idea what can best help track down this issue, and there doesn't seem to be a really viable way, since the rest of the network is running fine.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Analysis

From novice to tech pro — start learning today.