XP Pro Workstations
 

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???

XP Pro Workstations
 

Mark C. wrote:
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???

My suggestion is, don't share anything on workstations. Not files, and not
printers. The only printers you should share are true network printers with
print servers - and you should share those from a centralized server. It's
not worth the headache to do it the way you're trying to do it, seriously.
Print servers (and new printers with integrated print servers) are pretty
cheap nowadays.

XP Pro Workstations
 

Mark C. wrote:
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???

My suggestion is, don't share anything on workstations. Not files, and not
printers. The only printers you should share are true network printers with
print servers - and you should share those from a centralized server. It's
not worth the headache to do it the way you're trying to do it, seriously.
Print servers (and new printers with integrated print servers) are pretty
cheap nowadays.

XP Pro Workstations
 

Agree. If possible look for an 'n' model with a builtin RJ45 port. Although,
an add-on network box is an alternative. Use the TCP/IP or LPR printing
protocols, these are simple to setup and communicate direct to the printer,
avoiding extra server loading. Also they are are unaffected by username or
password changes (which is always an issue with peer-shared printers, change
your logon password and printers stop working all over the place, end result
of which is that no-one dares change their password!)

Also for business use avoid inkjets. Apart from sky-high running costs,
inkjets are typically deigned for direct printing from the computer, and are
problematic when networked. Lasers are the way to go.

"Lanwench [MVP - Exchange]" wrote:


My suggestion is, don't share anything on workstations. Not files, and not
printers. The only printers you should share are true network printers with
print servers - and you should share those from a centralized server. It's
not worth the headache to do it the way you're trying to do it, seriously.
Print servers (and new printers with integrated print servers) are pretty
cheap nowadays.

XP Pro Workstations
 

Agree. If possible look for an 'n' model with a builtin RJ45 port. Although,
an add-on network box is an alternative. Use the TCP/IP or LPR printing
protocols, these are simple to setup and communicate direct to the printer,
avoiding extra server loading. Also they are are unaffected by username or
password changes (which is always an issue with peer-shared printers, change
your logon password and printers stop working all over the place, end result
of which is that no-one dares change their password!)

Also for business use avoid inkjets. Apart from sky-high running costs,
inkjets are typically deigned for direct printing from the computer, and are
problematic when networked. Lasers are the way to go.

"Lanwench [MVP - Exchange]" wrote:


My suggestion is, don't share anything on workstations. Not files, and not
printers. The only printers you should share are true network printers with
print servers - and you should share those from a centralized server. It's
not worth the headache to do it the way you're trying to do it, seriously.
Print servers (and new printers with integrated print servers) are pretty
cheap nowadays.