Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Exchange 2003 standard to Exchange 2003 enterprise

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2003] >> Migration >> Exchange 2003 standard to Exchange 2003 enterprise Page: [1] 2 3   next >   >>
Login
Message << Older Topic   Newer Topic >>
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 12:47:04 AM   
Cali

 

Posts: 30
Joined: 17.Jul.2006
Status: offline 		ok.. so I am not the world best Exchange admin... but I thought I would help a friend in need out and do a "simple migration"...

setup

old_server
Windows 2000 with Exchange 2003 standard

new_server (new hardware)
Windows 2003 with Exchange 2003 enterprise


process

installed Windows 2003 and all updates/patches/fixes/tweaks
installed Exchange 2003 (added server to existing installation) sp2 patched

situation

new_server can send email to external (bob@yahoo.com)
new_server can NOT send email internal to old_server or to new_server     user@company.com
new_server can NOT receive email from old_server or new_server             user@company.com
new_server can NOT receive email from external (spam related perhaps)

on old_server, SurfControl spam filter is installed (not familar at all with this product)
[SurfControl email filtering for SMTP ver 5.01]

question/thoughts

While SufControl may be blocking the external email (since old_server is the master server), why cant the two exchange servers send mail between themselves?

I read the forums today for about 2 or 3 hours.. trying to use search and such.. with no luck.
I know, another 1 post newbie.. but hey I promise I am a good guy, not a complete newbie.. just Exchange 2003 lacking

_____________________________

<insert something funny>
Post #: 1
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 2:34:35 PM   
pjhutch

 

Posts: 3055
Joined: 21.Jul.2001
From: W Yorks, England
Status: offline 		I would check SMTP setting esp things like IP restrictions so that smtp can only be sent/received from specific IP address as exchange would be able to mail between exchange servers in the same organisation and routing group.

(in reply to Cali)
Post #: 2
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 3:09:31 PM   
Cali

 

Posts: 30
Joined: 17.Jul.2006
Status: offline
quote:

ORIGINAL: pjhutch

I would check SMTP setting esp things like IP restrictions so that smtp can only be sent/received from specific IP address as exchange would be able to mail between exchange servers in the same organisation and routing group.



Interesting idea.. though the outbound to external does work.

Would these settings you mention be more of a firewall/router/exchange setting?

(in reply to pjhutch)
Post #: 3
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 3:30:19 PM   
pjhutch

 

Posts: 3055
Joined: 21.Jul.2001
From: W Yorks, England
Status: offline 		Depends if the servers are in the same subnet or one is internal and the other is in a DMZ otherwise they should talk together. Anyway, I was mainly thinking of the settings in Exchange Manager.


(in reply to Cali)
Post #: 4
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 3:37:02 PM   
Cali

 

Posts: 30
Joined: 17.Jul.2006
Status: offline
quote:

ORIGINAL: pjhutch
Depends if the servers are in the same subnet or one is internal and the other is in a DMZ otherwise they should talk together. Anyway, I was mainly thinking of the settings in Exchange Manager.


good questions/ideas about network placement - both are in the same subnet; neither in a DMZ.  In the Exchange mangager, which area(s)
should I compare settings to for new_server and old_server?

--> First Administrative Group --> Servers --> new_server --> Protocols? server properties?

thanks for the ideas thus far.

(in reply to pjhutch)
Post #: 5
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 3:41:25 PM   
pjhutch

 

Posts: 3055
Joined: 21.Jul.2001
From: W Yorks, England
Status: offline 		Try SMTP, Default SMTP Virtual Server Properties. Access, Connection (All except the list below) and Relay (Only the list below, Allow all computers which successfully authenticate...)

(in reply to Cali)
Post #: 6
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 4:04:43 PM   
Cali

 

Posts: 30
Joined: 17.Jul.2006
Status: offline 		all of those settings are as you suggested.

I froze all message ques and here is the order of operation
(I had a mix of new_server to new_server emails, new_server to old_server emails, and new_server to external address)

messages pending submission
messages awaiting directory lookup
messages waiting to be routed

old_server.companyname.com SMTP   --> gone no delivery
local delivery   SMTP
  messages awaiting directory lookup
  message waiting to be routed
  local delivery  ---> gone no delivery

not sure how helpful this would or would not be.  any logs I perhaps I can post for better troubleshooting?

(in reply to pjhutch)
Post #: 7
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 4:11:31 PM   
pjhutch

 

Posts: 3055
Joined: 21.Jul.2001
From: W Yorks, England
Status: offline 		Have you tried the SMTPDiag tool?

See http://www.microsoft.com/downloads/details.aspx?FamilyID=bc1881c7-925d-4a29-bd42-71e8563c80a9&DisplayLang=en

(in reply to Cali)
Post #: 8
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 4:55:13 PM   
Cali

 

Posts: 30
Joined: 17.Jul.2006
Status: offline 		here is the output from that test:


Searching for Exchange external DNS settings.
Computer name is new_server.
VSI 1 has the following external DNS servers:
There are no external DNS servers configured.

Checking SOA for company.com.
Checking external DNS servers.
Checking internal DNS servers.

Checking TCP/UDP SOA serial number using DNS server [*.*.*.70].
TCP test succeeded.
UDP test succeeded.
Serial number: 17499

Checking TCP/UDP SOA serial number using DNS server [*.*.*.76].
TCP test succeeded.
UDP test succeeded.
Serial number: 17499
SOA serial number match: Passed.

Checking local domain records.
Starting TCP and UDP DNS queries for the local domain. This test will try to
validate that DNS is set up correctly for inbound mail. This test can fail for
3 reasons.
  1) Local domain is not set up in DNS. Inbound mail cannot be routed to
local mailboxes.
  2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail,
but will affect outbound mail.
  3) Internal DNS is unaware of external DNS settings. This is a valid
configuration for certain topologies.
Checking MX records using TCP: company.com.
A:     company.com [*.*.*.70]
A:     company.com [*.*.*.76]
A:     company.com [*.*.*.0]
Checking MX records using UDP: company.com.
A:     company.com [*.*.*.70]
A:     company.com [*.*.*.76]
A:     company.com [*.*.*.0]
Both TCP and UDP queries succeeded. Local DNS test passed.

Checking remote domain records.
Starting TCP and UDP DNS queries for the remote domain. This test will try to
validate that DNS is set up correctly for outbound mail. This test can fail for
3 reasons.
  1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows
2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP
queries first, then fall back to TCP queries.
  2) Internal DNS does not know how to query external domains. You must
either use an external DNS server or configure DNS server to query external
domains.
  3) Remote domain does not exist. Failure is expected.
Checking MX records using TCP: company.com.
A:     company.com [*.*.*.70]
A:     company.com [*.*.*.76]
A:     company.com [*.*.*.0]
Checking MX records using UDP: company.com.
Both TCP and UDP queries succeeded. Remote DNS test passed.

Checking MX servers listed for testuser@company.com.
Connecting to company.com [*.*.*.0] on port 25.
Connecting to the server failed. Error: 10060
Failed to submit mail to company.com.
Connecting to company.com [*.*.*.76] on port 25.
Connecting to the server failed. Error: 10061
Failed to submit mail to company.com.
Connecting to company.com [*.*.*.70] on port 25.
Received:
220 domain_controller.company.com Microsoft ESMTP MAIL Service, Version: 5.0.2195.6713 ready at  Tue, 18 Jul 2006 09:20:47 -0500


Sent:
ehlo company.com

Received:
250-domain_controller.company.com Hello [*.*.*.48]
250-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-TURN
250-ATRN
250-SIZE 2097152
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250 OK


Sent:
mail from: <test1@company.com>

Received:
250 2.1.0 test1@company.com....Sender OK

Sent:
rcpt to: <testuser@company.com>

Received:
550 5.7.1 Unable to relay for testuser@company.com

Error: Expected "250". Server rejected the recipient address.
Failed to submit mail to company.com.

< Message edited by Cali -- 18.Jul.2006 4:56:37 PM >

(in reply to pjhutch)
Post #: 9
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 5:04:10 PM   
pjhutch

 

Posts: 3055
Joined: 21.Jul.2001
From: W Yorks, England
Status: offline 		How is your DNS server configured? Is it a Windows server? Do you use Dynamic registrations? Do you have
Host and MX records for your Exchange servers and DCs and SRV records for your domain? Have you run DCDIAG?

(in reply to Cali)
Post #: 10
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 5:16:16 PM   
Cali

 

Posts: 30
Joined: 17.Jul.2006
Status: offline 		good questions about DNS

it is a Windows 2000 based DNS... and is using dynamic registrations

I thought using the old_server as a master bridgehead that no additional MX records locally would be required....
old_server is still working flawlessly during the entire setup.

here is the DCDIAG
Domain Controller Diagnosis

Performing initial setup:
  Done gathering initial info.

Doing initial required tests
 
  Testing server: Default-First-Site-Name\domain_controller
     Starting test: Connectivity
        ......................... domain_controller passed test Connectivity

Doing primary tests
 
  Testing server: Default-First-Site-Name\domain_controller
     Starting test: Replications
        ......................... domain_controller passed test Replications
     Starting test: NCSecDesc
        ......................... domain_controller passed test NCSecDesc
     Starting test: NetLogons
        ......................... domain_controller passed test NetLogons
     Starting test: Advertising
        ......................... domain_controller passed test Advertising
     Starting test: KnowsOfRoleHolders
        ......................... domain_controller passed test KnowsOfRoleHolders
     Starting test: RidManager
        ......................... domain_controller passed test RidManager
     Starting test: MachineAccount
        ......................... domain_controller passed test MachineAccount
     Starting test: Services
        ......................... domain_controller passed test Services
     Starting test: ObjectsReplicated
        ......................... domain_controller passed test ObjectsReplicated
     Starting test: frssysvol
        ......................... domain_controller passed test frssysvol
     Starting test: frsevent
        ......................... domain_controller passed test frsevent
     Starting test: kccevent
        ......................... domain_controller passed test kccevent
     Starting test: systemlog
        An Error Event occured.  EventID: 0xC0011093
           Time Generated: 07/18/2006   09:35:57
           (Event String could not be retrieved)
        ......................... domain_controller failed test systemlog
     Starting test: VerifyReferences
        ......................... domain_controller passed test VerifyReferences
 
  Running partition tests on : Schema
     Starting test: CrossRefValidation
        ......................... Schema passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... Schema passed test CheckSDRefDom
 
  Running partition tests on : Configuration
     Starting test: CrossRefValidation
        ......................... Configuration passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... Configuration passed test CheckSDRefDom
 
  Running partition tests on : company
     Starting test: CrossRefValidation
        ......................... company passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... company passed test CheckSDRefDom
 
  Running enterprise tests on : company.com
     Starting test: Intersite
        ......................... company.com passed test Intersite
     Starting test: FsmoCheck
        ......................... company.com passed test FsmoCheck

(in reply to pjhutch)
Post #: 11
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 5:25:33 PM   
pjhutch

 

Posts: 3055
Joined: 21.Jul.2001
From: W Yorks, England
Status: offline 		Looking at smtp log, it says:

Connecting to company.com [*.*.*.70] on port 25.
Received:
220 domain_controller.company.com Microsoft ESMTP MAIL Service, Version: 5.0.2195.6713 ready at  Tue, 18 Jul 2006 09:20:47 -0500

Is your DC an Exchange server as well? Maybe DNS MX is picking up the wrong server ...

(in reply to Cali)
Post #: 12
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 5:43:16 PM   
Cali

 

Posts: 30
Joined: 17.Jul.2006
Status: offline 		good darn observation

no the DC is not an exchange server
however that was the setup prior to beginning this madness.

so..

I looked in the DNS

the only entry I see is for "mail" pointing to old_server's IP address

no A record or MX record in local DNS..

again I am supposed to be helping out and this in not my normal environment -
so hopefully I am not coming across as totally clueless.

thanks for the information thus far.. i just cant help thinking it is something just SO SO simple.

(in reply to pjhutch)
Post #: 13
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 5:45:07 PM   
de.blackman

 

Posts: 1482
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline 		lets go back to basics then. from the new server,  can you telnet to the old server on port 25 and spoof a message to it? how about the other way around. When i say spoof, i mean create an email from the telnet command prompt.



_____________________________

De BlackMan
List Moderator
"Did you backup your Information Store Today?!"

(in reply to Cali)
Post #: 14
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 5:45:38 PM   
pjhutch

 

Posts: 3055
Joined: 21.Jul.2001
From: W Yorks, England
Status: offline 		I suggest creating an MX record and point it to your Exchange 2000 server then try SMTPDiag again...

(in reply to Cali)
Post #: 15
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 6:52:38 PM   
Cali

 

Posts: 30
Joined: 17.Jul.2006
Status: offline
quote:

ORIGINAL: de.blackman
lets go back to basics then. from the new server,  can you telnet to the old server on port 25 and spoof a message to it? how about the other way around. When i say spoof, i mean create an email from the telnet command prompt.


odd. this past weekend this exact test worked (i think).

today however new_server is not accepting any telnet on port 25.

restarted SMTP service - no change
since it isn't production, rebooted - no change

no firewall
can connected via telnet at local host

my brain hurts - what am i missing.  Looking at creating that MX record pjhutch - thanks for the suggestion.

(in reply to de.blackman)
Post #: 16
RE: Exchange 2003 standard to Exchange 2003 enterprise - 18.Jul.2006 11:10:58 PM   
Cali

 

Posts: 30
Joined: 17.Jul.2006
Status: offline 		ok i havent forgot about the MX record, but it sort of on the back burner now.

I tried googling telnet 25 refused on Exchange 2003

with no luck

this is server 2003 standard sp1
and exchange 2003 enterprise sp2


from old_server I can NOT telnet to new_server 25
from domain_control I can NOT telnet to new_server 25

from another workstation not in the domain I CAN telnet to new_server 25

is this a permission issue? help please.

(in reply to Cali)
Post #: 17
RE: Exchange 2003 standard to Exchange 2003 enterprise - 19.Jul.2006 8:21:22 PM   
Cali

 

Posts: 30
Joined: 17.Jul.2006
Status: offline 		not sure if the two above helpers got fustrated with me or not.

Will it come down to wiping the server clean and starting new?

Simple telnet - works from local machine
but will not function from old_server
also will not function from domain_controller

sometimes I really wish I went down the path of open source....

(in reply to Cali)
Post #: 18
RE: Exchange 2003 standard to Exchange 2003 enterprise - 19.Jul.2006 10:36:41 PM   
de.blackman

 

Posts: 1482
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline 		telnetting should have nothing to do with permissions. is windows firewall enabled on the server? How many NICs are there (enabled or disabled)? if multiple, check the binding order. Any antivirus running on the server? Try stopping any third party service (AV, spam software).

_____________________________

De BlackMan
List Moderator
"Did you backup your Information Store Today?!"

(in reply to Cali)
Post #: 19
RE: Exchange 2003 standard to Exchange 2003 enterprise - 19.Jul.2006 10:41:20 PM   
Cali

 

Posts: 30
Joined: 17.Jul.2006
Status: offline
quote:

ORIGINAL: de.blackman

telnetting should have nothing to do with permissions. is windows firewall enabled on the server? How many NICs are there (enabled or disabled)? if multiple, check the binding order. Any antivirus running on the server? Try stopping any third party service (AV, spam software).



NO windows firewall (service not even started) or 3rd party firewall
NO AV product install yet
2 NICS in the machine; 1 disabled in device manager so effectively 1 active and pingable

I didnt think permissions would have anything to do with it... but I am grabbing at straws now.

(in reply to de.blackman)
Post #: 20

Page:   [1] 2 3   next >   >> << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2003] >> Migration >> Exchange 2003 standard to Exchange 2003 enterprise Page: [1] 2 3   next >   >>
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts