Pages

Search

Exchange SBS 2003, server IP address changed, can't connect - Microsoft Exchange

Exchange SBS 2003, server IP address changed, can't connect - Microsoft Exchange

Exchange SBS 2003, server IP address changed, can't connect

Posted: 10 Sep 2006 03:28 PM PDT

Yes they did.

Basically they have broadband coming in and they have a LinkSys router
giving out IP addresses and have setup the server with one of the IP
addresses as static right now and to give them access to the internet, i've
had to re-enter all DNS addresses for the server.

"Ed Crowley [MVP]" wrote:
 

Running 2 compaines

Posted: 10 Sep 2006 11:59 AM PDT

If all you're worried about is running two separate address spaces, it's
about as simple as defining two recipient policies, and using some attribute
in Active Directory, such as the company name, to determine which address is
applied to each recipient.

If your concers are more extensive, what you're discussing can be a very
extensive topic.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"glenn" <com> wrote in message
news:%phx.gbl... 

System Folder

Posted: 09 Sep 2006 05:54 AM PDT

ESEUTIL /R might fix your problems, but you may lose a significant amount of
content. I think I would create a public store on another server, replicate
all folders to it, then delete the first public store. You could follow up
with the reverse if you want to put everything back, but I wouldn't be too
quick to do that until I thought I had a good handle on what caused the
corruption.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"S" <s@s.com> wrote in message news:phx.gbl... 

exchange 2003 rename mailbox

Posted: 08 Sep 2006 08:45 AM PDT

You just need to change their display name in Active Directory to change how
their name appears on incoming/outgoing email. You can also modify their
smtp address(es) on the email addresses tab if necessary.

Go easy on the cross posting. :)

--
Thanks,
Brian Desmond
Windows Server MVP - Directory Services

www.briandesmond.com


"jason sigurdur" <org> wrote in message
news:phx.gbl... 

Emails vanished!! Please help

Posted: 08 Sep 2006 04:38 AM PDT

On Mon, 11 Sep 2006 15:29:23 +0100, "Jarryd" <j@n.c> wrote:
 

Nope, no restarts of anything.
 

Yup, always back it up before you restore any previous backup.
 

Help, I deleted some log files

Posted: 07 Sep 2006 08:02 PM PDT

Glad to hear that you're cured.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Clayton" <com> wrote in message
news:MN2Ng.642715$news.easynews.com... 

public folders won't replicate to new server

Posted: 07 Sep 2006 07:42 PM PDT

I would start by creating a test mailbox on it and testing mail flow.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"seth" <net> wrote in message
news:%23YZRR$phx.gbl... 

Out Of Office not working

Posted: 07 Sep 2006 03:55 PM PDT

Hi,

Thank you for posting here.

According to your description, I understand this issue is: out of office
assistant is not working internal, also you enable OOF in OWA, the same
result. If I'm off base, please feel free to let me know.

First of all, I would like to let you know that that when Out of Office is
enabled, only one reply is sent to each sender in each session, even if you
receive multiple messages from that person. This is reset when you toggle
the Out of Office in the client. In other words, Exchange clears the
internal "sent to" list when you disable the Out of Office that is
currently enabled.

Therefore, I suggest that you enable OOF rules on that problematic user,
test the OOF rules, then disable it, restart Outlook and enable OOF rules
to test again. Will it work now? Also, you can test the problematic user's
OOF rules by sending emails from different users.

For more information about this, please refer to the following Microsoft KB
article:

157961 XCLN: Out of Office Reply Sent Only Once
http://support.microsoft.com/?id=157961
Note: This article also applies to Exchange Server 2003.

In order to get a more concrete idea as to what the exact problem is and
how to resolve it efficiently, I'd like to know the following question:

What the edition of your Exchange Server? Standard or Enterprise?

Did Out of Office Assistant even work before?

Please check whether there is anything antivirus software is scanning your
Exchange server or whether there is any Firewall enabled before your
Exchange server. If so, please remove it completely and test the issue
again.

Note: If there is any anti-virus email installed on client, please also
remove them temporarily.

Reference:

823166 Overview of Exchange Server 2003 and Antivirus Software
http://support.microsoft.com/?id=823166

Based on my research, I suggest you perform the following steps to check
whether the problem still occurs:

Step #1:
---------------------
1. Quit Outlook, in Command Prompt, type "outlook /cleanfreebusy"
2. Disable OOF and then restart Outlook, re-enable OOF.
3. Test the issue again.


Step #2:
----------------
If you are using Enterprise version Exchange server, I suggest you create a
new mailbox store and create a new mail-enabled user, host this new user's
mailbox on the new store. Test the issue again.



Step 3:
-------------
If this issue still occurs, I would like to suggest you stopping the Simple
Mail Transfer Protocol (SMTP) and Microsoft Exchange Routing Engine
services, and then restart them. After that, let's turn off OOF assistance
and turn it on again to test this issue again.

Step 4:
-------------
Another possible cause to this issue is the total program user count equals
the total server license count. For example, if you have five licenses for
Exchange server and you have used all five licenses, Exchange does not send
OOF messages. The following KB article which also applies to Exchange
Server 2003 is addressed this issue. If this is the case, please refer to
the workaround in the following KB to see if the issue can disappear.

811912 XADM: Out-of-Office Message Is Not Sent When All Exchange 2000 Client
http://support.microsoft.com/?id=811912


If the problem still occurs, to get the root cause of the issue, we need to
capture some troubleshooting logs for further research:

------------------
We need to message tracking to monitor whether the OOF has been sent to the
Exchange server. The detailed information about Message Tracking is
documented in the following KB articles:

XADM: How to Enable Message Tracking in Exchange 2000 Server
http://support.microsoft.com/kb/246856
Note: This article is also applied to Exchange 2003.

XADM: Using the Message Tracking Center to Track a Message
http://support.microsoft.com/kb/262162

Note: Please let me know the following information as well:

a. OOF sender's email address
b. The recipient email
c. When the email has been sent.

Please send this mail to com

Hope this helps, if you have any other concerns on this issue, 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 Exchange 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: Out Of Office not working
| thread-index: AcbS095K2IsE73HFQiaGCf9zIbd5pA==
| X-WBNR-Posting-Host: 216.39.152.73
| From: =?Utf-8?B?Sm9lIFMu?= <postalias>
| References: <com>
<phx.gbl>
| Subject: Re: Out Of Office not working
| Date: Thu, 7 Sep 2006 16:18:03 -0700
| Lines: 28
| 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:130117
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.exchange.misc
|
| Internal --
|
| "Ed Crowley [MVP]" wrote:
|
| > It's not working for messages from internal senders or just external?
If
| > it's external only, you need to enable Out of Office to the Internet.
| > --
| > Ed Crowley
| > MVP - Exchange
| > "Protecting the world from PSTs and brick backups!"
| >
| > "Joe S." <postalias> wrote in message
| > news:com...
| > >I have one user out of around 80 that the Out Of Office feature does
not
| > >work
| > > for.
| > > Outlook 2003, cache mode in Exchange 2003 sp2,Win 2003 SP1 domain
| > > enviroment. You can change the OoO text and turn it on. It's says
that
| > > it's
| > > on, but no OoO message is ever returned to anyone sending the account
an
| > > e-mail. No error messages. I have even tried using OWA to turn the
OoO on
| > > and
| > > it still doesn't work. No error messages on the Exch. server either.
Any
| > > ideas.
| > >
| >
| >
| >
|

IMAP Errors

Posted: 07 Sep 2006 09:54 AM PDT

I would look at my firewall, NAT or any proxy devices.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"CK" <microsoft.com> wrote in message
news:com... 

Third Party Utility - BCC Shows on Incoming Emails

Posted: 07 Sep 2006 09:46 AM PDT

Eleanor:
I have never heard of such a utility. I don't think the BCC information
would even be in the message when it was transferred to a server from
outside. That would defeat the whole purpose of the BCC if that information
were included in the message. I am pretty sure that doing this would be
impossible.
--
Jim McBee
Blog - http://mostlyexchange.blogspot.com
Directory Update - http://www.directory-update.com

"Eleanor, MCSE/MCT" <microsoft.com> wrote in
message news:com... 

Strange Exchange queue

Posted: 06 Sep 2006 09:34 PM PDT

He said "didnt" which I took to mean he doesn't have it installed.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Jim McBee (MVP - Exchange)" <spambegone.net> wrote in message
news:phx.gbl... 

Public Folders Error Message

Posted: 06 Sep 2006 11:13 AM PDT

Thanks this worked.
--
SeanR


"Alan Williams [MSFT]" wrote:
 

Outlook 2003- Corrupt Rules

Posted: 06 Sep 2006 03:46 AM PDT

I believe that you can use PFDAVADMIN to remove the hidden message that
controls the rules. If I'm wrong, someone more experienced with the tool
will correct me, I'm sure.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"nordberg" <hotmail.com> wrote in message
news:45012316$0$17539$astraweb.com... 

Should I restart Exchange services everynight ?

Posted: 06 Sep 2006 02:06 AM PDT

On Wed, 6 Sep 2006 05:03:03 -0700, Petri
<microsoft.com> wrote:
 
I'll lay odds that there are.