RE: Printers don't work after W2K3 install

Hi,

Based on my knowledge, the steps can be:

1. Install a new printer server
2. Using same IP address, computer name and printer share name for the new
printer server.
3. take the previous printer server offline
4. Join the new printer server into domain
5. Grant corresponding permissions to printer users.

The failed cause can be various. I'd like to suggest you check the registry
key at :

HKEY_CURRENT_USER\Printers\Connections\

to see if the connection is properly set.


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
Thread-Topic: Printers don't work after W2K3 install
thread-index: AcaPzxaRC62UDdVoQ6G8VZSEEgpLrw==
X-WBNR-Posting-Host: 216.36.147.15
From: =?Utf-8?B?RGFu?= <Dan@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Printers don't work after W2K3 install
Date: Wed, 14 Jun 2006 09:25:02 -0700
Lines: 10
Message-ID: <EEA847F2-04FC-4BA9-AC40-E47645CD3C47@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.migration
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24065
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.migration

Hi, we had a number of printers installed onto a Win2K Server DC acting
as a
printer server besides other network services. IP addr was x.x.x.100. I
then proceed to setup a W2K3 R2 Server, renamed it to the same name as
the
Win2K server after taking the old server down. Changed the IP addr back
to
its original as x.x.x.100. So the printers shared name is the same as
before. However, the clients' machine do not recognize these printers
anymore. It indicated as "Printer not found" in their Printers and Faxes
properties. All I had to do was remove these printers and resetup. Just
wondering why wouldn't the printers continue to work because the printers
share name and server IP addr is the same as before.


.

Relevant Pages

  • Re: !!HELP!! Pulling my hair on this one. Printer problems. Really need some help on this.
    ... Yes Larry I have already moved them off of the SBS server and onto a high ... When the printers were connecte they did show as being offline. ... have workstations connected are plugged into the same. ...
    (microsoft.public.windows.server.sbs)
  • Re: 2nd Branch Server and Laptop configuration suggestion
    ... please share all printers and folders the laptop user ... This newsgroup only focuses on SBS technical issues. ... now, that way, each branch is independent of any possible Server down at ...
    (microsoft.public.windows.server.sbs)
  • Re: !!HELP!! Pulling my hair on this one. Printer problems. Really need some help on this.
    ... Yes it is becoming a concerning issue with my SBS server. ... When the printers were connecte they did show as being offline. ... It can't be my hub because other wall jacks that have workstations ...
    (microsoft.public.windows.server.sbs)
  • Re: CUPS Server Error
    ... Server Identity ... > # Classification: the classification level of the server. ... the default language if not specified by the browser. ... determines whether the scheduler will allow new printers ...
    (Debian-User)
  • Re: !!HELP!! Pulling my hair on this one. Printer problems. Really need some help on this.
    ... If the server tried to contact a printer and could not, say because of a sporadic hardware issue, it might report the printeras offline. ... I think that what I would do next would be to delete all the printers, then go into Server Properties and delete all the drivers. ... So I think for now if I can resolve the issue as to why I cannot remove and delete the print queues from my SBS server then I can try to reinstall from scratch without the existing print queues still in place. ... By centralizing the spooler you can control access, do "grouped" deployments, such as department/building/remote printer locations using group policy, upgrade a driver on the server and have all workstations get the new driver automatically, and...ultimately...usually a better troubleshooting experience when problems arise because you know the driver, the port, and don't have several workstations with different configurations floating out there. ...
    (microsoft.public.windows.server.sbs)