Re: XP-SP2 causing memory leak on network printing?

[Dawn Anastasi]

We're getting this problem at our work too. Our office all uses XP
and the problem started occurring after SP2 was applied. The printers
use static IP addresses but the workstations are using DHCP. It would
take a lot of work to manually assign all IP addresses. I would think
that there would be a patch of some sort if so many people are having
this problem.

Dawn



"Interrogative" > wrote in message >...
> "deilenberger" > wrote in message
> ...
> > Folks,
> >
> > I've installed SP2 on about 6 machines at work (total network is about 25
> > machines and several W2K servers). On machines that are printing to our
> > high-volume printers, the users are experiencing problems.
> >
> > The problem manifests itself with an extreme slowdown of the printing.
>
> I have found that auto assigned internal IP addresses slows things down as
> the share takes a while to be found. Have you got a printer with it's own IP
> address? If so, assign it one manually. Is your entire network auto
> assigned? If so, assign manually. That is the way I brought my network
> printing back to normal.
>
> The above assumes it isn't just some physical prob somewhere. Eg, a NIC that
> is dying and bombarding the network with spurious crap thus slowing it all
> down.

[Interrogative]

"Dawn Anastasi" > wrote in message
m...
> We're getting this problem at our work too. Our office all uses XP
> and the problem started occurring after SP2 was applied. The printers
> use static IP addresses but the workstations are using DHCP. It would
> take a lot of work to manually assign all IP addresses. I would think
> that there would be a patch of some sort if so many people are having
> this problem.
>

I am sorry that it would take a lot of work for you. I can only assume your
work network must be enormous because per machine it should take only about
a minute assuming the machine is running normally. However, if you have 2000
XP machines, 2000 minutes is a lot of time! :)

The thing that should have been noted by your people who do the networking,
though, is that XP is and always has been slow to react on a network if left
auto. When XP first came out, I noticed that the first day, got sick of it
and manually assigned. Adding XP machines over time since was only a "1 at a
time" manual assign for me so no big deal. Your people should have been
doing that as well. However, now that it is where it is, perhaps your people
SHOULD be investing the time now so that in the future, everyone will be a
lot happier.