I am getting this message when manually logging into the FTP server i have setup for Maxexchange :

Connected to 192.168.10.2.
220 Connected to - Win32 FTP server
User (192.168.10.2none)): maxexchange
331 anonymous access allowed, send email name as PASS
Password:
530 User cannot log in
Login failed.

however, if i login with the credentials i have set for 'Guest' :

Connected to 192.168.10.2.
220 Connected to - Win32 FTP server
User (192.168.10.2none)): guest
331 anonymous access allowed, send email name as PASS
Password:
230-logon successful
230-==========================
230- Welcome to our FTP site!
230 ==========================


Now, I have done the following multiple times :

Shutdown & Restarted Maxexchange Server Manager & Maxexchange Service
Switched ports from 21 to 20 and vice versa
Tested FTP access on the Local MaxExchange server
Uninstalled and Reinstalled MaxExchange

Every time, I can login as guest, but cannot login as the Maxexchange user, has anyone encountered this before?

Hi,

What password did you use for 'Maxexchange'?

Re try with 'CONTROL'

Regards,

Ozzy

Thanks,
I've since Tried with :
'test' (setting at time)
'1234567890' (setting at time)
'CONTROL'
'control'

Same message every time. Have restarted service and remote manager numerous times, still no change.

I notice this is the same message as invalid Users receive. Anyone know more details on the FTP Server being used by Maxexchange?

Ok, had a callback from Maximizer support...

Admittedly, I'm feeling a little stupid on this one.

While the manual says to 'Restart the Service' after changing the passwords, this is not sufficient for it to take.
Open up TaskManager
and End the following processes :
spdm.exe
meclient.exe

and any other 'Maximizer Like' processes (only if you are comfortable doing so). The other suggested method is to restart the computer entirely (if its a required server, also sometimes undesirable)

This will allow the password change to take effect.

Now, i can login without issues.

Yes, it is important to remember that even if you have stopped the service you may still have the Server/Site Manager running minimised in the system tray.

As a rule of thumb all Maximizer related processes and applications should be shutdown when doing things like changing passwords and/or installing service packs.

Thanks for the help.

Just for Full Details of what was happening,

I was stopping the Maximizer Exchange Service in the services, AND closing all Maximizer windows / icons / taskbar items.

Unfortunately, I didn't realize that there were still additional background processes running that were not stopped / shutdown by the above procedure. Something to remember if facing this challenge.

On a side note, now that FTP is working, Maxexchange seems to be about 1000% better to use from the end user experience. Wish I had of set this up this way from the start.

Yeah sometime the wrapper processes don't terminate correctly when you shutdown the services, we've reported this to Maximizer for testing.

Also, when it comes to Max Exchange we would always recommend that you use the FTP processing as it is very fast and reliable.