tell me if this should technically work.... my internal exchange 2003 server name is lets say, exchange.mydomain.net publically, the url that points to owa is mail.mydomain.com so my ssl cert uses mail.mydomain.com as the common name... this all works fine for owa, so im assuming its ok. but i CANT make this work with rpc/http. when trying to connect via outlook, if i use the internal name i get an error saying the name on the cert doesnt match (because the cert has the public name). but if i try to use the public name i just keep getting prompted for my username and passowrd over and over again. what could be the problem here??
disregard... rebooted, all works "Phillip Drummond" wrote in message news:OmQ9D7BDIHA.1208@TK2MSFTNGP03.phx.gbl... > tell me if this should technically work.... > > my internal exchange 2003 server name is lets say, exchange.mydomain.net > publically, the url that points to owa is mail.mydomain.com > > so my ssl cert uses mail.mydomain.com as the common name... this all works > fine for owa, so im assuming its ok. > but i CANT make this work with rpc/http. > > when trying to connect via outlook, if i use the internal name i get an > error saying the name on the cert doesnt match (because the cert has the > public name). but if i try to use the public name i just keep getting > prompted for my username and passowrd over and over again. > > what could be the problem here?? >
