On Wednesday 24 December 2008 10:45:58 Mick wrote: > It could still be a machine naming issue if you are pointing your client > to e.g. http://192.168.2.2:631 instead of http://serv.ethnet:631 - which > is what I suspect the SSL certificate's CN record shows.
(There's always one more detail that gets forgotten.) I am pointing my client to serv.ethnet, not any IP address. It decides for itself, part-way through setting-up the printer, that it's now connected to a different host from before. > Either way - if you disable authentication with SSL this problem will go > away. - but remain unsolved. Thanks anyway. -- Rgds Peter
