SLLLOOWW data transfer from Win98 to Win2000 Pro

[Tracy L. Baker]

Existing network, with Win98 machines and a WinNT 4.0 SP6
domain server. Recently installed two identical Dell
boxes with Win2000 Professional to replace two Win98
machines. Remaining existing machines still have Win98.

Copying a 26mb file from Win98 to Win98 takes < 10 seconds.

Copy same file to Dell #1 takes about 3 minutes.

Copying to Dell #2 takes 13 minutes. (We wish to actually
copy over 4Gb of data, but that takes HOURS -- 6-8 hours!)

We have noticed that the copying to Dell #2 is *much*
faster if it takes pace BEFORE the Win98 machine logs into
the domain. After it logs in, there is a dramatic speed
decrease.

Are running Symantec AV v8.1 with real time file scanning
turned off.

Other notes:
- Both Dells have built-in Intel 1000MT adapters.
- Dell #1 was much slower as well, until a 3Com 3C905 NIC
was put into it.
- Dell #2 now has a Kingston adapter, with no change in
speed.
- Trying different ports on the Netgear switch had no
impact.
- Changing Cat5 patch cables had no impact.
- Changing Dell #2's adapter's (both the Intel and the
Kingston) to 100mb full-duplex (vice auto) had no impact.
- The copying is taking place by navigating through My
Network Places on Dell #2, finding the Win98 box, clicking
on its C: drive, entering the full access password, going
to the appropriate folder, highlighting and CTRL-C on the
file, then going to the proper copy location on the
Win2000 Pro machine (Dell #2) and pressing CTRL-V.

Any help as to why this may be happening? (I know, I
know -- I could put in a 3Com card into Dell #2, but that
doesn't address the root issue.)

Thanks in advance, and I'd really appreciate a response
sent to (e-mail address removed)

 

[Marina Roos]

Check the ipconfig/all from the clients. Does everything point to your
server-IP?

Marina

 

[Tracy L. Baker]

-----Original Message-----
Check the ipconfig/all from the clients. Does everything point to your
server-IP?

This shouldn't be necessary since I'm trying to copy
files from one client to another -- not between client
and server. (Unless I'm missing the point of your
answer, that is...)

 

[Marina Roos]

It still can be of importance. So, does it point to the server-IP or not?

Marina

 

[Tracy Baker]

I haven't had time to check... But I will tomorrow.

What, exactly should "pointing to the server IP"? WINS, DNS, DHCP,
Gateway...?

I'm sorry to seem dense on this -- but until this cropped up on this
one PC, I've not seen this problem.

It is interesting to note that, when I checked a Win2000 Pro client
here in my shop, the only IP entry that pointed to a server was WINS.
On my shop client, however, it was pointing to the OLD server -- I'd
forgotten to change its WINS server IP address to the new server's IP
until this morning. The interesting part is that it didn't have a
problem anyway...

Also, please remember that there is a second identical PC, with an
identical setup (wellll the IP's and computer name are different),
that does not exhibit this problem.

 

[Marina Roos]

Normally about everything should be pointing to your server-IP.
How many nics in the server?
Else just post the ipconfig/all from the server and the client.

Marina

 

[Tracy Baker]

I will, just as soon as I revisit my client.

Please keep in mind that the issue is copying a file via the network
FROM a Win98 client PC TO a Win200 Pro client PC.

They are both logged into a WinNT 4.0 SP6 server domain.

In this situation, one would assume that the server doesn't impact the
copying of a file from one client to another.

Also, the copying process slows dramatically AFTER the Win98 client
logs into the WinNT's domain. (by a factor of 4)

Also, pointing my DNS addressing on my clients to my internal WinNT
server (as you've suggested in other posts) doesn't make any sense,
since the WinNT server does not do any name resolution for the
internal LAN. (It most likely does not even have any DNS services
loaded.) So, if I were to do point my clients' DNS IPs to the WinNT
server's IP, how are the clients' supposed to get name resolution for
internet sites?

 

[Marina Roos]

Normally, Gateway, DHCP, DNS and WINS should be pointing to your server-IP.
Doesn't matter if the NT4 server has DNS-server installed.
Do you have options 003, 006, 044 and 046 (0x8) in DHCP-server, Scope
options?

marina

 

[Tracy Baker]

No, because DHCP is also not enabled on the WINNT server. Everything
in the LAN uses a static IP address (and subnet, gateway, DNS
addresses).

And again, how is internet name resolution supposed to work for the
client PCs if they're pointed to the internal WinNT server's IP
address -- and it isn't doing any name resolution itself? DHCP?
That's not needed in this installation...

There is a "router" in the installation - a LinkSys I believe (I
didn't install it), that *can* act as a DHCP server. But again,
everything is static, so it isn't used...

 

[Marina Roos]

Tracy,

DHCP-server really is a nobrainer.
Just make sure that the client is pointing to the server-IP for DNS, WINS
and Gateway.
WINS is needed for the name resolution.
Make sure that netbios over TCP/IP is enabled.

Marina