RE: Printers don't work after W2K3 install

Hi,

Based on my experience, this issue can occur because the conflicts between
the driver installed in Windows 2K system and Windows 2003 system.
Therefore, you have to re-stetup it.


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: AcaRWOUsF1z8BW+MQQeXIMNVz0l9yg==
X-WBNR-Posting-Host: 216.36.147.15
From: =?Utf-8?B?RGFu?= <Dan@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <EEA847F2-04FC-4BA9-AC40-E47645CD3C47@xxxxxxxxxxxxx>
<wjrVYLCkGHA.4948@xxxxxxxxxxxxxxxxxxxxx>
<9BB7C0C4-3B58-44EC-A55D-7DC2156929BD@xxxxxxxxxxxxx>
<L2CiqpQkGHA.5700@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Printers don't work after W2K3 install
Date: Fri, 16 Jun 2006 08:24:01 -0700
Lines: 164
Message-ID: <34E6D3A2-DC6A-40A5-8206-55EB81EA4C60@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:24113
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.migration

Thks Vincent. That wasn't my concern. They are printing. My concern
were
the printers not printing before, even though the shared name and IP addr
were the same as the old Print Server.

"Vincent Xu [MSFT]" wrote:

Hi,

Check two things:

1. Can you print any documents on the new print server?
2. Can you access any shared folder on the new print server?(create a
new
shared folder to test)

Thanks.

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: AcaQhEbKtzO2YZ0QRVu6xOFjvL7JBQ==
X-WBNR-Posting-Host: 216.36.147.15
From: =?Utf-8?B?RGFu?= <Dan@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <EEA847F2-04FC-4BA9-AC40-E47645CD3C47@xxxxxxxxxxxxx>
<wjrVYLCkGHA.4948@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Printers don't work after W2K3 install
Date: Thu, 15 Jun 2006 07:02:02 -0700
Lines: 85
Message-ID: <9BB7C0C4-3B58-44EC-A55D-7DC2156929BD@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:24097
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.migration

Maybe my explanation wasn't clear. That were the steps (kinda) that
I
took.
The mystery behind all this, is why would the clients failed to
connect
to
all these printers on the Print Server running W2K3 R2? The printer
share
name and IP addr of the Print Server is the same.
The Print Server before was running W2K.

"Vincent Xu [MSFT]" wrote:

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: How to quickly add print queue for all those Windows XP in an Windows 4.0 Domain?
    ... In my work place we just brought over 100 new PCs with Windows XP Prof, ... you simply install the correct XP printer driver on the NT 4.0 print server. ...
    (microsoft.public.windows.server.scripting)
  • Re: Print Server
    ... MH>>> I would like to make into a print server. ... I have a LAN card and a dongle or I have a Linksys wireless LAN ... MH> 1.1 Decide if you want X windows or not. ... install printer driver. ...
    (comp.os.linux.misc)
  • Re: Unable to install Netgear Print Server application
    ... Print Server Setup Software Version 3.01 ... Windows XP - Shell/User ... | the PS101 Print Server Software: ... | This error only comes up when I am attemtpingto install the NetGear PS101 ...
    (microsoft.public.windowsxp.print_fax)
  • Re: looking for a printer recommendation
    ... > Well if you had them install something like an HP print server ... which makes it pretty easy to reach windows ... > Why not use netcat. ...
    (comp.unix.sco.misc)
  • Re: Printer server redundancy
    ... That article specifically refers to windows 2003. ... Vincent Xu wrote: ... We have alot of network printers which were ... added to our Windows 2000 print server and are shared from there. ...
    (microsoft.public.windows.server.migration)