Showing results for 
Search instead for 
Do you mean 
Reply
New Member
Posts: 1
Registered: ‎02-27-2017

Can't get to Centreware following machine name change

We use Xerox machines with Safecom for charging.  We have recently upgraded our firmware to 73 from 72 for a range of devices due to scan to email issues.  Our machines all have names which refer to the building they are in.

 

We now have a problem, that if a machine is moved, and so needs a new name, we can no longer get into the machine's Centreware pages following the move.  Centreware responds, but the page is plain blank blue.

 

We've worked out that if we disable forced https before the move we can get into the Centreware page.  However, the machine then needs reimporting into Safecom due to its' new name and IP address,  

 

The problem seems to be certificate related, and if we recreate the certificate then we can put https back on.  However, this can only be done at the machine, as it can't be done over http.  Our support is outsourced, and there is no on onsite who can do this.  

 

Any suggestions?  Either as to procedures to get round this, or which items affect certificate security?  Doe the DNS need to match the machine name?

 

This is causing us major problems as following machine moves it is taking days to get the machine back into action.  We didn't have these issues with firmware version 72.  

 

Thanks

 

  

Highlighted
Analyst Nation Moderator
Posts: 5,320
Registered: ‎11-25-2013

Re: Can't get to Centreware following machine name change

[ Edited ]

We now have a problem, that if a machine is moved, and so needs a new name, we can no longer get into the machine's Centreware pages following the move.  Centreware responds, but the page is plain blank blue.

Clear your cache

 

We've worked out that if we disable forced https before the move we can get into the Centreware page.  However, the machine then needs reimporting into Safecom due to its' new name and IP address,

This isn't a problem, at that point the connection is entirely new

 

The problem seems to be certificate related, and if we recreate the certificate then we can put https back on.  However, this can only be done at the machine, as it can't be done over http.  Our support is outsourced, and there is no on onsite who can do this.  

There is no reason you can't do the certificate remotely, if you have access (Good luck being a remote IT with no LAN access to the client) then you change the certificate on the same page you created/uploaded it in the first place.

 

Capture.GIF

 

Any suggestions?  Either as to procedures to get round this, or which items affect certificate security?  Doe the DNS need to match the machine name? This doens't make sense as it is worded, the DNS server is what tells a printer how to resolve a hostname to an IP address, a DNS server can only be an IP address and it certainly doesn't tie itself to a printer in any way, if you reverse the question, yes, the new printer Hostname must be registered in your internal DNS server for people to be able to get to it via the hostname, but that has nothing to do with Xerox.

 

This is causing us major problems as following machine moves it is taking days to get the machine back into action.  We didn't have these issues with firmware version 72. 

How often do you move printers across the street? And yes, you would have had the same problems if you had the same setup, 072-073 changed nothing related to how IP addresses, hostnames or certificates were handled, Xerox doesn't define the standards or implement them in custom ways, your setup on 072 was different.

 

 

 

Please be sure to select "Accept Solution" and or select the thumbs up icon to enter Kudos for posts that resolve your issues. Your feedback counts!

Joe.