logical indeed! :)
Normally the only logical reason for that, would be that you didn't select "Device" under System Jobs:
hmm, sounds stupid, but when i actually send from the machine itself, it works...
if i use the "test configuraion" on cwis, it doesnt work ... go figure
Hey Guys, I'm new to the Xerox boards but have been working on wide format printers for a long, long time. Recently Microsoft rolled out quite a few security updates that broke printing and scanning for a lot of different MFP's. Take a look at the MSKB article and see if that helps the issues being discussed in this thread:
https://support.microsoft.com/en-us/help/4560960/windows-10-update-kb4560960
All the best,
interesting,
no i have dns timeout on 30 sec, but still the error displays after the same amount of time as before (2-3 sec) :-)
also, enabling ipv6 doesnt help :(
verry strange
But did increasing the time out also increased the the time before the error happened?
(not that I can explain why... but maybe it could something)
I can see that the Xerox is both asking the DNS to resolve the host name as both an IPv4 and a IPv6 address.
- You said you have disabled IPv6, which would make no sense why a IPv6 is resolved... Does it make a difference if you enable the IPv6 protocol?
(or if you accidentily left it off; does it make a difference if you disable it?)
yeah, indeed its nt the same issue
but its strange though... not all machines are affected, some work, some dont, same settings, same spar firmware...
seems only altalink is affected, workcentre 7855 dont havz the issue
increasing timeout to 30 sec, didnt help :(
also tried all combinations, ttls , ttls if available , with check certificate on/off doesnt help
normally it works with ttls (if available) and check servercertficate = OFF
i always do this setup ...
lots of customer called in, where it was working, and suddenly not anymore, so settings werent changed
Hi Fabio,
That's a pity.. I hoped we had exactly the same issue, as it would mean that possibly we both could use the same solution.
In your log there is a clear pause of 5 seconds in the communication, which is the default DNS time-out setting.
Does it make a difference if you change this time out (to... let's say 20 seconds)?
(if it does change the behaviour by increasing the time before you get the error, I guess it would mean that possibly the machine is waiting for something it doesn't get)
- Which of the settings do you have enabled under Security -> TLS?
- Do you have "validate server certificate" enabled or disabled at the SMTP config?
Kind regards,
Florian
no, rebooting doesnt help
tried IP/dns as well, no difference
attached a trace : https://www.dropbox.com/s/tdeo1bs406bnsom/NetworkTroubleshooting_2020-06-19T145443.133%2B0100.pcap?d...