Is each subnet setup at a site in AD?
Joel Stidley
Senior Systems Engineer
divine inc.
[EMAIL PROTECTED]
-Original Message-
From: Richard Dann [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 13, 2001 4:20 PM
To: Exchange Discussions
Subject: Problems installing E2K SP1
Folks,
I can't
If you have ever done a trust and tried to used Exchange 2000, in short
it doesn't work and is unsupported. I should actually clarify that, it
does sort of work; however permissions are a pain. You have to assign
rights on the exchange domain on each mailbox for each user. You also
need to do s
That all being said. If you plan on ignoring logic you can use ISA
server to publish your Exchange server. It will filter RPC data to
reduce the risks involved. There is a few docs on doing this on MS site
in the Hosting Series. There are limitations, such as not working well,
but it does work
Do you have a proxy server or firewall between you and the OWA box? If
so what?
Joel
-Original Message-
From: Steve Iadarola [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 16, 2002 4:44 PM
To: Exchange Discussions
Subject: RE: OWA Help
Ping via Server Name, IP and FQDN all come b
The message is a "feature" of Outlook XP. Previous versions of Outlook
would just sit and wait for this data to be retrieved. XP notifies the
users of these communications with the server. Typically though this
message means there was an issue talking to the server. If this is
frequent you wil
Technically this may seem to work. However having done this myself in a
large environment, it is not a good idea. There are issues that _can_
be over come but are not worth the time, some issues though may always
be there. Since your AD account is essentially your mailbox, you need
to make sure
Can the clients resolve the name of the server when they are having the
problem? Are the WINS settings correct on the new servers?
Joel
-Original Message-
From: Soysal, Serdar [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 25, 2002 1:50 PM
To: Exchange Discussions
Subject: RE: Win
Wingra will do all that and a little more. You will want to call them
to get all the gory details. The site isn't as detailed as it should
be.
Joel
-Original Message-
From: Williams Scott CTR [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 10:04 AM
To: Exchange Discussion
The other issues are what are you gaining by clustering at all? The
only things that you are covering with clustering are:
1) Hardware failure on the servers (not on the shared disk)
2) Shorter software upgrade or hotfix time (how often does this happen)
By adding clustering into the mix you
I am pretty sure this was stated already, try downloading the Full
offline address list as well as change the RPC Binding order as follows:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider]
"Rpc_Binding_Order"="ncacn_ip_tcp"
Couple other questions, how many GCs do you have? Are
You also want to consider the more applications/processes you run the
more likely one of them will stop working. This translates into
downtime. If for some reason your GC stops replicating or answering
requests and the normal recovery steps don't work, you may have to
reboot. It is the same for
Are you doing any SMTP proxying or filtering on your firewall or are you
using a SMTP gateway product? It sounds like the server sending you the
email is trying your first MX and then trying the second MX record and
it then goes through.
If this is a case (you can verify with the message headers
Here is a nice article about Microsoft's messaging plans from InfoWorld.
http://www.infoworld.com/articles/hn/xml/02/07/14/020714hntitanium.xml
-Original Message-
From: Hilary Cotter [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 11, 2002 7:48 AM
To: Exchange Discussions
Subject: Kodi
This may be flawed reasoning, but the version of MDAC that ships with
and is installed with Windows 2000 is 2.5. Exchange 5.5 Sp4 runs fine
on Windows 2000. I would assume that it would work just fine. However
all precautions should be taken.
-Original Message-
From: Schwartz, Jim [mai
-
> From: Stidley, Joel [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, March 14, 2002 1:47 PM
> To: Exchange Discussions
> Subject: RE: MDAC on Exchange
>
> This may be flawed reasoning, but the version of MDAC that ships with
> and is installed with Windows 2000 is 2.5. Ex
clarify something. The MDAX they would
> > like to install is 2.1.2 or higher. They've also stated that
> > if I were to use the 2.5 version of MDAC I would also need to
> > install Jet40SP3_Comp.exe.
> >
> > Or I could just tell them I need to migrate all the s
How is your network setup? Is your Exchange server behind a firewall or
VPN? Do you have a GC close to the clients? Have you done a netmon
trace to see at what point the problem is occurring?
Joel
-Original Message-
From: John Q Jr. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 19,
You may also want to try this too:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider]
"Rpc_Binding_Order"="ncacn_ip_tcp"
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 04, 2002 2:00 PM
To: Exchange Discussions
Subject: RE: Outl
18 matches
Mail list logo