SMTP Queue Folder Does Not Move to New Server 2

[rwright]

Mail moved from EX 2000 server to 2003, but message files are being updated on the old server queue folder:
c:\program files\exchsvr\mailrool\vsi1\queue
It has messages that are being updated even after all of the MS Exchange services are stopped on the old server. These are mostly 'undeliverable' messages, or SPAM but I am curious as to why I am getting them. I stopped the Virtual SMTP server on the old server and that stopped the messages from appearing but what did I miss when I moved the mail to the new server?
I followed the MS article (

http://support.microsoft.com/kb/307917/)

about removing the first EX server.

More details: we can send email to the Internet but cannot receive from the internet. Internal is ok.
I started the Virtual SMTP server and the System Attendant service both on the OLD server and that enabled us to receive. All of the other MS Exchange services are stopped and disabled. The folder
c:\program files\exchsvr\mailrool\vsi1\queue
on the OLD server is receiving the messages again. How do I move this to the NEW exchange server?

 

[paulha]

Have you NATted the external ip through to the new server yet ?

 

[rwright]

Good point - I'll check on that. Someone else manages the firewall and DNS so I'll have to confirm the changes were made.
What would cause the files to be on the hard drive of the OLD server with all of the Exchnage services (except System Attetndant) stopped? That's what has me stumped...

Thanks!

 

[rwright]

Well, according to the DNS and firewall admin, the NAT has been created to point to the new server... hummmm, the plot thickens...

I'm stuck - anyone have more ideas???

 

[lebisol]

post your IP or domain name...we can test your port 25 for you....if not a security issue.
if you can ask your admin to share his nat config.

:--------------------------------------:

[URL unfurl="true"]http://mostarnet.com[/url]

All around in my home town,
They tryin' to track me down...

 

[rwright]

pdsindy.com is the domain.

 

[lebisol]

Ok so it seems that mail.pdsindy.com is up and running
on your server called 'pdsappserver' so your port 25 is open/NATed to point to that machine and main MX record points to 68.165.203.18.
So if the 'pdsappserever' is the old exchange 2000 box that means that your firewall has a wrong NAT.
eg.
ip nat inside source static TCP 192.168.1.22 25 68.165.203.18 25 extendable

here is some more quick info on your mail

Non-authoritative answer:
pdsindy.com     MX preference = 10, mail exchanger = mail.pdsindy.com
pdsindy.com     MX preference = 20, mail exchanger = mail2.pdsindy.com
pdsindy.com     MX preference = 30, mail exchanger = mail3.pdsindy.com

>

C:\Documents and Settings\user>ping mail.pdsindy.com

Pinging mail.pdsindy.com [68.165.203.18] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 68.165.203.18:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

-

Pinging mail2.pdsindy.com [63.3.19.171] with 32 bytes of data:

Reply from 152.63.156.142: Destination net unreachable.
Reply from 152.63.156.142: Destination net unreachable.
Reply from 152.63.156.142: Destination net unreachable.
Reply from 152.63.156.142: Destination net unreachable.

Ping statistics for 63.3.19.171:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

-

Pinging mail3.pdsindy.com [209.131.193.197] with 32 bytes of data:

Reply from 209.131.193.197: bytes=32 time=95ms TTL=115
Reply from 209.131.193.197: bytes=32 time=112ms TTL=115
Reply from 209.131.193.197: bytes=32 time=76ms TTL=115
Reply from 209.131.193.197: bytes=32 time=74ms TTL=115

Ping statistics for 209.131.193.197:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 74ms, Maximum = 112ms, Average = 89ms

Now, check you DNS server to make sure MX= correct IP
Hope this helps you...
All the best!


:--------------------------------------:

[URL unfurl="true"]http://mostarnet.com[/url]

All around in my home town,
They tryin' to track me down...

 

[rwright]

Ok, that's the problem because pdsappserver is the OLD exchange server. The new one is PDSMailServer...

Thanks for all of your assistance!

 

[lebisol]

alright then, get this info in your admin hands and tell him/her that Firewall/NAT is NOT configured right.
the part...
eg.
ip nat inside source static TCP 192.168.1.22 25 68.165.203.18 25 extendable

match the bold part to reflect your internal IP of the new server and you should be on your way...
All the best!

:--------------------------------------:

[URL unfurl="true"]http://mostarnet.com[/url]

All around in my home town,
They tryin' to track me down...