RE: My Exchange 2007 installation guide

RE: My Exchange 2007 installation guide (Full Version)

All Forums >> [Microsoft Exchange 2007] >> Installation

Message

MIDOOooo -> RE: My Exchange 2007 installation guide (20.Jan.2008 11:16:54 AM)
u r welcome anytime @ twoj. glad i could help. u used NTLM and it worked cuz u r connected directly to exchange so need to use kerbros delegation or anything and for using only username it worked fine cuz it's automtically tries to authenticate to the default domain (i.e. ur domian that exchange part of). if u try to publish it with ISA or any other firewall u will face a problem of delegating NTLM authentication to exchange and that;s why u need to make KCD environment. any way good luck

mdjerome -> RE: My Exchange 2007 installation guide (26.Mar.2008 4:03:03 PM)
I truly appreciate your indepth write up on this becasue I have been looking for an alternitive to goin gthe UCC cert path for a while. However the one area that confuses me in your write up is all the server name and domain references.. Most places that have a single server like this have a differnt internal Domain name versus external. Like internally the full server name might be called SV1.abc.local BUT external references to it might be directted to mail.abc.com. My question to you is in your write up when do you use the internal name and when do you use the external?? I can figure this out for the live of me.. In your case is your internal server and domain names the same as your public internet names and domain?? If so is it posible to use your approach when they are different??? Thanks for any help you can provide

MIDOOooo -> RE: My Exchange 2007 installation guide (27.Mar.2008 3:29:58 AM)
it can be done so easily using DNS split approach. if u have 2 names internal srv1.123.com and external mail.abc.com you can use just the external name. go to your internal DNS and create a forward lookup zone named abc.com then create a host(A) record named mail and give the ip address for your internal server. that makes all users inside your organization see your internal server as mail.abc.com though it's named srv1.123.com. if you use exchange anywhere and published through ISA for example you won't need split dns beacuse it will use HTTP proxy in isa. any way hope this help you.

TwoJ -> RE: My Exchange 2007 installation guide (27.Mar.2008 11:17:09 PM)
MIDOOooo is correct (as usual [:)] ) you would want to create a split DNS so that you have two forward lookup zones in your DNS, that way on you LAN you can resolve both your internal domain names, as well as your external domain names. If you have a zone for an external domain name abc.com in your DNS server, it will service any requests for resolution under that domain. So you create the FLZ for abc.com, then enter an A record for mail and point it to your exchange computer's IP If you can its better to have your External & Internal domain names matching but if they don't then this would be the preferred method of dealing with name resolution. I hope this helps

mpalmgren -> RE: My Exchange 2007 installation guide (1.Apr.2009 12:03:07 AM)
I followed your steps, but when connected remotely, I am being prompted for username and password to the exchange server. Is it normal to see the name of the exchange server when being prompted for username and password? I would think it would be better to mask that. Also, no matter how many times I type it in, and whether I use the domain name or not, it immediately prompts me again. Does the certificate need to have the exchange server name in it? I am concerned that since Outlook knows what exchange server I am hitting, it would want the server name listed in the certificate. Should I configure Exchange to use nothing but the external DNS name (remote.company.com) so I am not prompted from server name? Once last item, my AD domain is company.local, but the email domain is company.com. Will your instructions work if the email domain and the AD domain are different?

MIDOOooo -> RE: My Exchange 2007 installation guide (1.Apr.2009 4:17:47 AM)
"I followed your steps, but when connected remotely, I am being prompted for username and password to the exchange server. Is it normal to see the name of the exchange server when being prompted for username and password? I would think it would be better to mask that. Also, no matter how many times I type it in, and whether I use the domain name or not, it immediately prompts me again." that means there's something wrong with authentication settings. did you choose basic authentication?!!! for certificate name, you will need to include all possible in the certificate. http://www.isaserver.org/tutorials/Generating-SSL-Certificates-Exchange-2007-ISA-Server-2006.html "Once last item, my AD domain is company.local, but the email domain is company.com. Will your instructions work if the email domain and the AD domain are different?" check my last post " it can be done so easily using DNS split approach. if u have 2 names internal srv1.123.com and external mail.abc.com you can use just the external name. go to your internal DNS and create a forward lookup zone named abc.com then create a host(A) record named mail and give the ip address for your internal server. that makes all users inside your organization see your internal server as mail.abc.com though it's named srv1.123.com. if you use exchange anywhere and published through ISA for example you won't need split dns beacuse it will use HTTP proxy in isa. any way hope this help you. "

Page: << < prev 1 2 [3]