XP very slow to write data in a W2k share

[Laurent Dumont]

Hello,
after many times exploring newsgroups, forums and Ms KB, without any answer,
I finaly submit you this case...

I certainly missed something....

Here is the case:

- 1 W2k sp4 server, AD domain member, 2 interfaces, 1 in AD side
(172.30.xx.xx), the other on a private subnet (a workgroup/192.168.xx.xx).
- 2 W2k sp4 workstations in the private subnet
- 2 XP sp2 workstations in the private subnet, i have to replace the W2k
with it....

These computers are link by a switch with all interfaces forced to 100Mb /
full duplex.
A local account is created on the 5 computers, as local user on
w<orkstations, and to grant permssions to the shares on the server.

On the workstations, a software reads files on the share, an operator modify
them, and they are rewrited on a another directory of the share.

Under W2k, everything seems to be ok, but under XP, the software becomes
very, very slow.

The hardware does not seems to be the trouble... The workstations are all
some Dell Precision Workstations 2Ghz for W2k and 3Ghz for XP, with intel
chipset for the lan.

When using "netperfs" to test the lan, i get between 75 and 85 Mb/s for a
100Mb/s link, so that's not so bad.
When testing FTP transfert, i get some equivalents résults under W2k and XP.

As soon as we use the windows copy system (event in command line), the XP
performances are falling.

I made some testing with command line tools for the resources kits:
- Creatfil, to have dummy files (512Ko, 1Mo, 10Mo, 100Mo)
- Timethis, to have running times.

Here is a shot details of tests:

- upload from server to XP => Ok (>68 Kb/s)
- download from XP client => Ok (>65Kb/s)

upload from W2k client => Ok (>60 Kb/s)
upload from XP client => NOT OK! (<35 Kb/s)

I saw many KB acticles, talking about SMB trafic (C/R transact - KB 330929),
or many other KB articles (885198 / 301952 / 311169 / 831129 / 825433 /
326826 / 328890 / 812661...), but no one seems to answer to my question.


Some news posts are talking about "Webclient" service, but it is not
significant.

I have to change theses W2k worstations, but it is not possible with so poor
performances, so any help would be appreciated

Thanks,

Laurent

 

[Mak]

Put _all_ interfaces to Auto / Auto for speed / duplex.

 

[Guest]

I also have similar problems with accessing files and printing from W2k
accessing a XP workstation with its printing resources shared and files
shared!

Where do I find or how do I set "Put_all_interfaces" that you talk about
below? How do I know what it is at the moment?

 

[Laurent Dumont]

Hello,
Alex, you can put all interfaces to auto speed and duplex or force it in a
specific speed/duplex by going in your network interface properties
(computer manager / devices manager / network cards or something like that,
i'm working on french OS).
For the switch, it depends on your equipment.


Mak, in my case, i've tried many combinations, the server and the W2k wks
are forced to 100/full, the switch interfaces are forced to.
For the XP wks, i get the betters performences by forcing everything to
100/full... So I it done, but do not solve the issue...

I'm waiting for other ideas, and no, it is not the QoS bandwith reservation
that is limiting...

Thanks,

Laurent

 

[Mak]

Laurent, you are missing the point here.
If you absolutelly need to force, instead of using standard Auto / Auto, you
will have to force to 100/Half.
Your 100/Full is not supported, wrong settings, duplex mismatch.
From the disription of your problem: ftp works, test works, real world -
doesn't (if you would use IPX - it will work too, IPX is more forgiven to
duplex mismatch).

You have to set NIC - switch port - switch port - NIC to Auto / Auto - have
you tried that yet?

 

[Laurent Dumont]

Hello;
I still thinking that it might be an issue between the server, acting as a
domain member, and the XP wks, that is only a workgroup member...

Any ideas about that?

Thanks,
Laurent

 

[Laurent Dumont]

Hello,
actually here is the situation:

Server NIC | Switch Port | Switch Port | Workstation
100/full | 100/Full | 100/Full | W2k 100/Full
=> I can not change it, and it works fine

Here are the tests for XP workstation:

| Auto/Auto | Auto/Auto
Case1
| Auto/Auto | 100/Full
Case 2
| Auto/Auto | 100/Half
3
| Auto/Auto | 1Gb/Full
4

| 100/Full | Auto/Auto
5
| 100/Full | 100/Full
6

| 100/half | Auto/Auto
7
| 100/half | 100/half
8

| 1Gb/Full | Auto/Auto
9
| 1Gb/Full | 1Gb/Full
Case 10

Case 1 2 3 4 5
6 7 8 9 10
Create file 23,37 19,83 18,66 16,37 13,64 16,82
17,50 14,78 16,30 10,94
Upload file 34,74 5,78 48,67 33,91 14,76 48,76
50,83 45,04 32,98 32,07
Download file 58,78 0,38 42,59 36,26 33,21 39,51
38,88 38,62 36,10 30,35

All results are in Mb/s

Sorry for the display, but it is not easy

I also had collisions in case 2, Deferred Tx in cases 2,3,7,8 and Rx errors
in cases 3,5,7,8.

The switch is a procurve 2824 (j4903a / i.08.62) and the lan adapter is an
intel 1000MT (built in).

In all cases, the creatfil.exe process is under the 25Mb/s.

If you have any ideas....

Thanks,
Laurent

 

[Mak]

Hi Laurent,
in-line replies:

Hello,
actually here is the situation:

Server NIC | Switch Port | Switch Port | Workstation
100/full | 100/Full | 100/Full | W2k 100/Full =>
I can not change it, and it works fine

Curious: why can't you change that? Obviously someone did, default is Auto /
Auto.
You can run the test NIC - switch port - switch port - NIC between 2 XP
machines (from your original post you have 2 of them).
Auto should perform somewhat better in this case, you have 1Gbit/s switch
and NICs (cables are OK too I hope).

Here are the tests for XP workstation:

| Auto/Auto | Auto/Auto
Case1
| Auto/Auto | 100/Full
Case 2
| Auto/Auto | 100/Half 3
| Auto/Auto | 1Gb/Full 4

| 100/Full | Auto/Auto
5
| 100/Full | 100/Full 6

| 100/half | Auto/Auto
7
| 100/half | 100/half 8

| 1Gb/Full | Auto/Auto
9
| 1Gb/Full | 1Gb/Full
Case 10

Case 1 2 3 4 5 6
7 8 9 10
Create file 23,37 19,83 18,66 16,37 13,64 16,82
17,50 14,78 16,30 10,94
Upload file 34,74 5,78 48,67 33,91 14,76
48,76 50,83 45,04 32,98 32,07
Download file 58,78 0,38 42,59 36,26 33,21 39,51
38,88 38,62 36,10 30,35

All results are in Mb/s

Sorry for the display, but it is not easy

not to worry, it's fine

I also had collisions in case 2, Deferred Tx in cases 2,3,7,8 and Rx
errors in cases 3,5,7,8.

I see some variations (as expected in tests), but 3, 7 and 8 for example
should (theoretically) produce 'same' (within test variation margin)
results.
Forcing 100/Full is not supported, as I said in IEEE standard, forcing
1Gbit/s is not even mentioned, exchange capabilities between 2 partners on
1Gbit/s must happen only in Auto detect (or subset - Auto-negotiate to
accept only 1Gbit/s partner): - hence, tests 9 and 10 are sort of 'not
needed', because it's not designed to work in 'this' condition.

You might want to copy large file / bunch of small files from machine to
machine. One note on Auto: it is fully hardware, no driver involved, whether
when you set something manually, negotiation restarts, according to the
driver (your XP driver might be different to 2k).

 

[Laurent Dumont]

Thank you Mak for your answers,
For the server and the W2k workstation, i can change parameters, but they
are very high use computers, and very importants for us... Peoples that
working with that will not be able to undertand that i have some test to do,
because they said "it work now, it's XP that doest not work!"
So I do what I can do...

Im' trying other files transferts, and i will let you know.

Laurent

 

[Mak]

OK. I have one question: what's with this number: "In all cases, the
creatfil.exe process is under the 25Mb/s." ?
What is it BTW, MByte per sec or Mbit per sec? (would be very strange if it
is Mega Byte, but I'll let you explain first). And why it has to be 25?