Re: Adding a printer problem
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 23 Aug 2006 14:15:54 -0400
In news:Dj0Hg.2506$s4.1798@xxxxxxxxxxxxxxxxxxxx,
Simon <simon@xxxxxxxxxxxx> typed:
Thanks :)
That seems to have done the trick, printer is now added and all looks
good just using a tcpip port. I'll wait until I'm on site to test from
the clients.
I agree, I should have gone jetdirect, the increased hassle of
straying from the norm just isn't worth it.
simon
Glad you got it working anyway!
Lanwench [MVP - Exchange] wrote:
In news:EeTGg.10434$2w1.4790@xxxxxxxxxxxxxxxxxxxx,
Simon <simon@xxxxxxxxxxxx> typed:
Hi There,
I had previously posted this problem, but have now got some more
information.
I am using a sitecom network print server attached to a HP laserjet
3500.
In general, I'd recommend sticking with HP JetDirects for HP print
servers.
I installed the client software onto the server
I generally don't recommend doing that. I would install only a
driver. Printer software suites are really meant for desktop
computers.
(sbs23k) so that
the server can see the printer. This adds another port to the server
for communication.
You can create a standard TCP/IP port and just use the driver,
surely.
The problem I have is the add printer wizard goes through all the
steps, asks for a share name etc, then completes. When the process
is finished the printer is showing under printers and faxes, but
not on the server management printer screen, even after a few
hours. If I go into the properties of the printer sharing is not
enabled, trying to enable it and save the settings give the error
that printer settings could not be saved.
If I run through the wizard again and add the printer a second time
using a different name then try and choose the same name for the
share I get the error the share name already exists.
The support people for the product assure me it's been tested fine
with w2k3 so should be ok with sbs as well.
Any ideas anyone ?
What happens if you try my suggestion above? Uninstall the software,
create a standard TCP/IP port using the printer's IP (either a
static IP or a DHCP reservation), and point it at the driver only.
Then share it.
Thanks,
simon
.
- References:
- Adding a printer problem
- From: Simon
- Re: Adding a printer problem
- From: Lanwench [MVP - Exchange]
- Re: Adding a printer problem
- From: Simon
- Adding a printer problem
- Prev by Date: Re: Active directory replication problems
- Next by Date: Switches for a SMB Network
- Previous by thread: Re: Adding a printer problem
- Next by thread: Simple question
- Index(es):
Relevant Pages
|
