XP Share Enumeration VERY slow when accessing from Win2K machine.

F

Frank Domina

Everything used to be fine -- used to work flawlessly and fast. I think
(but cannot swear to it) that the following problem started only after
installing XP SP2.

SETUP (home use):
Workgroup (not domain)
Machine 1: XP Professional SP2
Machine 2: Windows2000 SP4

- Both machines are current with all of security updates.
- Both machines are using user-level share access.
- Accounts w/ same user names and passwords exist on both machines.

XP machine accessing 2000 machine works great. No problems there.

2000 machine going directly to a known share on XP (e.g. \\machine1\MyShare)
opens up just fine -- nice and fast.

2000 machine trying to get enumeration of shares on XP (e.g. \\machine1)
takes nearly a MINUTE to list the shares! Refreshing the list (F5) again
takes just as long! One I have the list, opening any share is
instantaneous.

2000 machine sharing remote printer attached to XP machine makes ANY
printing take forever. Clicking on Print in any application takes SEVERAL
MINUTES to display the default and list of available printers. Once it
finally comes up, printing then works fine.

I'm guessing that XP SP2 added some new security "feature" that is causing
Win2000 machines to have this issue. How can I get my speed back? Waiting
MINUTES to begin printing simply isn't acceptable.

THINGS I ALREADY TRIED:
1) Mapping a drive to C$ and "net use" of IPC$, hoping it would "hole
open" access.....did not help.
2) Tried allowing anonymous enumeration....did not help
3) Tried completely disabling XP firewall....did not help
4) Tried swearing and kicking....did not help (but did kinda feel good)

To reiterate / summarize
- Win2K direct access to a known XP share authenticates and works
instantaneous (no problem)
- Win2K enumeration of XP machine's shares and printers is pathetically
slow (big problem)

I sure hope someone can help me!

Regards,
Frank Domina
 
F

Frank in Atlanta

Please see post with subject "Very slow SHARE enumeration 2K-2K or 2K-XP"
instead.

That post supersedes this one. I found out more information and re-posted a
new message about the problem.

Thanks,
Frank
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top