Exchange 2003 in Trusted Forest - Microsoft Exchange |
- Exchange 2003 in Trusted Forest
- Email attachments arrive with 0K and empty at external addresses
- buku ndr's and failure notices
- OWA Access for 2 Servers - Same Org - Different MX?
- How do I find...
- How to tell exchange he is no longer responsible for a domain
- Auto message to new or Moved users?
- 501 Sender IP must resolve
- Modifying Contact Views on the Exchange Server
- forwarding external email addresses to Microsoft exchange email address
- Default Global Address List is missing from All Global Address Lis
- OWA and SSL
- Urgent !! please help Exchnage 2003 , AD and DNS problem
- OWA-The Local Security Authority cannot be contacted
Exchange 2003 in Trusted Forest Posted: 01 Nov 2006 12:47 PM PST That is correct. I was hoping that we would be able to see each others Global Address Books too. We are in the process of merging two organizations and we are both using Exchange 2003 in a Windows 2003 environment as I indicated. We do want to have each of us see the public folders and the busy/free, but I was also hoping for the Global Address Books. Thanks "Ed Crowley [MVP]" wrote: |
Email attachments arrive with 0K and empty at external addresses Posted: 01 Nov 2006 07:53 AM PST Apologies for the lack of information. The details of our outgoing gateways are: Exchange 2003 SP2 Symantec Mail security for Exchange ver 4.6 MS Exchange IMF v2 mxClaim v3.1 (Discalimer add-on) Sending an email via a different gateway that doesn't have the IMF or mxclaim on works ok. Contacted producers of mxclaim and they could not reproduce problem. Only affects certain files and often resaving the file allows the file to be sent. I posted on the off chance that someone might had a similar problem TIA "Ed Crowley [MVP]" wrote: |
buku ndr's and failure notices Posted: 31 Oct 2006 07:24 PM PST By the way, this KB helped me out a bunch for cleaning out the muck in my queues. Until this was done my server was way out of whack. http://support.microsoft.com/default.aspx/kb/909005 "John Oliver, Jr. [MVP]" wrote: |
OWA Access for 2 Servers - Same Org - Different MX? Posted: 31 Oct 2006 01:05 PM PST Hi Ed, I really appreciate your time. Ultimately, I will have migrated all mailboxes to the new Enterprise 2003 Server. The users I have migrated do not use OWA which leaves about 60 users / mailboxes that need it. the exisiting environment has an MX pointing to a 3rd party Anti Spam solution (hosted) - the new Server has an Appliance in-house I'll manage. I tought if I could get another URL / OWA address to the new server, the migration would be less painful for the users. Again, thanks for your insight! "Ed Crowley [MVP]" wrote: |
Posted: 31 Oct 2006 10:48 AM PST Hi You can use "Active Directory Users and Computers" console, right click on your domain and click Find. On the section Find choose Custom Search, and on the Advanced tab paste this LDAP query: (&(objectcategory=person)(objectclass=user)(userAc countControl:1.2.840.113556.1.4.803:=2)(msExchHome ServerName=*)) In the Search results select all users and in the right click choose Exchange task and Delete mailbox. I hope this will help Nebojsa Seslija "Franky M." <microsoft.com> wrote in message news:com... |
How to tell exchange he is no longer responsible for a domain Posted: 31 Oct 2006 10:40 AM PST That did the trick. Thanks. "Leif Pedersen [MVP]" wrote: |
Auto message to new or Moved users? Posted: 31 Oct 2006 06:54 AM PST In brief, the best way to do it would be to have a provisioning script you always use to create accounts and add code to send that message to the process. -- Ed Crowley MVP - Exchange "Protecting the world from PSTs and brick backups!" "Transam388" <microsoft.com> wrote in message news:com... |
Posted: 30 Oct 2006 07:41 PM PST Very cool. Good luck! <com> wrote in message news:googlegroups.com... |
Modifying Contact Views on the Exchange Server Posted: 30 Oct 2006 11:07 AM PST Ed, Thank you very much. After some more research looking for the CIW on the MS website I discovered that the CIW is for installations but another tool called Custom Maintenance Wizard should allow me to change settings after the product is already installed and I'm downloading and looking into it right now. Thanks again, this seems to be just what I was looking for!! Jon |
forwarding external email addresses to Microsoft exchange email address Posted: 30 Oct 2006 05:50 AM PST Ian, If com is your catch-all mailbox it means the email address that the sending server is forwarding to doesn't exist. Have them double-check the address they're forwarding to, or have them forward the NDR to you to troubleshoot further. -- Bharat Suneja MVP - Exchange www.zenprise.com NEW blog location: www.exchangepedia.com/blog ---------------------------------------------- "Ian Burton" <com> wrote in message news:%23LuQiVn$phx.gbl... |
Default Global Address List is missing from All Global Address Lis Posted: 30 Oct 2006 03:10 AM PST Hi Leif, I have found the Default Global Address List in adsiedit under CN=All Global Address Lists, but unfortunately it won't open up the properties of the Default Global Address List (nothing happens when you attempt to do so). It also has nothing under the "Class" heading. Do you have any suggestions? Regards Paul "Leif Pedersen [MVP]" wrote: |
Posted: 29 Oct 2006 04:05 PM PST Thx for the info, but I figured it out. There are a few things that you have to do with the CA once it's created that did not appear anywhere in all the howto's that I checked. For anyone's future reference, you end up going to the /certserv site 3 times by the time that it's done. "mitch Roberson" wrote: |
Urgent !! please help Exchnage 2003 , AD and DNS problem Posted: 29 Oct 2006 04:00 PM PST Hello Mitch I checked the Directory Access tab the Automaticlly discover is already enabled, all the GC are listed there. on our Exchnage server I have checked our Exchnage server listed 3 DNS Server. it starting to make me think it may be to do with ESX vmware Server. I don't like the idea of having a FSMO DC and a exchnage in one server using vmware. Thank you for all your help. "mitch Roberson" wrote: |
OWA-The Local Security Authority cannot be contacted Posted: 28 Oct 2006 06:40 AM PDT From: =?Utf-8?B?TGVl?= <nospam> Subject: OWA-The Local Security Authority cannot be contacted Date: Sat, 28 Oct 2006 06:40:02 -0700 Newsgroups: microsoft.public.exchange.misc Hello. The issue I am having is with OWA. When a user logs on sometimes they get in w/o a prob and sometimes they get the message "The Local Security Authority cannot be contacted" Hi, Thank you for posting here. From your post, I understand users get "The Local Security Authority cannot be contacted" error message when accessing OWA. First, in order to get a clear picture on this issue, please let me know the following questions: 1. Does this issue occur on all users? 2. Does this issue occur in LAN? If you access the problematic account from Exchange Server, do you get the same result? 3. Has this ever worked before? 4. When did this problem begin? 5. Do you use http or https to access OWA? To isolate this issue, let's try the following steps to narrow down this issue: 1. Please create a new account, can you access OWA from internal network? 2. If you enable SSL on Exchange Server to access OWA, please temporary offload SSL and try it again. 3. If you access OWA from a non-domain workstation, can you login? 4. If this issue persists, I would like to check Log on locally rights and compared SMTP address in Recipient Policy and Exchange virtual directory. Check Log on Locally: ================ 1. Open GPEDIT.msc on the Exchange server. 2. Browse to Computer Configuration->Windows Settings->Security settings->Local Policies->User right assignment. 3. In the "Allow log on locally", make sure that these users or their groups are included in the list. 4. After that, you may run "gpupdate /force" on the server and test this issue. If this issue persists, restart the Exchange server to test this issue again. Compare SMTP addresses: ==================== - Recipient Policy for SMTP address: ----------------------------------- 1). Open Exchange system manager. 2). Locate Recipient Policies. 3). Right-click Default Recipient Policy and then click Properties. 4). Click the E-mail Addresses tab. 5). Check the SMTP line (which has been set as primary) and note down the Address. - Exchange virtual directory: ---------------------------- 1). Open Exchange system manager. 2). Locate Exchange virtual server in HTTP protocol. 3). Right-click Exchange virtual directory under Exchange virtual server and then click Properties. 4). On the General tab, check if the Exchange path is same with the SMTP address you just noted down. Please let me know the result at your earliest convenience, if anything unclear please feel free to let me know. Have a nice day! Best Regards, Chace Zhang (MSFT) Microsoft CSS Online Newsgroup Support Get Secure! - www.microsoft.com/security ================================================== === This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the newsgroup here: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e-mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please "Reply to Group" so that others may learn and benefit from your issue. Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues are resolved in a timely manner. For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional support phone numbers. Any input or comments in this thread are highly appreciated. ================================================== === This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- | Thread-Topic: OWA-The Local Security Authority cannot be contacted | thread-index: Acb6lpGb/BmoliWORYGBEzlg4rAgtQ== | X-WBNR-Posting-Host: 67.80.27.150 | From: =?Utf-8?B?TGVl?= <nospam> | Subject: OWA-The Local Security Authority cannot be contacted | Date: Sat, 28 Oct 2006 06:40:02 -0700 | Lines: 10 | Message-ID: <com> | MIME-Version: 1.0 | Content-Type: text/plain; | charset="Utf-8" | Content-Transfer-Encoding: 7bit | X-Newsreader: Microsoft CDO for Windows 2000 | Content-Class: urn:content-classes:message | Importance: normal | Priority: normal | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830 | Newsgroups: microsoft.public.exchange.misc | Path: TK2MSFTNGXA01.phx.gbl | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.exchange.misc:130979 | NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250 | X-Tomcat-NG: microsoft.public.exchange.misc | | | Hello. | The issue I am having is with OWA. When a user logs on sometimes they get in | w/o a prob and sometimes they get the message "The Local Security Authority | cannot be contacted" | | | | -- | Lee Morgenstein | |
You are subscribed to email updates from TextNData Forums - Microsoft Exchange To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google Inc., 20 West Kinzie, Chicago IL USA 60610 |