SMTP Trouble after replacing NIC

[tmaged]

I have a customers ES230 that had the NIC go bad. I pulled the NIC off our 200L in the service area & installed it on the customers machine. I put their IP address in & thought all was good. They called the other day saying they are unable to email. I went there & all of my SMTP settings were in the web page. Evidently this is on the NIC pwb ??? I changed all the settings to theirs & haven't been able to get it to work. Tried 08-947. Still no SMTP. Everthing else seems to work. I don't want to do 08-693 right? It should have worked on theirs since all my SMTP settings were right. Any way to re-initialize SMTP? Not sure where to go next.
Thanks for any help.

[atudorica]

take the easy way
save your network setings
do 08-693 up to 20 times
when you wil see "initialize" button on screen is done
you will be amaized

[tmaged]

Does 08-693 affect the Firmware on the NIC or just restores all settings. I was concerned it would revert the firmware to an older version or something.
Thanks,

[Baphomet]

I'd say do yourself a favor before you just go wild guessing about it. Go into the job log and see what code is given for the scan jobs that did not go through then look up the code in the handbook. It will tell you, for instance, if it was a communication error, authentication error, couldn't find the server, etc ... Most likely the error code will lead you in the right direction. If you don't have the service handboook, post the code I and will let you know what it means.

[ivovb]

In addition to Baphomet's post I would check firmware versions of both copy machines. All firmwares must be bundle in order system to work.
BR

[Baphomet]

	Quote:			Originally Posted by ivovb
	In addition to Baphomet's post I would check firmware versions of both copy machines. All firmwares must be bundle in order system to work. BR

It is true the if you revert the firmware and the NIC is at a more recent version it will ruin the NIC. But in that instance you would not be able to connect to the network at all.

I might just throw this into the discussion just for thought. I went to an account where the customer complained that the scan to email quit working. I get there and the job log indicated "OK" where the jobs were sent. The problem was that the customers mail server was down and not delivering the mail that day. A few hours later she received everything she had scanned. It is important to use the job log when troubleshooting scanning issues, otherwise you are just beating yourself to death.

[mckinley]

two things...

1. you do realise that if you have changed the NIC, the machine will have a different MAC address & therefore could be seen as an intruder on the network.
2. If the network is using anything such as SMB & it requires specific settings ( username / pwd or admin login / pwd, smb path ), smtp will fail.

I would speak to their network admin if they have one, or try to speak to who set the machine up on the network.

[atudorica]

my reset worked every single time
if you print but can't scan to email
you need to reset the NIC
do 08-693 until you'll see "initialize" button
this is your fix

[tmaged]

	Quote:			Originally Posted by Baphomet
	I'd say do yourself a favor before you just go wild guessing about it. Go into the job log and see what code is given for the scan jobs that did not go through then look up the code in the handbook. It will tell you, for instance, if it was a communication error, authentication error, couldn't find the server, etc ... Most likely the error code will lead you in the right direction. If you don't have the service handboook, post the code I and will let you know what it means.

I found all the error codes for scanning in the SH. I can't find where it lists the code. I've attached the Job log screen shot. I also tried clear/8 when I get the failed to send email error thinking it would display the error code. I also printed the error history list. Sadly, all were failures.
Am I missing something obvious ?
PS I did try 08-693 & reset all the SMTP settings.

[Sbarro]

Your authentication is set to PLAIN. It usually is LOGIN. Try another too.