We are able to access the share without issue from a Mac or PC. I have no idea why this would have just began after the host went down. Which based on this windows documentationĪppears to just be a generic access denied error. SMB2 147 Session Setup Response, Error: STATUS_LOGON_FAILURE The local share (centOS) negotiated via SMB2 and eventually returned this error to the printer. What I found was the printer reached out to our domain controller and it resolved the DNS to the local share. I ran a packet trace through Meraki to see what the communication was like between the printer and our windows server.
Verified I can ping the printer and reach its web interface. Verified that the printer can reach the internet as it can email scans. Tested with my own AD account (admin privileges), which failed in the same manner. Tested connecting to both the shares IP and its DNS name.Ĭhanged the password to the AD account that’s used on the printers. Verified with our printer vendor that the firmware was current on the Ricoh.
WHAT IS RICOH HOST CONTROLLER UPDATE
Verified that the CentOS box did not update when the host came back up. Verified that the Ricoh is connecting on the correct port (445). Verified that Windows Server 2012 does have SMB 1 enabled (though this is probably not needed). Verified that the active directory account that the printers are using is able to sign in to active directory. Troubleshooting that I have performed so far:
WHAT IS RICOH HOST CONTROLLER DRIVERS
Now with Driver Matic, a PC can have up to date drivers automatically. I will speak specifically to the Ricoh MP C5503, but note that all models of printers in the office fail to connect to the SMB Share A driver update may also improve stability and performance, or may fix aficko with games, programs and power management.
Local share is being managed by a CentOS installation running Egnyte Sync.īoth of these are located on the host that went down.Īs a side note I would say that this system is something that we have inherited so we are not full aware of all of its ins and outs To give you an idea of environment it is as follows:Īctive Directory / DNS is being handled on a Windows 2012 server They will now give errors that authentication failed. After it came back up all of printers that scan to SMB shares were no longer able to do that. On January 29th one of hosts that several virtual machines sit on went down. I will break down how the issue began and what I have tried / learned so far. I have spent the past week and a half trying to resolve this issue but have been failing so far. Hello I hope someone can give me some guidance here.
0 kommentar(er)
