JStewart Data Systems

To those of you wondering, Steven did hear back from me. I did not leave him hanging. At last contact, the printer and scanner were able to communicate with all the computers on his network. Unfortunately, it took two visits and a phone call to fully resolve the issue. Sometimes this is what it takes, especially when it is an intermittent failure like this one. He was only charged for the first service call. I am sorry that Steven was disappointed in my performance on this job. No, the comment was not the best, and probably deserved more thought. But it was honest. I didn't know for sure. Could have given him some BS explanation, but that is not how I work. . It wasn't until the second service call, that I had a much better idea of where the fault lay. I was able to confirm it through research, and with Steven sharing with me that his phone kept loosing connectivity to the home network. I do not know if the phone problem was occurring on the first service call. It was not mentioned. In a nutshell, the problem was not with Windows connectivity to the printer, but a combination of a quirk in the firmware of the model of printer he had, and an unstable Comcast internet connection. The printer, rather than responding to the lost wireless connection by checking for the connection to be reestablished, would go into corner and sulk. It required manual intervention by the user to bring the printer out of its funk. First time I'd seen a printer act that way in the 12 years I've been in this business. Fix was to use a wired connection to the Comcast modem from the printer. Everything seems to be working fine at last contact.