Hi Everyone,
I have an annoying but quirky problem. I have a dell laptop with a broadcom
440x NIC and an intel wireless NIC.
Using the wired broadcom NIC, I copy data from a windows share in our domain
to the local machine which runs at around 400kb/s, but when I transfer data
to the server, it runs at normal speed.
Also, when I do the same with the wireless intel NIC, the copy from and to
runs at normal speed.
When I use the broadcom nic to copy data from a samba share, or a non domain
windows share, the speed is normal.
I decided to dive into the network monitor to see if something lit up. And
what I noticed is when I copy data from the domain share to the local
computer using the broadcom nic, I this pattern.
13 16.763528 0015C56B19AD LOCAL SMB C read & X, FID = 0x4005, Read 0xf000 at
0x00188000 RIVLAP1001 BACKUP-2003 IP
14 16.763528 LOCAL 0015C56B19AD SMB R read & X, Read 0xf000 BACKUP-2003
RIVLAP1001 IP
15 16.763528 LOCAL 0015C56B19AD NBT SS: Session Message Cont., 1460 Bytes
BACKUP-2003 RIVLAP1001 IP
16 16.763528 0015C56B19AD LOCAL TCP Control Bits: .A...., len: 0,
seq:2003849037-2003849037, ack: 330310363, win:65535, src: 2287 dst: 445
RIVLAP1001 BACKUP-2003 IP
17 16.763528 LOCAL 0015C56B19AD NBT SS: Session Message Cont., 1460 Bytes
BACKUP-2003 RIVLAP1001 IP
18 16.763528 LOCAL 0015C56B19AD NBT SS: Session Message Cont., 1460 Bytes
BACKUP-2003 RIVLAP1001 IP
......
253 17.857278 0015C56B19AD LOCAL SMB C read & X, FID = 0x4005, Read 0x1000
at 0x001B7000 RIVLAP1001 BACKUP-2003 IP
254 17.857278 LOCAL 0015C56B19AD SMB R read & X, Read 0x1000 BACKUP-2003
RIVLAP1001 IP
255 17.857278 LOCAL 0015C56B19AD NBT SS: Session Message Cont., 1460 Bytes
BACKUP-2003 RIVLAP1001 IP
256 17.857278 LOCAL 0015C56B19AD NBT SS: Session Message Cont., 1240 Bytes
BACKUP-2003 RIVLAP1001 IP
It has the SMB C read & X, FID and SMB R read & X, Read packets between 10 -
200 packets.
Then I uploaded data to the server via the broadcom nic, and these messages
were much less frequent.
This is also a fresh XP SP2 install with only the latest NIC drivers
installed. It was also happening on an XP SP3 install with all the latest
updates and drivers.
Does anyone know what the issue here is?
Thank you for any replies!
|