RE: Domain rename with Exchange 2007 server.
Not only is it not supported, it doesn't work. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Leedy, Andy [mailto:ale...@butlerschein.com] Sent: Tuesday, September 14, 2010 4:14 PM To: MS-Exchange Admin Issues Subject: Domain rename with Exchange 2007 server. Can a domain be renamed with an Exchange 2007 server in it? Note: our internal domain is different than our public domain. According Microsoft it is not supported. http://technet.microsoft.com/en-us/library/cc738208(WS.10).aspx Domain rename is also not supported in a forest in which Exchange Server 2007 or Exchange Server 2010 is deployed. Thanks, Andy ** CONFIDENTIALITY NOTICE - The information transmitted in this message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy all copies of this document. Thank you. Butler Schein Animal Health ** --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Domain rename with Exchange 2007 server.
I'm fairly certain you answered your own question. Did I miss something? On Tue, Sep 14, 2010 at 1:13 PM, Leedy, Andy ale...@butlerschein.comwrote: Can a domain be renamed with an Exchange 2007 server in it? Note: our internal domain is different than our public domain. According Microsoft it is not supported. http://technet.microsoft.com/en-us/library/cc738208(WS.10).aspx “Domain rename is also not supported in a forest in which Exchange Server 2007 or Exchange Server 2010 is deployed.” Thanks, Andy ** CONFIDENTIALITY NOTICE - The information transmitted in this message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy all copies of this document. Thank you. Butler Schein Animal Health ** --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Domain rename with Exchange 2007 server.
I can't exactly say that gives me a warm and fuzzy feeling. Sounds like pull the trigger and see if it breaks. :@ -Andy From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, September 14, 2010 4:15 PM To: MS-Exchange Admin Issues Subject: RE: Domain rename with Exchange 2007 server. Not only is it not supported, it doesn't work. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Leedy, Andy [mailto:ale...@butlerschein.com] Sent: Tuesday, September 14, 2010 4:14 PM To: MS-Exchange Admin Issues Subject: Domain rename with Exchange 2007 server. Can a domain be renamed with an Exchange 2007 server in it? Note: our internal domain is different than our public domain. According Microsoft it is not supported. http://technet.microsoft.com/en-us/library/cc738208(WS.10).aspx Domain rename is also not supported in a forest in which Exchange Server 2007 or Exchange Server 2010 is deployed. Thanks, Andy ** CONFIDENTIALITY NOTICE - The information transmitted in this message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy all copies of this document. Thank you. Butler Schein Animal Health ** --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Domain rename with Exchange 2007 server.
On your hands/head be it. Warning: I recommend you don't do it. At all. Don't even try. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Leedy, Andy [mailto:ale...@butlerschein.com] Sent: Tuesday, September 14, 2010 4:48 PM To: MS-Exchange Admin Issues Subject: RE: Domain rename with Exchange 2007 server. I can't exactly say that gives me a warm and fuzzy feeling. Sounds like pull the trigger and see if it breaks. :@ -Andy From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, September 14, 2010 4:15 PM To: MS-Exchange Admin Issues Subject: RE: Domain rename with Exchange 2007 server. Not only is it not supported, it doesn't work. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Leedy, Andy [mailto:ale...@butlerschein.com] Sent: Tuesday, September 14, 2010 4:14 PM To: MS-Exchange Admin Issues Subject: Domain rename with Exchange 2007 server. Can a domain be renamed with an Exchange 2007 server in it? Note: our internal domain is different than our public domain. According Microsoft it is not supported. http://technet.microsoft.com/en-us/library/cc738208(WS.10).aspx Domain rename is also not supported in a forest in which Exchange Server 2007 or Exchange Server 2010 is deployed. Thanks, Andy ** CONFIDENTIALITY NOTICE - The information transmitted in this message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy all copies of this document. Thank you. Butler Schein Animal Health ** --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Domain rename with Exchange 2007 server.
Uhhh, what part of it doesn't work did you miss there... It only works and is only supported under Windows 2003/Exchange 2003. No more, no less... On Tue, Sep 14, 2010 at 1:47 PM, Leedy, Andy ale...@butlerschein.comwrote: I can’t exactly say that gives me a warm and fuzzy feeling. Sounds like pull the trigger and see if it breaks. :@ -Andy *From:* Michael B. Smith [mailto:mich...@smithcons.com] *Sent:* Tuesday, September 14, 2010 4:15 PM *To:* MS-Exchange Admin Issues *Subject:* RE: Domain rename with Exchange 2007 server. Not only is it not supported, it doesn’t work. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com http://theessentialexchange.com/ *From:* Leedy, Andy [mailto:ale...@butlerschein.com] *Sent:* Tuesday, September 14, 2010 4:14 PM *To:* MS-Exchange Admin Issues *Subject:* Domain rename with Exchange 2007 server. Can a domain be renamed with an Exchange 2007 server in it? Note: our internal domain is different than our public domain. According Microsoft it is not supported. http://technet.microsoft.com/en-us/library/cc738208(WS.10).aspx “Domain rename is also not supported in a forest in which Exchange Server 2007 or Exchange Server 2010 is deployed.” Thanks, Andy ** CONFIDENTIALITY NOTICE - The information transmitted in this message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy all copies of this document. Thank you. Butler Schein Animal Health ** --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Domain has unknown Exchange signature
This is a known issue. Ignore it. 12639 is the correct signature value. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: chipsh...@comcast.net [mailto:chipsh...@comcast.net] Sent: Wednesday, March 10, 2010 6:50 AM To: MS-Exchange Admin Issues Subject: Domain has unknown Exchange signature Slowly doing a migration from Exchange 2003 SP2 to Exchange 2010. Using the MS Exchange Best Practices analyzer returns the Domain has an unknown Exchange signature. Ref: http://technet.microsoft.com/en-us/library/aa997081(EXCHG.80).aspx. My objectVersion is 12639. Exchange 2003 was NOT installed using a pre-release version. Additionally, when installing Exchange 2010, part of the install process was a domain prep. I'm trying to determine why this error occurs and if it is something I should take steps to try and correct knowing that the Exchange 2003 server (which is a domain controller) will eventually be retired from the network. If I leave it as it is what are the potential issues this may cause moving forward? Thanks. Steve
Re: Domain has unknown Exchange signature
Thanks Michael. I found several Google threads pertaining to this. It is my perception that Exchange 2010 integration with Exchange 2003 is not fully baked. Exchange signature errors, validation errors, nominated Recipient Update Service errors, home MDB errors etc. etc. and everything seems to point back to the 2003 server. Lots of chasing my tail and never catching it. - Original Message - From: Michael B. Smith michael @ smithcons .com To: MS-Exchange Admin Issues exchangelist @ lyris .sunbelt-software.com Sent: Wednesday, March 10, 2010 8:40:06 AM GMT -05:00 US/Canada Eastern Subject: RE: Domain has unknown Exchange signature This is a known issue. Ignore it. 12639 is the correct signature value. Regards, Michael B. Smith Consultant and Exchange MVP http :// TheEssentialExchange .com From: Chipshead @comcast.net [ mailto : Chipshead @comcast.net] Sent: Wednesday, March 10, 2010 6:50 AM To: MS-Exchange Admin Issues Subject: Domain has unknown Exchange signature Slowly doing a migration from Exchange 2003 SP2 to Exchange 2010. Using the MS Exchange Best Practices analyzer returns the Domain has an unknown Exchange signature. Ref: http :// technet . microsoft .com/en-us/library/aa997081( EXCHG .80). aspx . My objectVersion is 12639. Exchange 2003 was NOT installed using a pre-release version. Additionally, when installing Exchange 2010, part of the install process was a domain prep. I'm trying to determine why this error occurs and if it is something I should take steps to try and correct knowing that the Exchange 2003 server (which is a domain controller) will eventually be retired from the network. If I leave it as it is what are the potential issues this may cause moving forward? Thanks. Steve
Re: Domain/UserID for OWA Logon question
To fix this, use the IIS Internet Service Manager to set the default domain for the Exchange virtual directory to be whatever domain your users' accounts are in --- Kevin Fricke [EMAIL PROTECTED] wrote: In a single domain/single Exchange site with OWA in the same domain but set up as a front end server on it's own box, users must enter domain/userID to get into OWA. Is there a way to force it to always assume a default domain name? List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm __ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Domain/UserID for OWA Logon question
Hello, This is to solve a multi-domain environment but I'd be interested to see if this would work for you. I wonder if the reg hack would do what you're looking for. What do you think? http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q166635; -Original Message- From: Kevin Fricke [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 8:40 AM To: MS-Exchange Admin Issues Subject:Domain/UserID for OWA Logon question In a single domain/single Exchange site with OWA in the same domain but set up as a front end server on it's own box, users must enter domain/userID to get into OWA. Is there a way to force it to always assume a default domain name? List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Re: Domain/UserID for OWA Logon question
search the kb. there are like 3 articles regarding this. Kevin Fricke [EMAIL PROTECTED] wrote in message news:282023@exchangelist... In a single domain/single Exchange site with OWA in the same domain but set up as a front end server on it's own box, users must enter domain/userID to get into OWA. Is there a way to force it to always assume a default domain name? List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Domain/UserID for OWA Logon question
Does this work for Exchange 2000 as well? It says Exchange 5.5. -- Matt Lathrum General Dynamics Decision Systems When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl. -Original Message- From: Mike Newell [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 9:16 AM To: MS-Exchange Admin Issues Subject:RE: Domain/UserID for OWA Logon question Hello, This is to solve a multi-domain environment but I'd be interested to see if this would work for you. I wonder if the reg hack would do what you're looking for. What do you think? http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q166635; -Original Message- From: Kevin Fricke [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 8:40 AM To: MS-Exchange Admin Issues Subject:Domain/UserID for OWA Logon question In a single domain/single Exchange site with OWA in the same domain but set up as a front end server on it's own box, users must enter domain/userID to get into OWA. Is there a way to force it to always assume a default domain name? List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message Good gawd! Y'all not have anything better to do? Why not find out who is better at hacking the network? Or hack each others workstations? If a "hacker" is worth his salt, he won't care if your computer is a member of the domain or not. This is usually because, we don't care if your computers are in a domain or a workgroup, we care about the exploits we find and what we do with those exploits... Once a machine is compromised, you're pretty much "owned" anyway... -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message Domains are more secure. Workgroups in DMZs. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm -- The information contained in this email message is privileged and confidential information intended only for the use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copy of this message is strictly prohibited. If you have received this email in error, please immediately notify Veronis Suhler Stevenson by telephone (212)935-4990, fax (212)381-8168, or email ([EMAIL PROTECTED]) and delete the message. Thank you. ==
RE: domain
Title: Message "If that box gets compromised, then the damage is only limited to that box." Not necessarily... VBEG -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:19 AMTo: MS-Exchange Admin IssuesSubject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message what if youre dual homed. and your internal nic doesnt have a default gateway assigned to it? and Netbios is disabled on the external nic? -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:27 AMTo: MS-Exchange Admin IssuesSubject: RE: domain True; I only meant that the attacker doesn't get default or passthru access to other boxes, as one might if all boxes were in the same domain. -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:15 AMTo: MS-Exchange Admin IssuesSubject: RE: domain "If that box gets compromised, then the damage is only limited to that box." Not necessarily... VBEG -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:19 AMTo: MS-Exchange Admin IssuesSubject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message Ok, but if you have an exchange server, or ISA server on your DMZ, how to you equate it to the production domain? A front end exchange server would have to be in your production Domain.. I would think you would dual home the server, and thus done properly would give you some protection on your production domain but if you have internal clients, putting them in your domain is more secure than putting them in some obscure workgroup right? Then you can use domain policy to lock them down, track activity and so forth right? -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:19 AMTo: MS-Exchange Admin IssuesSubject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message Ok, but if you have an exchange server, or ISA server on your DMZ, how to you equate it to the production domain? A front end exchange server would have to be in your production Domain.. I would think you would dual home the server, and thus done properly would give you some protection on your production domain but if you have internal clients, putting them in your domain is more secure than putting them in some obscure workgroup right? Then you can use domain policy to lock them down, track activity and so forth right? -Original Message-From: Andy David [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:24 AMTo: MS-Exchange Admin IssuesSubject: RE: domain Domains are more secure. Workgroups in DMZs. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm --The information contained in this email message is privileged and confidential information intended only for the use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copy of this message is strictly prohibited. If you have received this email in error, please immediately notify Veronis Suhler Stevenson by telephone (212)935-4990, fax (212)381-8168, or email ([EMAIL PROTECTED]) and delete the message. Thank you.== List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message Martin is dual-homed. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:29 AMTo: MS-Exchange Admin IssuesSubject: RE: domain what if youre dual homed. and your internal nic doesnt have a default gateway assigned to it? and Netbios is disabled on the external nic? -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:27 AMTo: MS-Exchange Admin IssuesSubject: RE: domain True; I only meant that the attacker doesn't get default or passthru access to other boxes, as one might if all boxes were in the same domain. -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:15 AMTo: MS-Exchange Admin IssuesSubject: RE: domain "If that box gets compromised, then the damage is only limited to that box." Not necessarily... VBEG -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:19 AMTo: MS-Exchange Admin IssuesSubject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm -- The information contained in this email message is privileged and confidential information intended only for the use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copy of this message is strictly prohibited. If you have received this email in error, please immediately notify Veronis Suhler Stevenson by telephone (212)935-4990, fax (212)381-8168, or email ([EMAIL PROTECTED]) and delete the message. Thank you. ==
RE: domain
Title: Message Dual-homing is an invite to your internal network... regardless of gateway or disabling NetBios. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:29 AMTo: MS-Exchange Admin IssuesSubject: RE: domain what if youre dual homed. and your internal nic doesnt have a default gateway assigned to it? and Netbios is disabled on the external nic? -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:27 AMTo: MS-Exchange Admin IssuesSubject: RE: domain True; I only meant that the attacker doesn't get default or passthru access to other boxes, as one might if all boxes were in the same domain. -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:15 AMTo: MS-Exchange Admin IssuesSubject: RE: domain "If that box gets compromised, then the damage is only limited to that box." Not necessarily... VBEG -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:19 AMTo: MS-Exchange Admin IssuesSubject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
There are also degrees of difference depending on whether you're talking about an AD domain or a WinNT domain. In AD the forest itself is your security boundary. Although a domain is in fact a security boundary when considering the management aspects of Active Directory, it does not provide complete isolation in the face of possible attacks by service administrators who maliciously modify the behavior of the system. -from http://www.microsoft.com/windows2000/docs/addeladmin.doc -Original Message- From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:19 AM To: MS-Exchange Admin Issues Subject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message- From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AM To: MS-Exchange Admin Issues Subject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains... List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt- software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message A... this is true... -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:27 AMTo: MS-Exchange Admin IssuesSubject: RE: domain True; I only meant that the attacker doesn't get default or passthru access to other boxes, as one might if all boxes were in the same domain. -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:15 AMTo: MS-Exchange Admin IssuesSubject: RE: domain "If that box gets compromised, then the damage is only limited to that box." Not necessarily... VBEG -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:19 AMTo: MS-Exchange Admin IssuesSubject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message If you're putting a FE server in your DMZ, you might as well take the DMZ out of the picture. You are punching far too many holes in your FW to even consider it a FW in this scenario... -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:25 AMTo: MS-Exchange Admin IssuesSubject: RE: domain Ok, but if you have an exchange server, or ISA server on your DMZ, how to you equate it to the production domain? A front end exchange server would have to be in your production Domain.. I would think you would dual home the server, and thus done properly would give you some protection on your production domain but if you have internal clients, putting them in your domain is more secure than putting them in some obscure workgroup right? Then you can use domain policy to lock them down, track activity and so forth right? -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:19 AMTo: MS-Exchange Admin IssuesSubject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message and?? -Original Message-From: Andy David [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:38 AMTo: MS-Exchange Admin IssuesSubject: RE: domain Martin is dual-homed. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:29 AMTo: MS-Exchange Admin IssuesSubject: RE: domain what if youre dual homed. and your internal nic doesnt have a default gateway assigned to it? and Netbios is disabled on the external nic? -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:27 AMTo: MS-Exchange Admin IssuesSubject: RE: domain True; I only meant that the attacker doesn't get default or passthru access to other boxes, as one might if all boxes were in the same domain. -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:15 AMTo: MS-Exchange Admin IssuesSubject: RE: domain "If that box gets compromised, then the damage is only limited to that box." Not necessarily... VBEG -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:19 AMTo: MS-Exchange Admin IssuesSubject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm --The information contained in this email message is privileged and confidential information intended only for the use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copy of this message is strictly prohibited. If you have received this email in error, please immediately notify Veronis Suhler Stevenson by telephone (212)935-4990, fax (212)381-8168, or email ([EMAIL PROTECTED]) and delete the message. Thank you.== List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message But if you are interested in security at all, you don't put an Exchange server on your DMZ. Or any box that has to authenticate with the internal domain, for that matter. It is just dumb. Even with FE/BE, you don't need to put the FE server on the DMZ. You would enable SSL and open port 443 to that server. Ben Winzenz Network/Systems Administrator Peregrine Systems -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:31 AMTo: MS-Exchange Admin IssuesSubject: RE: domain Ok, but if you have an exchange server, or ISA server on your DMZ, how to you equate it to the production domain? A front end exchange server would have to be in your production Domain.. I would think you would dual home the server, and thus done properly would give you some protection on your production domain but if you have internal clients, putting them in your domain is more secure than putting them in some obscure workgroup right? Then you can use domain policy to lock them down, track activity and so forth right? -Original Message-From: Andy David [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:24 AMTo: MS-Exchange Admin IssuesSubject: RE: domain Domains are more secure. Workgroups in DMZs. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm --The information contained in this email message is privileged and confidential information intended only for the use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copy of this message is strictly prohibited. If you have received this email in error, please immediately notify Veronis Suhler Stevenson by telephone (212)935-4990, fax (212)381-8168, or email ([EMAIL PROTECTED]) and delete the message. Thank you.==List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message how so? -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:23 AMTo: MS-Exchange Admin IssuesSubject: RE: domain Dual-homing is an invite to your internal network... regardless of gateway or disabling NetBios. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:29 AMTo: MS-Exchange Admin IssuesSubject: RE: domain what if youre dual homed. and your internal nic doesnt have a default gateway assigned to it? and Netbios is disabled on the external nic? -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:27 AMTo: MS-Exchange Admin IssuesSubject: RE: domain True; I only meant that the attacker doesn't get default or passthru access to other boxes, as one might if all boxes were in the same domain. -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:15 AMTo: MS-Exchange Admin IssuesSubject: RE: domain "If that box gets compromised, then the damage is only limited to that box." Not necessarily... VBEG -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:19 AMTo: MS-Exchange Admin IssuesSubject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message Depends on how you look at it. Is having $100 in one bank more or less secure than having $1 each in 100 different banks? -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]]Sent: Tuesday, July 30, 2002 10:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message I did this for a customer once. Don't remember exactly what he was doing with it, but he insisted he had to have it. Ended up using null modem/RAS/netbios. Connection could only be initiated from the internal network, on a short fuse idle timeout. Best I could come up with and get him what he wanted. -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]]Sent: Tuesday, July 30, 2002 10:23 AMTo: MS-Exchange Admin IssuesSubject: RE: domain Dual-homing is an invite to your internal network... regardless of gateway or disabling NetBios. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:29 AMTo: MS-Exchange Admin IssuesSubject: RE: domain what if youre dual homed. and your internal nic doesnt have a default gateway assigned to it? and Netbios is disabled on the external nic? -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:27 AMTo: MS-Exchange Admin IssuesSubject: RE: domain True; I only meant that the attacker doesn't get default or passthru access to other boxes, as one might if all boxes were in the same domain. -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:15 AMTo: MS-Exchange Admin IssuesSubject: RE: domain If that box gets compromised, then the damage is only limited to that box. Not necessarily... VBEG -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:19 AMTo: MS-Exchange Admin IssuesSubject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message Sorry, I don't disclose that kind of information. Let's just say if you dual-homed a machine and I was scanning your network and found it... well, it would bea fun time had by all... -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:43 AMTo: MS-Exchange Admin IssuesSubject: RE: domain how so? -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:23 AMTo: MS-Exchange Admin IssuesSubject: RE: domain Dual-homing is an invite to your internal network... regardless of gateway or disabling NetBios. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:29 AMTo: MS-Exchange Admin IssuesSubject: RE: domain what if youre dual homed. and your internal nic doesnt have a default gateway assigned to it? and Netbios is disabled on the external nic? -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:27 AMTo: MS-Exchange Admin IssuesSubject: RE: domain True; I only meant that the attacker doesn't get default or passthru access to other boxes, as one might if all boxes were in the same domain. -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:15 AMTo: MS-Exchange Admin IssuesSubject: RE: domain "If that box gets compromised, then the damage is only limited to that box." Not necessarily... VBEG -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:19 AMTo: MS-Exchange Admin IssuesSubject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup in workgoups and not domains...List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message
Now
that's an interesting configuration... :o)
-Original Message-From: Campbell, Rob
[mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30,
2002 12:01 PMTo: MS-Exchange Admin IssuesSubject: RE:
domain
I
did this for a customer once. Don't remember exactly what he was doing
with it, but he insisted he had to have it.
Ended up using null modem/RAS/netbios. Connection could only be
initiated from the internal network, on a "short fuse" idle timeout.
Best I could come up with and get him what he wanted.
-Original Message-From: Ely, Don
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, July 30, 2002
10:23 AMTo: MS-Exchange Admin IssuesSubject: RE:
domain
Dual-homing is an invite to your internal network... regardless
of gateway or disabling NetBios.
-Original Message-From: MHR(Michael
Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002
11:29 AMTo: MS-Exchange Admin IssuesSubject: RE:
domain
what if youre dual homed. and your internal nic doesnt have a
default gateway assigned to it? and Netbios is disabled on the external
nic?
-Original Message-From: Erik Sojka
[mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:27
AMTo: MS-Exchange Admin IssuesSubject: RE:
domain
True; I only meant that the attacker doesn't get default or
passthru access to other boxes, as one might if all boxes were in the
same domain.
-Original Message-From: Ely, Don
[mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30,
2002 11:15 AMTo: MS-Exchange Admin
IssuesSubject: RE: domain
"If that box gets compromised, then the
damage is only limited to that box."
Not necessarily...
VBEG
-Original Message-From: Erik
Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30,
2002 11:19 AMTo: MS-Exchange Admin
IssuesSubject: RE: domain
That's a wide open question. Are you talking for an
internal network or just for a DMZ deployment?
A box in the DMZ should be in its own separate thing (domain
or WG, doesn't matter which). If that box gets compromised,
then the damage is only limited to that box. The attacker
doesn't also get access to the production domain or any other DMZ
boxes.
-Original
Message-From: MHR(Michael Ross)
[mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002
11:17 AMTo: MS-Exchange Admin IssuesSubject:
domain
Can
anyone settle a bet?
I have
a coworker who is saying a workgroup is more secure than a domain,
I say its the otherway around.
He is
also betting me that any servers setup in your DMZ should be setup
in workgoups and not domains...List Charter
and FAQ
at:http://www.sunbelt-software.com/exchange_list_charter.htmList
Charter and FAQ
at:http://www.sunbelt-software.com/exchange_list_charter.htmList
Charter and FAQ
at:http://www.sunbelt-software.com/exchange_list_charter.htmList
Charter and FAQ
at:http://www.sunbelt-software.com/exchange_list_charter.htmList
Charter and FAQ
at:http://www.sunbelt-software.com/exchange_list_charter.htmList
Charter and FAQ
at:http://www.sunbelt-software.com/exchange_list_charter.htmList
Charter and FAQ
at:http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain
Title: Message Actually that should have been null modem/RAS/netbeui. Anyway, it worked. Basically it was a back door that only opened one way. Hopefully it was just too weird for a hacker to look for or want to mess with. -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]]Sent: Tuesday, July 30, 2002 12:40 PMTo: MS-Exchange Admin IssuesSubject: RE: domain Now that's an interesting configuration... :o) -Original Message-From: Campbell, Rob [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 12:01 PMTo: MS-Exchange Admin IssuesSubject: RE: domain I did this for a customer once. Don't remember exactly what he was doing with it, but he insisted he had to have it. Ended up using null modem/RAS/netbios. Connection could only be initiated from the internal network, on a short fuse idle timeout. Best I could come up with and get him what he wanted. -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]]Sent: Tuesday, July 30, 2002 10:23 AMTo: MS-Exchange Admin IssuesSubject: RE: domain Dual-homing is an invite to your internal network... regardless of gateway or disabling NetBios. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:29 AMTo: MS-Exchange Admin IssuesSubject: RE: domain what if youre dual homed. and your internal nic doesnt have a default gateway assigned to it? and Netbios is disabled on the external nic? -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 10:27 AMTo: MS-Exchange Admin IssuesSubject: RE: domain True; I only meant that the attacker doesn't get default or passthru access to other boxes, as one might if all boxes were in the same domain. -Original Message-From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:15 AMTo: MS-Exchange Admin IssuesSubject: RE: domain If that box gets compromised, then the damage is only limited to that box. Not necessarily... VBEG -Original Message-From: Erik Sojka [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:19 AMTo: MS-Exchange Admin IssuesSubject: RE: domain That's a wide open question. Are you talking for an internal network or just for a DMZ deployment? A box in the DMZ should be in its own separate thing (domain or WG, doesn't matter which). If that box gets compromised, then the damage is only limited to that box. The attacker doesn't also get access to the production domain or any other DMZ boxes. -Original Message-From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 11:17 AMTo: MS-Exchange Admin IssuesSubject: domain Can anyone settle a bet? I have a coworker who is saying a workgroup is more secure than a domain, I say its the otherway around. He is also betting me that any servers setup in your DMZ should be setup
RE: Domain name in logon?
Title: Message
then
you need to make their username user@domain
:)
Or
play with .net server pop3 server that works that way
-Original Message-From: Brent McCrary
[mailto:[EMAIL PROTECTED]] Sent: Friday, June 21, 2002 3:40
PMTo: MS-Exchange Admin IssuesSubject: Re: Domain name
in logon?
When they logon via Outlook or Outlook Express
I'd like them to have to put their full address in the "account name"
field.
- Original Message -
From:
Matthew
Carpenter
To: MS-Exchange Admin
Issues
Sent: Friday, June 21, 2002 2:36
PM
Subject: Re: Domain name in
logon?
Where are you referring?
On OWA? Check Name on a profile set
up?
- Original Message -
From:
Brent
McCrary
To: MS-Exchange Admin
Issues
Sent: Friday, June 21, 2002 2:33
PM
Subject: Domain name in logon?
Anyone know how can I make my Exchange 5.5
server accept the "@domain-name.com" after my account name?
I only have 1 domain, but I still would like
users to enter their full email address.
Thanks,Brent McCrary
kcconnect.net
List Charter and FAQ
at:http://www.sunbelt-software.com/exchange_list_charter.htmList
Charter and FAQ
at:http://www.sunbelt-software.com/exchange_list_charter.htmList
Charter and FAQ
at:http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
Re: Domain name in logon?
Title: RE: Mail Sending order problems Where are you referring? On OWA? Check Name on a profile set up? - Original Message - From: Brent McCrary To: MS-Exchange Admin Issues Sent: Friday, June 21, 2002 2:33 PM Subject: Domain name in logon? Anyone know how can I make my Exchange 5.5 server accept the "@domain-name.com" after my account name? I only have 1 domain, but I still would like users to enter their full email address. Thanks,Brent McCrary kcconnect.net List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Domain name in logon?
Title: Message in OWA or Outlook ? -Original Message-From: Brent McCrary [mailto:[EMAIL PROTECTED]] Sent: Friday, June 21, 2002 15:33To: MS-Exchange Admin IssuesSubject: Domain name in logon? Anyone know how can I make my Exchange 5.5 server accept the "@domain-name.com" after my account name? I only have 1 domain, but I still would like users to enter their full email address. Thanks,Brent McCrary kcconnect.net List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Re: Domain name in logon?
Title: RE: Mail Sending order problems When they logon via Outlook or Outlook Express I'd like them to have to put their full address in the "account name" field. - Original Message - From: Matthew Carpenter To: MS-Exchange Admin Issues Sent: Friday, June 21, 2002 2:36 PM Subject: Re: Domain name in logon? Where are you referring? On OWA? Check Name on a profile set up? - Original Message - From: Brent McCrary To: MS-Exchange Admin Issues Sent: Friday, June 21, 2002 2:33 PM Subject: Domain name in logon? Anyone know how can I make my Exchange 5.5 server accept the "@domain-name.com" after my account name? I only have 1 domain, but I still would like users to enter their full email address. Thanks,Brent McCrary kcconnect.net List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Domain name change
Multihomed, keep both Ip's running for a few weeks.. thats what I did.. If you are not changing the ip's then simply keep both MX records running for a while.. -Original Message- From: Dawson, Valencia [mailto:[EMAIL PROTECTED]] Sent: 03 May 2002 06:04 To: MS-Exchange Admin Issues Subject: Domain name change We will soon be changing domain names. If any of you have recently undergone this please advise me of the steps to take. We are using WindowsNT/Exchange 5.5 with Outlook 98/200/XP. What changes do I make on the Exchange server to reflect this change? How do I make an easy transition so people can get mail from both the new and the old at least for a while? How do I make the change so the email addresses at least going out will reflect the new name. Any help in the right direction will be appreciated. Thank you List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Re: Domain name change
http://www.swinc.com/resource/exch_faq_appxk.htm - Original Message - From: Dawson, Valencia [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Friday, May 03, 2002 12:03 PM Subject: Domain name change We will soon be changing domain names. If any of you have recently undergone this please advise me of the steps to take. We are using WindowsNT/Exchange 5.5 with Outlook 98/200/XP. What changes do I make on the Exchange server to reflect this change? How do I make an easy transition so people can get mail from both the new and the old at least for a while? How do I make the change so the email addresses at least going out will reflect the new name. Any help in the right direction will be appreciated. Thank you List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Domain name change
The domain name is what is changing- email address etc. I am not moving the server to a new domain. -Original Message- From: Missy Koslosky [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 12:16 PM To: MS-Exchange Admin Issues Subject: Re: Domain name change http://www.swinc.com/resource/exch_faq_appxk.htm - Original Message - From: Dawson, Valencia [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Friday, May 03, 2002 12:03 PM Subject: Domain name change We will soon be changing domain names. If any of you have recently undergone this please advise me of the steps to take. We are using WindowsNT/Exchange 5.5 with Outlook 98/200/XP. What changes do I make on the Exchange server to reflect this change? How do I make an easy transition so people can get mail from both the new and the old at least for a while? How do I make the change so the email addresses at least going out will reflect the new name. Any help in the right direction will be appreciated. Thank you List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Domain name change
Will you be moving over to a new IP range as well? Regards Ruan -Original Message- From: Dawson, Valencia [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 6:38 PM To: MS-Exchange Admin Issues Subject: RE: Domain name change The domain name is what is changing- email address etc. I am not moving the server to a new domain. -Original Message- From: Missy Koslosky [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 12:16 PM To: MS-Exchange Admin Issues Subject: Re: Domain name change http://www.swinc.com/resource/exch_faq_appxk.htm - Original Message - From: Dawson, Valencia [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Friday, May 03, 2002 12:03 PM Subject: Domain name change We will soon be changing domain names. If any of you have recently undergone this please advise me of the steps to take. We are using WindowsNT/Exchange 5.5 with Outlook 98/200/XP. What changes do I make on the Exchange server to reflect this change? How do I make an easy transition so people can get mail from both the new and the old at least for a while? How do I make the change so the email addresses at least going out will reflect the new name. Any help in the right direction will be appreciated. Thank you List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Domain name change
That was already done. -Original Message- From: Ruan Kotze - CPX NAM [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 11:47 AM To: MS-Exchange Admin Issues Subject: RE: Domain name change Will you be moving over to a new IP range as well? Regards Ruan -Original Message- From: Dawson, Valencia [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 6:38 PM To: MS-Exchange Admin Issues Subject: RE: Domain name change The domain name is what is changing- email address etc. I am not moving the server to a new domain. -Original Message- From: Missy Koslosky [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 12:16 PM To: MS-Exchange Admin Issues Subject: Re: Domain name change http://www.swinc.com/resource/exch_faq_appxk.htm - Original Message - From: Dawson, Valencia [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Friday, May 03, 2002 12:03 PM Subject: Domain name change We will soon be changing domain names. If any of you have recently undergone this please advise me of the steps to take. We are using WindowsNT/Exchange 5.5 with Outlook 98/200/XP. What changes do I make on the Exchange server to reflect this change? How do I make an easy transition so people can get mail from both the new and the old at least for a while? How do I make the change so the email addresses at least going out will reflect the new name. Any help in the right direction will be appreciated. Thank you List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Domain name change
In that case you'll need to have two smtp addresses on each mailbox, one for the old and one for the new domain. Change the MX and A records on the old domain to point to the new ip, and you'll be all set. If your old domain doesn't exist anymore, you'll have to re-register it. Regards Ruan -Original Message- From: Dawson, Valencia [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 6:53 PM To: MS-Exchange Admin Issues Subject: RE: Domain name change That was already done. -Original Message- From: Ruan Kotze - CPX NAM [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 11:47 AM To: MS-Exchange Admin Issues Subject: RE: Domain name change Will you be moving over to a new IP range as well? Regards Ruan -Original Message- From: Dawson, Valencia [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 6:38 PM To: MS-Exchange Admin Issues Subject: RE: Domain name change The domain name is what is changing- email address etc. I am not moving the server to a new domain. -Original Message- From: Missy Koslosky [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 12:16 PM To: MS-Exchange Admin Issues Subject: Re: Domain name change http://www.swinc.com/resource/exch_faq_appxk.htm - Original Message - From: Dawson, Valencia [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Friday, May 03, 2002 12:03 PM Subject: Domain name change We will soon be changing domain names. If any of you have recently undergone this please advise me of the steps to take. We are using WindowsNT/Exchange 5.5 with Outlook 98/200/XP. What changes do I make on the Exchange server to reflect this change? How do I make an easy transition so people can get mail from both the new and the old at least for a while? How do I make the change so the email addresses at least going out will reflect the new name. Any help in the right direction will be appreciated. Thank you List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Re: Domain name change
Oh. Duh. Add the new addresses to your GAL. You'll need to: 1) Export your current GAL to a CSV. 2) Create a new header called secondary-proxy addresses. 3) Copy all current domain SMTP addresses to the new field. Format MUST be smtp:[EMAIL PROTECTED] - note lower case smtp. 4) Create new SMTP addresses for all users (if your localpart is remaining the same, simply replace the old name with the new in the e-mail addresses column). 5) Import your changes. Q155414 should help if you're unfamiliar with import export processes. And add an MX record in DNS for the new domain. Better? - Original Message - From: Dawson, Valencia [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Friday, May 03, 2002 12:37 PM Subject: RE: Domain name change The domain name is what is changing- email address etc. I am not moving the server to a new domain. -Original Message- From: Missy Koslosky [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 12:16 PM To: MS-Exchange Admin Issues Subject: Re: Domain name change http://www.swinc.com/resource/exch_faq_appxk.htm - Original Message - From: Dawson, Valencia [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Friday, May 03, 2002 12:03 PM Subject: Domain name change We will soon be changing domain names. If any of you have recently undergone this please advise me of the steps to take. We are using WindowsNT/Exchange 5.5 with Outlook 98/200/XP. What changes do I make on the Exchange server to reflect this change? How do I make an easy transition so people can get mail from both the new and the old at least for a while? How do I make the change so the email addresses at least going out will reflect the new name. Any help in the right direction will be appreciated. Thank you List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Domain name change
Don't forget to change the settings on what ever you use for anti-relaying to accept mail for the new domain. -Original Message- From: Missy Koslosky [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 1:08 PM To: MS-Exchange Admin Issues Subject: Re: Domain name change Oh. Duh. Add the new addresses to your GAL. You'll need to: 1) Export your current GAL to a CSV. 2) Create a new header called secondary-proxy addresses. 3) Copy all current domain SMTP addresses to the new field. Format MUST be smtp:[EMAIL PROTECTED] - note lower case smtp. 4) Create new SMTP addresses for all users (if your localpart is remaining the same, simply replace the old name with the new in the e-mail addresses column). 5) Import your changes. Q155414 should help if you're unfamiliar with import export processes. And add an MX record in DNS for the new domain. Better? - Original Message - From: Dawson, Valencia [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Friday, May 03, 2002 12:37 PM Subject: RE: Domain name change The domain name is what is changing- email address etc. I am not moving the server to a new domain. -Original Message- From: Missy Koslosky [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 12:16 PM To: MS-Exchange Admin Issues Subject: Re: Domain name change http://www.swinc.com/resource/exch_faq_appxk.htm - Original Message - From: Dawson, Valencia [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Friday, May 03, 2002 12:03 PM Subject: Domain name change We will soon be changing domain names. If any of you have recently undergone this please advise me of the steps to take. We are using WindowsNT/Exchange 5.5 with Outlook 98/200/XP. What changes do I make on the Exchange server to reflect this change? How do I make an easy transition so people can get mail from both the new and the old at least for a while? How do I make the change so the email addresses at least going out will reflect the new name. Any help in the right direction will be appreciated. Thank you List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Domain name change
I think I am on my way now. Thank you all. -Original Message- From: Schwartz, Jim [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 1:11 PM To: MS-Exchange Admin Issues Subject: RE: Domain name change Don't forget to change the settings on what ever you use for anti-relaying to accept mail for the new domain. -Original Message- From: Missy Koslosky [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 1:08 PM To: MS-Exchange Admin Issues Subject: Re: Domain name change Oh. Duh. Add the new addresses to your GAL. You'll need to: 1) Export your current GAL to a CSV. 2) Create a new header called secondary-proxy addresses. 3) Copy all current domain SMTP addresses to the new field. Format MUST be smtp:[EMAIL PROTECTED] - note lower case smtp. 4) Create new SMTP addresses for all users (if your localpart is remaining the same, simply replace the old name with the new in the e-mail addresses column). 5) Import your changes. Q155414 should help if you're unfamiliar with import export processes. And add an MX record in DNS for the new domain. Better? - Original Message - From: Dawson, Valencia [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Friday, May 03, 2002 12:37 PM Subject: RE: Domain name change The domain name is what is changing- email address etc. I am not moving the server to a new domain. -Original Message- From: Missy Koslosky [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 12:16 PM To: MS-Exchange Admin Issues Subject: Re: Domain name change http://www.swinc.com/resource/exch_faq_appxk.htm - Original Message - From: Dawson, Valencia [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Friday, May 03, 2002 12:03 PM Subject: Domain name change We will soon be changing domain names. If any of you have recently undergone this please advise me of the steps to take. We are using WindowsNT/Exchange 5.5 with Outlook 98/200/XP. What changes do I make on the Exchange server to reflect this change? How do I make an easy transition so people can get mail from both the new and the old at least for a while? How do I make the change so the email addresses at least going out will reflect the new name. Any help in the right direction will be appreciated. Thank you List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Re: Domain name change
Dear friend, 1. create a recipient policy that creates the new (second) smtp-address for each of the users (like @second.com). You can do that in e2k system manager. 2. Create an MX record in the internet-dns that directs internet mail designated for the new second adress (second.com) to the smtp-connector of your e2k-organisation (may be the same e2k-server). 3. if your users should be represented with the new domain name, so you can decide to take the new smtp-address as first-address in response mails. 3. for your outlook users the whole thing is transparent - you have to do nothing. But it's better to inform the users to take the new address in their signature and so on... Mit freundlichen Grüßen Hans Willi Kremer * freiberuflicher Dozent und Berater, * MCDBA, MCSE +I, MCSD, MCT, * Schwerpunkte SQL-Server Exchange Server, * Buchautor zum SQL Server im Galileo-Press Verlag Website: HTTP:[EMAIL PROTECTED] Mail: mailto:[EMAIL PROTECTED] Telefon: 0241 / 1681727 Privat: 0241 / 9319743 Küppershofweg 6 - 52134 Herzogenrath / Aachen -Ursprüngliche Nachricht- Von: dp [mailto:[EMAIL PROTECTED]] Gesendet: Sonntag, 4. November 2001 05:44 An: MS-Exchange Admin Issues Betreff: RE: Domain name change Have both addresses in SMTP ? Forward old to new? -Original Message- From: Tianhong Zhang [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 01, 2001 10:20 To: MS-Exchange Admin Issues Subject: Domain name change Our domain will be changed soon. So the email will be change too. What should I do in order to let users to get the email from old and new email address both. We use Exchange 2000 and Outlook98/2000. Thanks Tianhong List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Domain name change
1) configure MX records. 2) add second domain through default recipient policy (or your custom recipient policy) william -Original Message- From: Tianhong Zhang [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 01, 2001 7:20 AM To: MS-Exchange Admin Issues Subject: Domain name change Our domain will be changed soon. So the email will be change too. What should I do in order to let users to get the email from old and new email address both. We use Exchange 2000 and Outlook98/2000. Thanks Tianhong List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Domain type stuck in IMS
Sounds like a DNS problem. If you're using an internal DNS that's doing forwarding make sure there hasn't been a .net zone created on your internal DNS. -Original Message- From: Errol Parker [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 7:38 AM To: MS-Exchange Admin Issues Subject: Domain type stuck in IMS I sent a note yesterday regarding a particular domain (earthlink.net) stuck in the IMS. It seems that it is not just one domain, but one domain type sitting in the outbound queue. The emails stuck are all .net domain types. Anyone else experience this? List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain name problems with exchange
*curtsy* You're quite welcome! -Michèle Immigration site: http://LadySun1969.tripod.com Our new 2001 Miata: http://members.cardomain.com/bpituley Tiggercam: http://www.tiggercam.co.uk - Murphy's Technology Laws Murphy's Technology Law #1: You can never tell which way the train went by looking at the track. - -Original Message- From: Clark, Steve [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 5:29 PM To: MS-Exchange Admin Issues Subject: RE: domain name problems with exchange Thank you. It's always nice to see the word breast thrown in any conversation. Tends to lift the general content of the conversation. Steve Clark Clark Systems Support, LLC AVIEN Charter Member www.clarksupport.com 301-610-9584 voice 240-465-0323 Efax -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 4:42 PM To: MS-Exchange Admin Issues Subject: RE: domain name problems with exchange Freudian slipcovers -- keep your furniture looking its breast. er, I mean best -Michèle Immigration site: http://LadySun1969.tripod.com Our new 2001 Miata: http://members.cardomain.com/bpituley Tiggercam: http://www.tiggercam.co.uk - The fact that no one understands you doesn't mean you're an artist. - -Original Message- From: Lefkovics, William [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 4:15 PM To: MS-Exchange Admin Issues Subject: RE: domain name problems with exchange Freudian record slip? -Original Message- From: Chris Hampton [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 12:03 PM To: MS-Exchange Admin Issues Subject: RE: domain name problems with exchange Gentlemen, Thanks for the help. MY DNS gay had messed up the record and it is now fixed thanks Chris List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain name problems with exchange
As a side note, mail.rootcandles.com does have records, but since you decided not to use that, the point is moot. -Original Message- From: Chris Hampton [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 5:55 AM To: MS-Exchange Admin Issues Subject: domain name problems with exchange My mansgement and I wanted to call our email server mail.rootcandles.com after discussion with the other execs he cameback and told me to change it to rootcandles.com(-mail.) I changes the dns entries on all of the accounts to have both and the mx record to reflect the needed change and it gives me this error. A mail message was not sent due to a protocol error. 511 5.0.0 [EMAIL PROTECTED]... Sorry [209.221.23.134], Invalid address rootcandles.com. The message that caused this notification was: To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Subject: test Does anyone have any ideas. Thanks In Advanced. Chris __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain name problems with exchange
Is rootcandles.com(-mail.) even a valid host name?? -Michèle Immigration site: http://LadySun1969.tripod.com Our new 2001 Miata: http://members.cardomain.com/bpituley Tiggercam: http://www.tiggercam.co.uk - Standards are like toothbrushes. Everybody agrees you should have one, but no one wants to use yours. - -Original Message- From: Chris Hampton [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 8:55 AM To: MS-Exchange Admin Issues Subject: domain name problems with exchange My mansgement and I wanted to call our email server mail.rootcandles.com after discussion with the other execs he cameback and told me to change it to rootcandles.com(-mail.) I changes the dns entries on all of the accounts to have both and the mx record to reflect the needed change and it gives me this error. A mail message was not sent due to a protocol error. 511 5.0.0 [EMAIL PROTECTED]... Sorry [209.221.23.134], Invalid address rootcandles.com. The message that caused this notification was: To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Subject: test Does anyone have any ideas. Thanks In Advanced. Chris __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain name problems with exchange
I think what he meant was the he removed the mail part... I had to think about it for few minutes. If he didnt, that is the most hosed name I have ever seen. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 6:08 AM To: MS-Exchange Admin Issues Subject: RE: domain name problems with exchange Is rootcandles.com(-mail.) even a valid host name?? -Michèle Immigration site: http://LadySun1969.tripod.com Our new 2001 Miata: http://members.cardomain.com/bpituley Tiggercam: http://www.tiggercam.co.uk - Standards are like toothbrushes. Everybody agrees you should have one, but no one wants to use yours. - -Original Message- From: Chris Hampton [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 8:55 AM To: MS-Exchange Admin Issues Subject: domain name problems with exchange My mansgement and I wanted to call our email server mail.rootcandles.com after discussion with the other execs he cameback and told me to change it to rootcandles.com(-mail.) I changes the dns entries on all of the accounts to have both and the mx record to reflect the needed change and it gives me this error. A mail message was not sent due to a protocol error. 511 5.0.0 [EMAIL PROTECTED]... Sorry [209.221.23.134], Invalid address rootcandles.com. The message that caused this notification was: To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Subject: test Does anyone have any ideas. Thanks In Advanced. Chris __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain name problems with exchange
Gentlemen, Thanks for the help. MY DNS gay had messed up the record and it is now fixed thanks Chris __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain name problems with exchange
Does he know he's the DNS gay? -Original Message- From: Chris Hampton [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 2:03 PM To: MS-Exchange Admin Issues Subject: RE: domain name problems with exchange Gentlemen, Thanks for the help. MY DNS gay had messed up the record and it is now fixed thanks Chris __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain name problems with exchange
Freudian record slip? -Original Message- From: Chris Hampton [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 12:03 PM To: MS-Exchange Admin Issues Subject: RE: domain name problems with exchange Gentlemen, Thanks for the help. MY DNS gay had messed up the record and it is now fixed thanks Chris List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: domain name problems with exchange
Thank you. It's always nice to see the word breast thrown in any conversation. Tends to lift the general content of the conversation. Steve Clark Clark Systems Support, LLC AVIEN Charter Member www.clarksupport.com 301-610-9584 voice 240-465-0323 Efax -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 4:42 PM To: MS-Exchange Admin Issues Subject: RE: domain name problems with exchange Freudian slipcovers -- keep your furniture looking its breast. er, I mean best -Michèle Immigration site: http://LadySun1969.tripod.com Our new 2001 Miata: http://members.cardomain.com/bpituley Tiggercam: http://www.tiggercam.co.uk - The fact that no one understands you doesn't mean you're an artist. - -Original Message- From: Lefkovics, William [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 4:15 PM To: MS-Exchange Admin Issues Subject: RE: domain name problems with exchange Freudian record slip? -Original Message- From: Chris Hampton [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 12:03 PM To: MS-Exchange Admin Issues Subject: RE: domain name problems with exchange Gentlemen, Thanks for the help. MY DNS gay had messed up the record and it is now fixed thanks Chris List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
