Does the client File and Print exception pertain to the local subnet or all
subnets?
I recall a bug in SP1 where there was an issue when all subnets were open
but the spooler could still fall back to polling mode, but with a quick
check, I did not find the specifics. Enable the exception for all subnets,
close the remote window, stop start client spooler, open the remote
printers folder. You will need to restart the spooler since once the
spooler gets into a communication mode it stays in that mode to that server
until a restart.
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike M" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Alan,
>
> Thank you for your quick reply!
>
> No firewalls are enabled on the print servers, however by turning off the
> firewall on the XP client, this nagging issue is gone.
>
> File & Printer sharing is in the exception list for that XP client in
> question. Why would the client's firewall get in the way of this?
> <scratching head>
>
>
> Thank you again,
> Mike
>
>
>
>
>> Yes, the client spooler is in polling mode.
>>
>> There are several things that can cause this but most likely the client
>> has a firewall turned on and the File and Print sharing ports are not
>> enabled.
>>
>> Enable the File and Printer exception in the firewall. Close the remote
>> window to the print server. Stop the client spooler service, start the
>> client spooler service, then reopen the remote folder.
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>
>