rpflueger
asked on
Recipient address rejected: User unknown in virtual alias table
I am running a test environment with Virtual PC. I have a W2K DC, W2K Exchange 2K, and XP Pro running on seperate virtual boxes. I have installed and configured Exchange, and installed Outlook 2k3 o nthe XP box. I cna send emails from the XP box to outside domains, but incoming emailsto the test domain are rejected with the following error:
Your message did not reach some or all of the intended recipients.
Subject: email test
Sent: 9/27/2006 6:56 AM
The following recipient(s) could not be reached:
administrator@testlab.net on 9/27/2006 6:56 AM
There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
<mailserver.domain.net #5.5.0 smtp;550 <administrator@testlab.net
All of the research I can find refers to postfix. I am not running postfix, only Exchange 2k.
Your message did not reach some or all of the intended recipients.
Subject: email test
Sent: 9/27/2006 6:56 AM
The following recipient(s) could not be reached:
administrator@testlab.net on 9/27/2006 6:56 AM
There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
<mailserver.domain.net #5.5.0 smtp;550 <administrator@testlab.net
All of the research I can find refers to postfix. I am not running postfix, only Exchange 2k.
are ur mx ercords set up? correctly go to www.dnsreport.com and run tests on your domain name and see what results you get
ASKER
i setup an mx record in dns on the dc. however, since this is a "test lab" environment, there are no mx records to register with isp dns on the internet. the only failure i get from dnsreport.com is an all namesservers respond:
ERROR: Some of your nameservers listed at the parent nameservers did not respond. The ones that did not respond are:
66.102.140.196
Note: If you are running a Watchguard Firebox with DNS Proxy enabled, there may be a bug causing port numbers get mixed up -- if this is the case, you can contact Watchguard to see if they have a fix.
i am not trying to send email via the internet, only from behind my firewall from one private network to another private network behind the same firewall.
ERROR: Some of your nameservers listed at the parent nameservers did not respond. The ones that did not respond are:
66.102.140.196
Note: If you are running a Watchguard Firebox with DNS Proxy enabled, there may be a bug causing port numbers get mixed up -- if this is the case, you can contact Watchguard to see if they have a fix.
i am not trying to send email via the internet, only from behind my firewall from one private network to another private network behind the same firewall.
have you already an ex server in place that is receiving email and that has an mx record pointing to your mail server
you need to get a registered domain name so other people on the internet can see your server and send mail to it
you need to get a registered domain name so other people on the internet can see your server and send mail to it
That isn't an Exchange message.
Therefore something other than your Exchange server is answering for the domain.
Setting up DNS records on the AD DNS server means that the internet doesn't know where to deliver your email.
Are you trying to email in to this site from inside or outside of your network?
If outside, then it will not work.
If inside, then ensure that you aren't using a smart host that sends all email out to the internet. A smart host setting overrides an MX lookup that can be found from DNS.
Simon.
Therefore something other than your Exchange server is answering for the domain.
Setting up DNS records on the AD DNS server means that the internet doesn't know where to deliver your email.
Are you trying to email in to this site from inside or outside of your network?
If outside, then it will not work.
If inside, then ensure that you aren't using a smart host that sends all email out to the internet. A smart host setting overrides an MX lookup that can be found from DNS.
Simon.
ASKER
this is a test environment. i do not need or want to send email to the internet from this exchange server.
i can send emails successfully between email accounts in this test domain. i can also send email successfully from the test domain to accounts in my production domain. it is only when i try to send an email from my production domain to the test domain. are you saying i need to add an mx record to me production domain for the exchange server in the test domain?
i do not have any other "mail server" products running in my production or test domain. i have exchange 2000 running in both domains. i do nto have any linux or unix boxes running on my network. it is strictly a microsoft network, servers, workstations, applications, etc.
i am getting ready to move (in the production domain) from Exchange 2000/Windows 2000 domain to Exchange 2003/Windows2003 domain. i am moving exchange to a new server and wanted to setup the test environment to work out the bugs first, but do not care about sending email to and from the internet.
i can send emails successfully between email accounts in this test domain. i can also send email successfully from the test domain to accounts in my production domain. it is only when i try to send an email from my production domain to the test domain. are you saying i need to add an mx record to me production domain for the exchange server in the test domain?
i do not have any other "mail server" products running in my production or test domain. i have exchange 2000 running in both domains. i do nto have any linux or unix boxes running on my network. it is strictly a microsoft network, servers, workstations, applications, etc.
i am getting ready to move (in the production domain) from Exchange 2000/Windows 2000 domain to Exchange 2003/Windows2003 domain. i am moving exchange to a new server and wanted to setup the test environment to work out the bugs first, but do not care about sending email to and from the internet.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.