The USB ports are not usable like that, they are for printing from a PC and for scan/print to and from a USB stick, or for powering devices and adding things like card readers, they are not for diagnostics.
DHCP gets an address from a DHCP server, DHCP/A gets it by checking the IP's on the network and assigning itself one that isn't in use.
As for the hostname stuff, recently a bunch of mail servers seem to require the .local be added when the device sending is not part of a real domain. No idea on the why, they didn't need it at all for a very long span, then all of the sudden we started seeing errors on Office365 SMTP traffic, then a week later Godaddy and Gmail, then some more, and more etc etc.At some point one of us accidentally stumbled on the .local fix, we have been suggesting it ever since, and it seems to be working.
I assume it was discovered in a Wireshark trace.
After running the trace tests yesterday, we realized we had a problem with our SMTP2GO account and switched over to the google aspmx server described in the attached link.
We did this to eliminate the SMTP2GO variable. But no luck in in sending emails. Then we made the changes you suggested in the previous post and we had success. Thank you. We are wondering why the DHCP instead of DHCP/Autonet and the host and domain name changes you suggested made such a huge difference. Any explanation?
Also, for future issues, could we have hooked up to the USB ports (#7 and #8) in the attached diagram to do local troubleshooting with a laptop or do we need something specialized to do this. When we hooked to port #7 with the laptop, it did not seem to have any effect.
Thank you again.
My guess would be that you used DHCP/Autonet and not DHCP.
The fix, if not that, would be to set the primary DNS as 188.8.131.52 and the secondary as 192.168.1.1.
And failing that, the only thing left is a factory wipe, because its clearly a false message if you are getting login failures, becuas ewithout DNS you don't get a login prompt to fail on.
Also in the DNS, add .local to the Hostname (XEROX.local)
And set the domain name to WORKGROUP.local
Okay, we will contact SMTP2GO support. But could you please address why we keep getting this error on the top left of the screen?
DNS server failure. Make sure that DNS address is correctly set. Or, make sure that the dynamic DNS setting is enabled in tools.
Based on the previous screen shot we shared with you, why are we getting this message if we set the DNS server to be selected automatically and also enabled dynamic DNS. What are we missing?
Please contact SMTP2Go support.
We ran a signal trace test. Here are the results.
We could not login with our original username. We are still not sure why, it is a valid SMTP2GO account. Anyways, we tried a new username and were able to get logged in. But then we had a domain issue and it resulted in a failure. Is this failure something to do with the 7435, our router, or what? It would be great if you folks could point us in the right direction. Thank you.
Here is a shot of our TCP/IP settings.
Should we not have selected obtain DNS server address automatically or enabled dynamic DNS registration? We have done this on other system devices. Is there a problem with the host name?
We are going to go off and try and run a signal trace test and come back with the results.
Weird. What happens if you replace mail.smtp2go.com with 184.108.40.206
I don't at all know what is happening with your printer, you simply cannot have been getting the errors you were getting if DNS wasn't setup properly in the first place. DNS is the server that tells the printer how to resolve the mail.smtp2go.com host name into an IP address to communicate with, which had to have been working or you would not have gotten to the login failure.
Based on your input, we checked our Smtp2go.com account, but did not have anything under our dashboard. So, we rebooted the everything to start over and attempted the scan to email again. We have now gotten the error code 016-772, DNS server un-sets up in SMTP. We tried it a few times with the same error but think we have had it for today. Are we getting close? What needs to be done in the DNS configuration?