IPP: Website error with DNS Alias, Hostname works

[Marcus]

Hi,

I intend to connect the printers for my clients using IPP
and HTTP in future. I want to set up multiple W2K
printservers, on which the printers are configured exactly
the same way. (Same driver, same configuration). I want to
connect the clients with the printers by creating the
connection using the printers webpage.
(http://DNSALIAS/printers). If a server has downtime I
want to change the DNS-Alias and use another printserver.

The problem I have, is that I can connect to the printers
website when I use the Hostname, but not when I use the
DNS Alias. When I try to open the webpage using the DNS-
Alias I receive the following error code.
"An error occured while processing the request; Error
code: 80070034; Hint: ADSI-printer determined (Translated
from German, hope I didn't make to many mistakes.)
(Ein Fehler ist beim Verarbeiten der Anforderung
aufgetreten; Fehlercode: 80070034; Hinweis: ADSI-Drucker
ermittelt.)

Other websites being hosted on this Server can be
addressed by either the Hostname or the DNS-Alias.

If anybody has an idea how to solve this problem I would
appreciate his/her help.

Thanks in advance
Marcus

 

[JohnNews]

Marcus:


I will attempt to answer your question based on MY OWN (limited) experience
in the Print Server discipline.

Good idea to setup at least TWO print servers - primary (production) &
secondary (backup).

If you set up your print servers as CLUSTERS then maybe switching over will
work automatically if one print server fails.
But I believe the clustering concept works from Windows 2000 Advance Server
and up.

I prefer a MANUAL switch over if one print server fails. In which case just
disconnect primary from network and rename secondary with the name of
primary. I am assuming at this point that both print servers have identical
print drivers installed.

Once you repair your faulty primary, rename it to the original name of the
secondary.

Let us know how things work out for you, Marcus, keep us posted.



Thanks,
John

 

[Marcus]

Hi John,

thanks for your reply.

The idea I have is to use any Server I have running. I
don't want to use a cold spare. That's the reason why
renaming a backup server is not an option and why I had
the idea of using a DNS Alias for the printserver. The
idea seems to work with other servers. But with the
specific server I want to use as primary printserver I get
this error message. I believe it's a problem with the
Printers Website or the IIS.

Thanks
Marcus

 

[Alan Morris\(MSFT\)]

ADSI which is what the spooler uses to drive the asp pages for web printing
isn't CNAME aware, the spooler is CNAME aware from Win2k SP4 on.



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi All

I have the same problem as Marcus, but for different reasons.

We have a naming convention for servers that isn't very user friendly, and

I want to publish a useful URL for users to use i.e.
http://location/printers. However, when I add a CNAME record pointing
"location" to the real server name, I get the same error (Error 80070035,
Get ADSI Printers). I think it might be related to the .asp code, as when
you open the IIS default printers URL (servername/printers) the first .asp
page says "All printers on servername", then if I put "ipaddress/printers"
the first page reflects this and now says "All printers on ipaddress". This
must mean it's getting something from the browser that it uses to render the
page, and somehow by redirecting ot through a DNS alias, it can't get the
browser info. I'm no .asp codehead though, so I'm reaching my limits with
that.

This is a big pain, although for now we'll just put a link on the Intranet

that points to the duff servername URL. It would be great to tell visitors
using our Guest WLAN to point their browser at "location/printers", but we
can't go handing out server names directly.

 

[haykelv]

Hi All,

I'm in a very similar situation - I have two print servers,
production and 1 backup server.

I want to use round robin DNS (or the smarter DNS load balancing whic
uses costs/ratios) to present a single name to our clients.

The problem I get is that if I map to \\alias\printqueue the host tha
reponds (say server1) responds with its true hostname and my XP deskto
pcs write server1 into the registry entry for the print queue. When th
client then attempts to use the printer object but DNS redirects the
to server2, the xp workstation gets an access denied error.

Does anyone have any ideas on how I can get this to work?

*Hi All

I have the same problem as Marcus, but for different reasons.

We have a naming convention for servers that isn't very use
friendly, and I want to publish a useful URL for users to use i.e
http://location/printers. However, when I add a CNAME recor
pointing "location" to the real server name, I get the same error
(Error 80070035, Get ADSI Printers). I think it might be related t
the .asp code, as when you open the IIS default printers UR
(servername/printers) the first .asp page says "All printers o
servername", then if I put "ipaddress/printers" the first pa
ge reflects this and now says "All printers on ipaddress". This mus
mean it's getting something from the browser that it uses to rende
the page, and somehow by redirecting ot through a DNS alias, it can'
get the browser info. I'm no .asp codehead tho
ugh, so I'm reaching my limits with that.

This is a big pain, although for now we'll just put a link on th
Intranet that points to the duff servername URL. It would be grea
to tell visitors using our Guest WLAN to point their browser a
"location/printers", but we can't go handing out server n
ames directly.

Anyone coming up with a workable solution gets $20 in their Paypa
account!

Thanks

-
haykel