![](templates/Cobalt/images/spacer.gif) |
Home of the Kip Doctor!
REGISTER: In order to register for our forums please send an E mail to [email protected] stating what user name and password you would like. This is now required due to all the spambots that have been registering.
![KeepItPrinting.com Forum Index](images/logo/Cobalt.gif) |
KeepItPrinting.com The "unofficial' and "unauthorized" KIP info site.
|
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
|
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
cmwade77 doctor
Joined: 03 Aug 2006 Posts: 251
![](templates/Cobalt/images/spacer.gif) |
Posted: Wed Jan 21, 2015 3:53 pm Post subject: KIP 3000 & 8000 Email Issues |
![Back to top](templates/Cobalt/images/icon_top.gif) |
|
I am having a problem when I try to setup the email alerts on the KIP 3000 & 8000.
The error that gets returned is Error 500: Internal Server Error
We have a 7970 in one of our other offices that this works on with no problems.
I have checked that the DNS servers are specified and are correct. I have also tried using the sever's IP address instead of the server name.
I saw on another thread to try to telnet <<servername>> 25, replacing <<servername>> with the appropriate server. I try this and I get an error that telnet is not a recognized command.
Can anyone help? |
|
|
|
|
|
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
jezebel09 resident
Joined: 12 Jun 2013 Posts: 209
![](templates/Cobalt/images/spacer.gif) |
Posted: Thu Jan 22, 2015 8:17 pm Post subject: |
![Back to top](templates/Cobalt/images/icon_top.gif) |
|
This unfortunately can be so many things. Early versions of PrintNET were very easy to corrupt.
I don't think there is an easy solution here other than a reload. I usually hate to suggest that, but these are older machines and who knows what has been changed.
However, a reload might be worse than just dealing without email; as I said, these are older printers and I am sure you have them tweaked in a way that works for you. _________________ **************************************
Ockham's razor - usually is the best answer....
************************************** |
|
|
|
|
|
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
|
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
![](templates/Cobalt/images/spacer.gif) |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
![](templates/Cobalt/images/spacer.gif) |