NW server drops when large data copy using Win2k adv. Svr

  • Thread starter Thread starter netware
  • Start date Start date
N

netware

Hi,

When I copy a lot of data ( 60 gigs, xcopy) from one computer to the
netware server using the Windows 2000 Adv. Server console, the Win
server looses connectivity to the NW server (can't ping DNS name, all
netware mapped drives (i.e. F, Z) are no longer reachable, and xcopy
errors with message that it can't write because the destination drive
is no longer
available.

The problem consitently occurs when run from the Win server; however,
the errors occur at different times during the copy. That is, the error
does not always occur when the same files are copied.

When I break the xcopy command to copy one directory at a time, I get
no errors. The q:\files subdir contains about 20 directories.

When I use a different XP workstation to execute the batch file, I do
not receive the connectivity errors.

batch file: xcopy q:\files\*.* f:\files /d /s /e /i /c /r /h /y

NW 6.5 new install
Windows 2000 Advanced Server sp4, clean install
Source workstation is XP machine

NW server and Win server are on same switch (3com 3870)
XP machine is off yonder connected with gigabit ethernet.

Q: is mapped to XP source machine
F: is mapped to SYS on NW server



I execute the batch file from the Win server

Windows 2000 server also runs: DNS, DHCP, WINS
Running Active Directory on Win server

NW client 4.91 is installed on Windows server, SLP is static

NW server has Scoped SLP and is the only DA
DNS for DA is SLP1 and it resolves correctly

Both servers have one dual-port Intel Pro/1000MT NIC. Both ports are
teamed (802.3ad)

If anyone knows what would cause the loss of communication, let me
know.
thanks,
Craig
 
Usually the "mapped drive loosing connection" is a symptom of the computer
having an incorrect secondary DNS server listed. Most of the time it's an
ISP's DNS server. What DNS server are you using for secondary on your
network?


hth
DDS W 2k MVP MCSE
 
Ah, ha. There is no secondary on the Win server, but there is a
secondary on the successful xp machine and that secondary is the ISP's
DNS. If I put the ISPs DNS as secondary or should I have an internal
secondary DNS?
 
You should have a DNS server that is set up for the AD domain in the primary
and secondary DNS settings. You should never have your ISP's DNS server on
any AD client. The only place the ISP's DNS server should be listed is as a
forwarder on the DNS server set up for the AD domain.

hth
DDS W 2k MVP MCSE
 
Back
Top