Yes, I understand the context you're using for this. Do you have all the correct ports forwarded through your NAT router?
The configuration on the router worked on version 3.0 but not on 3.1. It stayed unchanged over the upgrade.
(I forward the ports 80 143 443 7071)
... and the request for the login screen is forwarded correctly by the router and the the page is delivered to the client outside.
Appending ?redirect=0 to the url on client side solves the problem.
Last edited by winne27; 04-25-2006 at 12:47 AM.
I got burned by this too. Was working fine in 3.0.1 but after switch to 3.1 it redirects to the servers local name which is not a publicly available name. So nobody can get past the login screen.
I've got several hundred users, so unless I can get the redirect=0 appended by default, that isn't a good option for me.