M
Martin
Hi,
Have a network with around 1000 mostly XP clients. A
mix of NT4 and W2000 servers. The primary network print
server is a 2000 server system (SP4) with around 70
printers defined (including some LPD).
When choosing to add a new network printer from an XP
client machine and clicking the "browse" option in the
wizard (We have no AD), the searching.. dialog opens and
takes around 10 minutes to return a list of printers -
which is unusably long for most users. What is strange
is that browing for printers from the same client machine
via the "entire network" or using start-->run
\\printserver format is instantaneous. This would seem
to rule out any browsing issues.
WINS is in use - but have been unable to find any
problems with the configuration that may be affecting
browsing - I understand that client machines use an RPC
to ENUM printers from the browse master (for the segment -
or domain master browser??) I guess it is this process
that is running slowly - but why?
The network itself is very quick based on Foundary kit
with Multi gigabit backbone and 100MB/s to desktops.
Any suggestions on how to improve this printer browsing
problem or is this just "that way it is"???
Regards.
Have a network with around 1000 mostly XP clients. A
mix of NT4 and W2000 servers. The primary network print
server is a 2000 server system (SP4) with around 70
printers defined (including some LPD).
When choosing to add a new network printer from an XP
client machine and clicking the "browse" option in the
wizard (We have no AD), the searching.. dialog opens and
takes around 10 minutes to return a list of printers -
which is unusably long for most users. What is strange
is that browing for printers from the same client machine
via the "entire network" or using start-->run
\\printserver format is instantaneous. This would seem
to rule out any browsing issues.
WINS is in use - but have been unable to find any
problems with the configuration that may be affecting
browsing - I understand that client machines use an RPC
to ENUM printers from the browse master (for the segment -
or domain master browser??) I guess it is this process
that is running slowly - but why?
The network itself is very quick based on Foundary kit
with Multi gigabit backbone and 100MB/s to desktops.
Any suggestions on how to improve this printer browsing
problem or is this just "that way it is"???
Regards.