Deprecated: Function set_magic_quotes_runtime() is deprecated in /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php on line 1505 Call Stack: 0.0001 326576 1. {main}() /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:0 0.0003 327428 2. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:25 0.0004 328716 3. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php:20 0.0011 403020 4. vB_Registry->vB_Registry() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php:43 0.0012 403676 5. vB_Input_Cleaner->vB_Input_Cleaner() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php:2337
Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /archive/global.php on line 26

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3113

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265
Can send and receive, but not from our parent company [Archive] - MCSE
PDA

View Full Version : Can send and receive, but not from our parent company

Lloyd
03-25-04, 11:24 AM
something
I recently installed several Exchange 2000 Servers into
our Exchange 5.5 organization. Things were working
properly with the 5.5 servers online. I removed the 5.5
servers from the organization, including the IMC that had
special routing set up for our parent company.

Now, we can still send email to our parent company, but
are unable to receive. Email to the rest of the world
works fine.

The 5.5 server that used to handle email to and from our
parent company had a different IP address than the 2000
server has.

The only error that I'm getting that seems to have
anything to do with our parent domain is:
Source: DCOM
Category: None
Event ID: 10009
Description: DCOM was unable to communicate with the
computer mailinbound.(parentcompany).com using any of the
configured protocols.

My question is, is this an issue on our end, or do they
need to point their servers to our new IP address, and if
it's on our end, any ideas on what I can do to clear up
this problem? Any way I can get the information that used
to be in our old IMC settings? Thank you for your reply.

Lloyd Thielsen


My questions are:
Fitz Crittle [MSFT]
03-25-04, 12:22 PM
something
A user from the Parent company should get a Non Delivery report (NDR) that
should tell you why they aren't able to send to you. If other domains can
send to your Exchange Server, then I don't think the issues is with
Exchange. It's probably a configuration issue at the Parent site.

Thanks,
Fitz Crittle

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup


"Lloyd" <lloyd.thielsen@chargecraft.com> wrote in message
news:134b801c41285$9d474320$a301280a@phx.gbl...
> I recently installed several Exchange 2000 Servers into
> our Exchange 5.5 organization. Things were working
> properly with the 5.5 servers online. I removed the 5.5
> servers from the organization, including the IMC that had
> special routing set up for our parent company.
>
> Now, we can still send email to our parent company, but
> are unable to receive. Email to the rest of the world
> works fine.
>
> The 5.5 server that used to handle email to and from our
> parent company had a different IP address than the 2000
> server has.
>
> The only error that I'm getting that seems to have
> anything to do with our parent domain is:
> Source: DCOM
> Category: None
> Event ID: 10009
> Description: DCOM was unable to communicate with the
> computer mailinbound.(parentcompany).com using any of the
> configured protocols.
>
> My question is, is this an issue on our end, or do they
> need to point their servers to our new IP address, and if
> it's on our end, any ideas on what I can do to clear up
> this problem? Any way I can get the information that used
> to be in our old IMC settings? Thank you for your reply.
>
> Lloyd Thielsen
>
>
> My questions are:
03-25-04, 01:23 PM
something
Thus far, they haven't got any NDRs. The error message
doesn't seem to be related?


>-----Original Message-----
>A user from the Parent company should get a Non Delivery
report (NDR) that
>should tell you why they aren't able to send to you. If
other domains can
>send to your Exchange Server, then I don't think the
issues is with
>Exchange. It's probably a configuration issue at the
Parent site.
>
>Thanks,
>Fitz Crittle
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>Please do not send email to this address, post a reply to
this newsgroup
>
>
>"Lloyd" <lloyd.thielsen@chargecraft.com> wrote in message
>news:134b801c41285$9d474320$a301280a@phx.gbl...
had[color=blue]
the[color=blue]
if[color=blue]
used[color=blue]
reply.[color=blue]
>
>
>.
>
Lloyd
03-25-04, 01:23 PM
something
Thanks for your answer, but there haven't been any NDRs so
far. I think I know where I could make sure that our
settings are right - on the Exchange 5.5 server, under the
IMS properties, on the connections tab, in the E-mail
Domain button, there were some IP addresses that I could
put under Access settings on the SMTP Virutal Server
Properties on the Exchange 2000 server.

Unfortunately, those settings were blown away when I
deleted the IMS on the 5.5 machine. Any way I could
restore the 5.5 computer to get settings without
interfering with the current Exchange setup (Mailboxes
have been moved, etc.)?

Thanks,
Lloyd

>-----Original Message-----
>A user from the Parent company should get a Non Delivery
report (NDR) that
>should tell you why they aren't able to send to you. If
other domains can
>send to your Exchange Server, then I don't think the
issues is with
>Exchange. It's probably a configuration issue at the
Parent site.
>
>Thanks,
>Fitz Crittle
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>Please do not send email to this address, post a reply to
this newsgroup
>
>
>"Lloyd" <lloyd.thielsen@chargecraft.com> wrote in message
>news:134b801c41285$9d474320$a301280a@phx.gbl...
had[color=blue]
the[color=blue]
if[color=blue]
used[color=blue]
reply.[color=blue]
>
>
>.
>
Jenny Frye [MSFT]
03-25-04, 06:21 PM
something
Lloyd,

If I understand correctly, the problem is your parent company cannot send
mail TO your new E2k server. The IMS\Connections|Specify by Email Domain
settings would have controlled mail OUT of your IMS so I don't believe
restoring the old 5.5 server to retrieve the settings is going to solve the
problem if this is an inbound problem.

How is your parent company trying to send mail to your server? Are they
sending SMTP mail via internet or are they using X.400? If it is SMTP, are
they configured to use DNS to lookup your MX/A records or do they have your
server configured as a smarthost? If they have your server setup as a
smarthost then they will need to add the IP address of your E2k server to
the settings.

The DCOM error possibly is related but it isn't a good clue at this point.
You may want to go to the properties of the Exchange server object in System
Manager and go to the Diagnostics Logging page. Set the
MSExchangeTransport\SMTP Protocol logging to Maximum. This may log events
in the application log that will tell you more about the problem - assuming
they are trying to communicate using SMTP.

--
Jenny Frye
Microsoft PSS

This posting is provided 'AS IS' with no warranties and confers no rights.
Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
vBulletin v3.6.2, Copyright ©2000-2010, Jelsoft Enterprises Ltd.