ftp DataRate Problem.......

Hi, I have multiples Pcs with Windows OSs and an IBM S/390 System, they are conected together by a switch (Enterasys-VH48 10/100Mbps).
PC-A=Windows server 2003 PC-B=Windows server 2003 PC-C=WindowsXP PC-D=Windows98

1.- We are having delay problems between S/390 and PC-A when I do a FTP conection from and to the 390 unit. DataRate=30kbps
2.- The connections between s390 and PC-B and between 390 and PC-C are fine. DataRate=98Mbps
3.- The connections between PC-A and  PC-B and PC-C are fine. DataRate=98Mbps
4.- The port where s/390 is connected presents CRC errors (51144 in 1 day)

The problem between s/390 and PC-A appear with other Pcs too, whatever OS it be.

Some Ideas?????

Thanks for your help

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.

>4.- The port where s/390 is connected presents CRC errors (51144 in 1 day)
These errors are unacceptible. They point to physical layer problems with cabling, punch-down panel, if you also see collisions, it could be a duplex mismatch, etc.

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
sounds like physical problem to me. check the cabling if that is not it check the configuration for the nic card. i usually use auto-negotiate for most network card settings and have been trouble free. like lrmoore said there could be a duplex mismatch. try changing the duplex settings if it is already on auto. after that it could be a bad network jack or even the siwtch port. i had a couple of bad ports on my cisco 2950's go bad on me before.
i've had similar problems with a bad (damged) nic or a broken driver.
To check the cabling connect some other device to the place where you have s/390 unit and see the data rate.

4.- The port where s/390 is connected presents CRC errors (51144 in 1 day)

CRC and Alignment errors are usually indicative of a duplex mismatch.  On servers, IMHO, best practice is to nail everything at 100 Mbps Full Duplex (assuming 100 Mbps).  I don't like to rely on autonegotiate working properly for servers.  Or make sure it's Auto on both sides if you have to use Autonegotiate.

It's strange though that between A and B is fine, and between B and server are fine.  If server is mismatched, then all clients should see an issue.

If server to switch is ok, then check machine A to its access switch - again either Auto on both sides or 100 full on both sides.

If that doesn't do it, string a cable on the floor from your server switch to the server and swap out the cable (when you can) to eliminate the cables inbetween.  Try different ports.  Try different NICs.  Could be environmental somewhere (high EFI or EMI).
jaccAuthor Commented:
OK, friends thank you very much for your comments.
I change the UTP cable and the data rate is good now.
I do not understand why, with some pcs it worked fine and with other no...... ??????????????????

Well , now everything is OK

thanks again
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
Networking Protocols

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.