Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Slow\s+restore\s+for\s+large\s+NT\s+client\.\.\s+help\!\s*$/: 4 ]

Total 4 documents matching your query.

1. Slow restore for large NT client.. help! (score: 1)
Author: Jeff Connor <connorj AT NIAGARAMOHAWK DOT COM>
Date: Wed, 13 Sep 2000 13:20:03 -0400
We are in the process of restoring a subdirectory of a very large NT client file space (D:) and it is running really slow. I thought I'd see if any of you have some ideas as to where we can look for
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-09/msg00451.html (12,713 bytes)

2. Re: Slow restore for large NT client.. help! (score: 1)
Author: Lisa Cabanas <CABANL AT MAIL.MODOT.STATE.MO DOT US>
Date: Wed, 13 Sep 2000 14:09:25 -0500
Jeff, Have you tried pinging with different packet sizes to see what the MSS is set to on the switches/ atm fabric? How well do ftps perform? How fast does an nslookup resolve both ways? What does a
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-09/msg00464.html (14,555 bytes)

3. Re: Slow restore for large NT client.. help! (score: 1)
Author: Richard Sims <rbs AT BU DOT EDU>
Date: Wed, 13 Sep 2000 15:34:24 -0400
Jeff - Lisa's insightful response made me think of something... You say you are using 100Mbit Ethernet. A gotcha in that area to make sure of is that your adapter cards are not set for Auto Negotiati
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-09/msg00469.html (10,948 bytes)

4. Re: Slow restore for large NT client.. help! (score: 1)
Author: Jeff Connor <connorj AT NIAGARAMOHAWK DOT COM>
Date: Wed, 13 Sep 2000 16:02:50 -0400
Thanks Lisa and Richard. The assertion by our Network group that the communications pipe is ok is based on the packet trace using a sniffer. The frame size for most packets it 1514, according to the
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-09/msg00471.html (13,185 bytes)


This search system is powered by Namazu