Firetrust Support Forums

I got a problem where a client using mail washer pro is hanging the server that has mail enable on it and running mail washer Enterprise.
It looks as though DNS gets over whelmed. You open a dos box and you cannot ping a domain name. Rebooting the mail server is the only way I have gotten it to send the mail that is hung. Is there some kind of incompatibility issue with washer pro and washer enterprise?

No, there shouldn't be and we use both all the time.

Perhaps you can go to MW Enterprise>>Settings>>General>>Logging, and change it to High. Then when the problem occurs, go to the logs at:

Windows: C:\Program Files\MailWasher Enterprise Server\logs
Linux: \var\log\mwes

And send them to me at nick.bolton@firetrust.com and we should be able to see what's going on.

Thanks

thanks will do that but here is the second issue I cannot log on to the admin account. How do I find the password or reset it?

Gene

I also replied to that

http://www.firetrust.com/en/products/ma ... d-password

Thanks set to high now. It hangs about once a week. Nothing showing in the Microsoft logs or the Mail enable logs about any Issue.

How do I find the version I have of mail washer server?

If you login and look at the program logo, you'll see the version number scroll along under it. Current version 3.0.0.6

Curiously we have another user with this issue as well, they're using SBS - are you? Can you let me know what you're running there?

Thanks

Give this a try
http://cdn.firetrust.com/downloads/mwes ... r-3008.exe

It has a few options for DNS

1. If this problem occurs, it will deregister the socket DLL and re-register it so DNS will work again. This is better than restarting MWES
2. It will use all nameservers if any others are setup instead of just one.
3. We can set a flag in the registry to use an external DNS specified.

The aforementioned solution is not working for me. Is there any other way to get it fix?TragusInfantigoRx

Still working on a fix for this, it's been really difficult to pin down as we need to replicate it to fix it.

For now, try restarting the 'Mailwasher Enterprise Server' Service (Start>>Run>>Services.msc) and then right click on the service, select 'Properties', then the 'Recovery' tab and choose to restart after a failure.

Can you try this and see if it fixes things?
http://cdn.firetrust.com/downloads/mwes ... r-3013.exe