Print Management MMC

Hello,

We are working on deploying a new MS Win2k3 R2 Print Server. We have been
administering it from Windows Vista. We frequently have problems connecting
the Print Management MMC to the server. When you launch the MMC, it
connects to the Print Server and you can list the drivers installed on the
server, the forms, and even ports. The list of printers is blank. You can
browse to the \\servername and it displays all the shared printers (about
100). You can even add a new printer in the MMC. The new printer won't
show up in the MMC but you can browse out to install it via the share and it
works. No errors are reported. It happens with the Windows Vista Firewall
service running or disabled.

Has anyone else seen a similar issue? If so, have you found a solution?

Thanks,

Peter J.
Boise State Help Desk

 

Check the number of connections to the client. XP and Vista clients can
only have 10 connections. Use the MMC snapin Shared Folders / Shares. If
the IPC$ share is 10 the spooler from the server cannot connect back to the
client.

If the client machine has printer connections to multiple Server 2003
machines, each server connection will take up one IPC$ back to the client.

For the Firewall setting, make sure that the scope is configured for all
computers not just the local subnet. If you already have a connection to
the server, you will need to restart the spooler on the client and allow the
machines to reconnect with the new mode.



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"Boise State Help Desk" <HelpDesk+BoiseState@newsgroup.nospam> wrote in
message news:uS4RGvpyJHA.2324@TK2MSFTNGP06.phx.gbl...
> Hello,
>
> We are working on deploying a new MS Win2k3 R2 Print Server. We have been
> administering it from Windows Vista. We frequently have problems
> connecting the Print Management MMC to the server. When you launch the
> MMC, it connects to the Print Server and you can list the drivers
> installed on the server, the forms, and even ports. The list of printers
> is blank. You can browse to the \\servername and it displays all the
> shared printers (about 100). You can even add a new printer in the MMC.
> The new printer won't show up in the MMC but you can browse out to install
> it via the share and it works. No errors are reported. It happens with
> the Windows Vista Firewall service running or disabled.
>
> Has anyone else seen a similar issue? If so, have you found a solution?
>
> Thanks,
>
> Peter J.
> Boise State Help Desk
>
>

 

Alan,

Thank you for the response but I am not 100% sure I understand it. The
printer server with Windows Server 2003 R2 should have unlimited
connections. If I understand your information, you stated that it is
possible to use up the client's 10 connections by connecting to several
print servers. We currently only have 1 MS Print server. I am failing to
account for all 10 connections on the client side at this point. Can you
point me to a tool or command line to check on the number of connections?

Peter

"Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
news:u2fLdbryJHA.4800@TK2MSFTNGP06.phx.gbl...
> Check the number of connections to the client. XP and Vista clients can
> only have 10 connections. Use the MMC snapin Shared Folders / Shares. If
> the IPC$ share is 10 the spooler from the server cannot connect back to
> the client.
>
> If the client machine has printer connections to multiple Server 2003
> machines, each server connection will take up one IPC$ back to the client.
>
> For the Firewall setting, make sure that the scope is configured for all
> computers not just the local subnet. If you already have a connection to
> the server, you will need to restart the spooler on the client and allow
> the machines to reconnect with the new mode.
>
>
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Boise State Help Desk" <HelpDesk+BoiseState@newsgroup.nospam> wrote in
> message news:uS4RGvpyJHA.2324@TK2MSFTNGP06.phx.gbl...
>> Hello,
>>
>> We are working on deploying a new MS Win2k3 R2 Print Server. We have
>> been administering it from Windows Vista. We frequently have problems
>> connecting the Print Management MMC to the server. When you launch the
>> MMC, it connects to the Print Server and you can list the drivers
>> installed on the server, the forms, and even ports. The list of printers
>> is blank. You can browse to the \\servername and it displays all the
>> shared printers (about 100). You can even add a new printer in the MMC.
>> The new printer won't show up in the MMC but you can browse out to
>> install it via the share and it works. No errors are reported. It
>> happens with the Windows Vista Firewall service running or disabled.
>>
>> Has anyone else seen a similar issue? If so, have you found a solution?
>>
>> Thanks,
>>
>> Peter J.
>> Boise State Help Desk
>>
>>
>
>

 

here's the KB on this
http://support.microsoft.com/kb/954377

do not add the MaxRPCSize setting to the print server unless it is running
Windows 2000

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
news:u2fLdbryJHA.4800@TK2MSFTNGP06.phx.gbl...
> Check the number of connections to the client. XP and Vista clients can
> only have 10 connections. Use the MMC snapin Shared Folders / Shares. If
> the IPC$ share is 10 the spooler from the server cannot connect back to
> the client.
>
> If the client machine has printer connections to multiple Server 2003
> machines, each server connection will take up one IPC$ back to the client.
>
> For the Firewall setting, make sure that the scope is configured for all
> computers not just the local subnet. If you already have a connection to
> the server, you will need to restart the spooler on the client and allow
> the machines to reconnect with the new mode.
>
>
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Boise State Help Desk" <HelpDesk+BoiseState@newsgroup.nospam> wrote in
> message news:uS4RGvpyJHA.2324@TK2MSFTNGP06.phx.gbl...
>> Hello,
>>
>> We are working on deploying a new MS Win2k3 R2 Print Server. We have
>> been administering it from Windows Vista. We frequently have problems
>> connecting the Print Management MMC to the server. When you launch the
>> MMC, it connects to the Print Server and you can list the drivers
>> installed on the server, the forms, and even ports. The list of printers
>> is blank. You can browse to the \\servername and it displays all the
>> shared printers (about 100). You can even add a new printer in the MMC.
>> The new printer won't show up in the MMC but you can browse out to
>> install it via the share and it works. No errors are reported. It
>> happens with the Windows Vista Firewall service running or disabled.
>>
>> Has anyone else seen a similar issue? If so, have you found a solution?
>>
>> Thanks,
>>
>> Peter J.
>> Boise State Help Desk
>>
>>
>
>

 

You said you were having problem managing the server using Vista which has
the 10 connection limit. Server 2003 R2 or Server 2008 is the platform you
would use when monitoring many print servers remotely.

net sess will list the current connections through the server service on any
windows machine.

net sess

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"Boise State Help Desk" <HelpDesk+BoiseState@newsgroup.nospam> wrote in
message news:up8QupYzJHA.4800@TK2MSFTNGP06.phx.gbl...
> Alan,
>
> Thank you for the response but I am not 100% sure I understand it. The
> printer server with Windows Server 2003 R2 should have unlimited
> connections. If I understand your information, you stated that it is
> possible to use up the client's 10 connections by connecting to several
> print servers. We currently only have 1 MS Print server. I am failing
> to account for all 10 connections on the client side at this point. Can
> you point me to a tool or command line to check on the number of
> connections?
>
> Peter
>
> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
> news:u2fLdbryJHA.4800@TK2MSFTNGP06.phx.gbl...
>> Check the number of connections to the client. XP and Vista clients can
>> only have 10 connections. Use the MMC snapin Shared Folders / Shares.
>> If the IPC$ share is 10 the spooler from the server cannot connect back
>> to the client.
>>
>> If the client machine has printer connections to multiple Server 2003
>> machines, each server connection will take up one IPC$ back to the
>> client.
>>
>> For the Firewall setting, make sure that the scope is configured for all
>> computers not just the local subnet. If you already have a connection to
>> the server, you will need to restart the spooler on the client and allow
>> the machines to reconnect with the new mode.
>>
>>
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/search/?adv=1
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Boise State Help Desk" <HelpDesk+BoiseState@newsgroup.nospam> wrote in
>> message news:uS4RGvpyJHA.2324@TK2MSFTNGP06.phx.gbl...
>>> Hello,
>>>
>>> We are working on deploying a new MS Win2k3 R2 Print Server. We have
>>> been administering it from Windows Vista. We frequently have problems
>>> connecting the Print Management MMC to the server. When you launch the
>>> MMC, it connects to the Print Server and you can list the drivers
>>> installed on the server, the forms, and even ports. The list of
>>> printers is blank. You can browse to the \\servername and it displays
>>> all the shared printers (about 100). You can even add a new printer in
>>> the MMC. The new printer won't show up in the MMC but you can browse out
>>> to install it via the share and it works. No errors are reported. It
>>> happens with the Windows Vista Firewall service running or disabled.
>>>
>>> Has anyone else seen a similar issue? If so, have you found a solution?
>>>
>>> Thanks,
>>>
>>> Peter J.
>>> Boise State Help Desk
>>>
>>>
>>
>>