Re: NT4 Workstations can't connect to printers after migration to Server 2003
- From: v-xuwen@xxxxxxxxxxxxxxxxxxxx (Vincent Xu [MSFT])
- Date: Fri, 21 Jul 2006 05:20:39 GMT
Hi,
Wounderful! Great Job!
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.
======================================================
--------------------
<VLkLIY6qGHA.5976@xxxxxxxxxxxxxxxxxxxxx>From: "Tim Munro" <Excelsior@xxxxxxxxxxx>
References: <#ENB5v0qGHA.4408@xxxxxxxxxxxxxxxxxxxx>
to Server 2003Subject: Re: NT4 Workstations can't connect to printers after migration
microsoft.public.windows.server.migration:24508Date: Thu, 20 Jul 2006 08:20:29 -0400
Lines: 87
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Message-ID: <edyMlb$qGHA.5108@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: 134.117.135.162
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
orX-Tomcat-NG: microsoft.public.windows.server.migration
We have resolved this issue.
For the imgration here's the info
We have changed hardware and jumped from Win2k in an NT domain to
Win2k3 R2 in Active Directory (a new domain)
Original printer server name has been CNAMEd so existing printers
will continue to work. (no problem for XP)
There were no WINS entires for either the real print server name
printersthe CNAME entry.
Solution to NT4 workstation issue:
Add WINS entries for both real server name AND CNAME entry.
One minor issue renames, NT4 workstations can map/use the
livesusing the real server name without the domain extension. If they use the
CNAME they must fully qualify the name with the DNS domain the server
rights.in. NT4 workstation (and servers) can't seem to properly resolve CNAMEs.
--
Tim
"Vincent Xu [MSFT]" <v-xuwen@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:VLkLIY6qGHA.5976@xxxxxxxxxxxxxxxxxxxxxxxx
Hi,
First,how did you migrate the printing infrastructure?
Second, check if you installed the directory service client?
http://support.microsoft.com/kb/288358
Third, Now, the printers are all connected to a print server?
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
to======================================================
--------------------
Server 2003From: "Tim Munro" <Excelsior@xxxxxxxxxxx>
Subject: NT4 Workstations can't connect to printers after migration to
microsoft.public.windows.server.migration:24491Date: Wed, 19 Jul 2006 11:56:58 -0400
Lines: 11
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Message-ID: <#ENB5v0qGHA.4408@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: 134.117.135.162
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
2003X-Tomcat-NG: microsoft.public.windows.server.migration
Hello all,
I have just migrated our printing infrastructure to Windows Server
R2. I now have a issue where Windows NT 4 workstations cannot connect
"printerany
printers. While trying to add (or re-add) printers, I'm getting
name is invalid". Any pointers on where to look would be most welcome.
--
Tim
.
- References:
- NT4 Workstations can't connect to printers after migration to Server 2003
- From: Tim Munro
- RE: NT4 Workstations can't connect to printers after migration to Server 2003
- From: Vincent Xu [MSFT]
- Re: NT4 Workstations can't connect to printers after migration to Server 2003
- From: Tim Munro
- NT4 Workstations can't connect to printers after migration to Server 2003
- Prev by Date: RE: ADMT Option File Parameters
- Next by Date: Re: Problem after migrate
- Previous by thread: Re: NT4 Workstations can't connect to printers after migration to Server 2003
- Next by thread: Failed to create a trust relationship between NT4 and 2003 AD
- Index(es):
Relevant Pages
|
Loading