Re: shared printing limbo

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



OK, so evidentally this has something to do with the NetWare client I have
installed on the domain controller; for the purpose of migration.

I tried setting up a printer on the Exchange server and sharing it. Then I
installed a printer pointing to this share on yet another server and it
worked just fine.

So, if I can't find a workaround for the NetWare client problem I guess I'll
have to move the printers to another server.

Any helpful suggestions would be welcomed :)

Thanks,

Jerry




"CroiX" <usenet-general@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:13739a6n9vjkp12@xxxxxxxxxxxxxxxxxxxxx
I should have probably also mentioned that I verified that the firewall is
not a problem. It is not enabled on any of the servers.

Since I wrote the first message. I also tried installing the Print Server
Role on the machine hosting the printers. This didn't seem to make any
difference.

The printers are all using Standard TCP/IP Ports.

Thanks again,

Jerry




"CroiX" <usenet-general@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:13736hmdbhfuc3b@xxxxxxxxxxxxxxxxxxxxx
Greetings:

Some time back, I setup an AD environment with several servers. This
environment hasn't gone into production yet, but for the past year
everything seems to have been working just fine. However, today I setup
several printers on a 'backup' domain controller. Then I shared them, and
published them to AD. Initially, I had installed the printers locally on
each of the servers, but as we progressed with our environment
development I determined that this was the wrong way to do it.

Next, I went over to a member server and installed these shared printers
by searching for them in AD. Everything seemed to go just as would be
expected. The problem is, I can print a test page from the domain
controller, but not from the member server.

When I try to print from the member server, the confirmation dialog pops
up and says everything worked, but the printer never prints. Nothing
appears in any of the event logs that would indicate a problem.

I verified permissions. Everyone is allowed to print. I checked effective
rights for several accounts. Nothing looks out-of-place.

The account I was trying to print with, from both the domain controller
and the member server, is the enterprise admin. This is the same account
that was used to install the printers.

This is not the first time I have ever tried to print to a shared printer
in Windows. In fact, I have a Windows Server 2003 AD environment at home
where shared printing seems to be working just fine. This is, however,
the first time I have tried to share printers with other servers (instead
of just workstations).

Any idea what the heck might be going on here?

Thanks,

Jerry








.



Relevant Pages

  • Re: I hate IIS - "Server Application Unavailable" error message
    ... this is on a Win2003 Server. ... complaints or warnings installing IIS for me. ... as the SYSTEM account on a domain controller, although I would encrypt the section. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: FSMO roles on old server
    ... Exchange is installed on a Member Server ... If Exchange is installed on a Domain Controller then it will look ... installing Exchange on a Domain Controller but now work for a company that ...
    (microsoft.public.windows.server.active_directory)
  • Re: HP2600N Nightmare on Win2k3 server
    ... Been installing HP2600N's at schools no problem in a server environment. ... shared the printers and config'd GPO to 'push' these printers ... Phoned HP up and they said the HP2600N Win2k3 server driver wasn't designed ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Print Server Advertizement Problems
    ... Each building has a domain controller. ... Building B and C have a single server that is ... the printers in the main headquarters. ... The only difference is that the print queues ...
    (microsoft.public.windows.server.general)
  • Re: migrating the domain controller
    ... The way I usually do this is by simply installing new hardware (don't forget ... - replicate DNS to new server ... Using Ntdsutil.exe to seize or transfer FSMO roles to a domain controller ... How To Create or Move a Global Catalog in Windows 2000 (it is same on ...
    (microsoft.public.windows.server.networking)