
:-)Īnyway, since you've already done it and it obviously didn't crash or otherwise have an impact on the server (you'd be asking other questions otherwise) you can proceed. I've googled for help as well, but I just might not have enough understanding of wireshark/packet capturing to utilize the advise/info I've found in my google searches.Īlright, installing WinPCAP and Wireshark on a Domain Controller? I wouldn't dare to do that. I'd consider myself a novice when it comes to Wireshark, though I'm understanding more and more as I use it. I'd like to setup Wireshark to capture traffic from the MFP (192.168.0.20) to the DC/print server SMTP relay (IP 192.168.0.20). Just "error connecting".) I am not sure if the job is being rejected by the SMTP relay on the DC/print server or if it is being rejected by Office 365 SMTP.

When a scan to email job is started from the printer, I get a connection error message (it is not descriptive at all. I'm trying to configure the MFP for scan to email using the SMTP relay on the DC/print server which is pointing to a Office 365 SMTP server. I've installed wireshark and winpcap on the DC/print server. I have a MFP (mock IP 192.168.0.20) and a SMTP relay which is setup on our DC/print server (mock IP 192.168.0.10). Hi all, I've been searching online for some help to this, but so far I haven't found an answer (or at least I have not recognized the answer).
