Printer Sever - Some clients can't print

Hi,

I've a dozen workstations that are members of a Windows 2003 domain. The
server has the R3 Printer Management role installed.

I changed the IP address of the Dell network printer that is installed on
the server and shared. I also changed the IP address of the server and
workstations. I changed the TCP/IP port connection and the server can print
fine as can most of the workstations that are connected to this shared
printer.

However, some workstations can not print. At one failing workstation (Win XP
Pro), I deleted the printer (which took a long time) and added it back (which
took a long time). Trying to Test Print via properties takes a long time
before it fails and a message displays that it doesn't have the proper print
driver.

I looked in the servers Print Mangement - Drivers Folder and I see the
drivers are present. I then uninstalled the printer from the server and used
the Dell installation CD to put it back, but I still have the same symptoms.

I suppose the problem is some workstations are failing to download the print
driver from the server? I'm don't know how the workstations managed to lose
the drivers in the first place as they were able to print just fine before I
changed the IP addresses.

Any ideas where the problem might be? Thanks!
--
Bob

Please don't bother to reply to the post. The symtoms have changed, so I'll
have to do some more digging before I post again. I find that different
users can print from the failing workstation. So it seems to be more a user
profile problem rather than the machine. Yet these same failing user profiles
can print fine from other workstations. Deleting the profile on the
workstation doesn't help, so maybe it is a corrupt Roaming Profile on the
server. I may find that deleting working profiles will fail also once they
are refreshed from the server. Just don't know yet.

Anyway, I've some more problem isolation to do before I post again. Thanks
the same.
--
Bob

Hello Bob,

Thank you for using newsgroup!

If you have any questions, please feel free to post here.

Thanks & Regards,

Ken Zhao

Microsoft Online Support
Microsoft Global Technical Support Center

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





--------------------
| Thread-Topic: Printer Sever - Some clients can't print
| thread-index: AceZgaxZOiAezLaJQQOm+PZgndbYRw==
| X-WBNR-Posting-Host: 207.46.193.207
| From: =?Utf-8?B?Qm9i?= <86c6c2e6-(E-Mail Removed)>
| References: <0621DB2E-C2F5-46BA-AE17-(E-Mail Removed)>
| Subject: RE: Printer Sever - Some clients can't print
| Date: Fri, 18 May 2007 12:21:02 -0700
| Lines: 13
| Message-ID: <9FBD578E-EDB8-4550-ADFD-(E-Mail Removed)>
| 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.2826
| Newsgroups: microsoft.public.windows.server.networking
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.networking:4633
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.networking
|
| Please don't bother to reply to the post. The symtoms have changed, so
I'll
| have to do some more digging before I post again. I find that different
| users can print from the failing workstation. So it seems to be more a
user
| profile problem rather than the machine. Yet these same failing user
profiles
| can print fine from other workstations. Deleting the profile on the
| workstation doesn't help, so maybe it is a corrupt Roaming Profile on the
| server. I may find that deleting working profiles will fail also once
they
| are refreshed from the server. Just don't know yet.
|
| Anyway, I've some more problem isolation to do before I post again.
Thanks
| the same.
| --
| Bob
|

Thanks Ken,
It turned out to be the central roaming profile on the server. Creating a
new one resolved it.
--
Bob

Hello Bob,

Thanks for your reply and let us know you have resolved the issue.

Thanks & Regards,

Ken Zhao

Microsoft Online Support
Microsoft Global Technical Support Center

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





--------------------
| Thread-Topic: Printer Sever - Some clients can't print
| thread-index: AceblGOcOi3w7by1QWagLJNr7Uewkw==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?Qm9i?= <86c6c2e6-(E-Mail Removed)>
| References: <0621DB2E-C2F5-46BA-AE17-(E-Mail Removed)>
<9FBD578E-EDB8-4550-ADFD-(E-Mail Removed)>
<(E-Mail Removed)>
| Subject: RE: Printer Sever - Some clients can't print
| Date: Mon, 21 May 2007 03:40:03 -0700
| Lines: 5
| Message-ID: <EA7B8E5E-D56D-4EE8-B29C-(E-Mail Removed)>
| 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.2826
| Newsgroups: microsoft.public.windows.server.networking
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.networking:4667
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.networking
|
| Thanks Ken,
| It turned out to be the central roaming profile on the server. Creating a
| new one resolved it.
| --
| Bob
|