Home All Groups Group Topic Archive Search About
Author
11 Feb 2009 4:40 AM
Mark C.
Let me try this again, typed this all out and it kicked it out with an
error.....i have a server 2003, on a domain, 10 workstations, with a given
number sharing printers. All workstations are windows xp pro, mix of service
pack 2, upgraded service pack 3, and built on service pack 3.  On some
systems the list in directory, is not an option when installing the printer,
but on some can still browse or run the unc name and see the printer,  1
system, service pack 2, installed a new printer, list in directory works
great, all systems can attach, on a upgraded to service pack 3 system, list
in directory is not an option, can not access it from any workstation.  Im
also going to have to rename the systems from specific names to generic work
functions, for ex   workstation name, outside-sale, username quote.  There
are only 10 workstations, so at any given system only 9 others are attaching,
so i know im not exceeding the 10 connection limit....any suggestions???

Author
11 Feb 2009 4:39 PM
Robert L. (MS-MVP)
If you have a domain, you should not be limited to 10 connections. Dose she
printer come with Ethernet or you connect it to the server?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
Show quoteHide quote
"Mark C." <Ma***@discussions.microsoft.com> wrote in message
news:B0DFEAB6-15AE-428D-878E-8082018FF9AD@microsoft.com...
> Let me try this again, typed this all out and it kicked it out with an
> error.....i have a server 2003, on a domain, 10 workstations, with a given
> number sharing printers. All workstations are windows xp pro, mix of
> service
> pack 2, upgraded service pack 3, and built on service pack 3.  On some
> systems the list in directory, is not an option when installing the
> printer,
> but on some can still browse or run the unc name and see the printer,  1
> system, service pack 2, installed a new printer, list in directory works
> great, all systems can attach, on a upgraded to service pack 3 system,
> list
> in directory is not an option, can not access it from any workstation.  Im
> also going to have to rename the systems from specific names to generic
> work
> functions, for ex   workstation name, outside-sale, username quote.  There
> are only 10 workstations, so at any given system only 9 others are
> attaching,
> so i know im not exceeding the 10 connection limit....any suggestions???
Author
12 Feb 2009 2:25 PM
Lanwench [MVP - Exchange]
Robert L. (MS-MVP) <findem***@chicagotech.net> wrote:
Show quoteHide quote
> If you have a domain, you should not be limited to 10 connections.
> Dose she printer come with Ethernet or you connect it to the server?
>
>> Let me try this again, typed this all out and it kicked it out with
>> an error.....i have a server 2003, on a domain, 10 workstations,
>> with a given number sharing printers. All workstations are windows
>> xp pro, mix of service
>> pack 2, upgraded service pack 3, and built on service pack 3.  On
>> some systems the list in directory, is not an option when installing
>> the printer,
>> but on some can still browse or run the unc name and see the
>> printer,  1 system, service pack 2, installed a new printer, list in
>> directory works great, all systems can attach, on a upgraded to
>> service pack 3 system, list
>> in directory is not an option, can not access it from any
>> workstation.  Im also going to have to rename the systems from
>> specific names to generic work
>> functions, for ex   workstation name, outside-sale, username quote. There
>> are only 10 workstations, so at any given system only 9 others
>> are attaching,
>> so i know im not exceeding the 10 connection limit....any
>> suggestions???

Yes - there's no 10-connection limit unless the print server is running
WinXP Pro. Additionally, note that SBS questions should be posted in
microsoft.public.windows.server.sbs. I find the OP's post a bit unclear and
suspect more details may be required.
Author
18 Feb 2009 11:58 AM
Mark C.
They are local printers on the workstations to be shared on the
network...thats what im referring to about 10 connections, they are not
ethernet attached, print server attached or connected to the server.   There
are about 6 printers throughout the network locally attached to the
workstations either parallel or usb

Show quoteHide quote
"Robert L. (MS-MVP)" wrote:

> If you have a domain, you should not be limited to 10 connections. Dose she
> printer come with Ethernet or you connect it to the server?
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Mark C." <Ma***@discussions.microsoft.com> wrote in message
> news:B0DFEAB6-15AE-428D-878E-8082018FF9AD@microsoft.com...
> > Let me try this again, typed this all out and it kicked it out with an
> > error.....i have a server 2003, on a domain, 10 workstations, with a given
> > number sharing printers. All workstations are windows xp pro, mix of
> > service
> > pack 2, upgraded service pack 3, and built on service pack 3.  On some
> > systems the list in directory, is not an option when installing the
> > printer,
> > but on some can still browse or run the unc name and see the printer,  1
> > system, service pack 2, installed a new printer, list in directory works
> > great, all systems can attach, on a upgraded to service pack 3 system,
> > list
> > in directory is not an option, can not access it from any workstation.  Im
> > also going to have to rename the systems from specific names to generic
> > work
> > functions, for ex   workstation name, outside-sale, username quote.  There
> > are only 10 workstations, so at any given system only 9 others are
> > attaching,
> > so i know im not exceeding the 10 connection limit....any suggestions???
>
>
Author
19 Feb 2009 12:22 AM
Lanwench [MVP - Exchange]
Mark C. <Ma***@discussions.microsoft.com> wrote:
> They are local printers on the workstations to be shared on the
> network...thats what im referring to about 10 connections, they are
> not ethernet attached, print server attached or connected to the
> server.   There are about 6 printers throughout the network locally
> attached to the workstations either parallel or usb
>

Ah. My advice? Don't share them. Share networkable printers only.


Show quoteHide quote
> "Robert L. (MS-MVP)" wrote:
>
>> If you have a domain, you should not be limited to 10 connections.
>> Dose she printer come with Ethernet or you connect it to the server?
>>
>> --
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting on
>> http://www.ChicagoTech.net
>> How to Setup Windows, Network, VPN & Remote Access on
>> http://www.HowToNetworking.com
>> "Mark C." <Ma***@discussions.microsoft.com> wrote in message
>> news:B0DFEAB6-15AE-428D-878E-8082018FF9AD@microsoft.com...
>>> Let me try this again, typed this all out and it kicked it out with
>>> an error.....i have a server 2003, on a domain, 10 workstations,
>>> with a given number sharing printers. All workstations are windows
>>> xp pro, mix of service
>>> pack 2, upgraded service pack 3, and built on service pack 3.  On
>>> some systems the list in directory, is not an option when
>>> installing the printer,
>>> but on some can still browse or run the unc name and see the
>>> printer,  1 system, service pack 2, installed a new printer, list
>>> in directory works great, all systems can attach, on a upgraded to
>>> service pack 3 system, list
>>> in directory is not an option, can not access it from any
>>> workstation.  Im also going to have to rename the systems from
>>> specific names to generic work
>>> functions, for ex   workstation name, outside-sale, username quote.
>>> There are only 10 workstations, so at any given system only 9
>>> others are attaching,
>>> so i know im not exceeding the 10 connection limit....any
>>> suggestions???