A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

XP Pro Workstations



 
 
Thread Tools Display Modes
  #1  
Old February 18th 09, 12:43 PM posted to microsoft.public.windowsxp.network_web
Mark C.[_2_]
external usenet poster
 
Posts: 15
Default 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???
Ads
  #2  
Old February 19th 09, 05:30 AM posted to microsoft.public.windowsxp.network_web
Lanwench [MVP - Exchange]
external usenet poster
 
Posts: 1,547
Default 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.


  #3  
Old February 19th 09, 05:30 AM posted to microsoft.public.windowsxp.network_web
Lanwench [MVP - Exchange]
external usenet poster
 
Posts: 1,547
Default 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.


  #4  
Old February 20th 09, 01:09 PM posted to microsoft.public.windowsxp.network_web
Anteaus
external usenet poster
 
Posts: 1,330
Default 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.


  #5  
Old February 20th 09, 01:09 PM posted to microsoft.public.windowsxp.network_web
Anteaus
external usenet poster
 
Posts: 1,330
Default 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.


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 08:36 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.