• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 230
  • Last Modified:

Exchange 2000 setup - "object not found" and am I following the correct installation procedure

Hi folks,

I am just trying to get to grips with exchange server and have encoutered a few problems - any help you could give me would be greatly appreciated.

This is the procedure I have followed:

· Fresh installation of Windows 2000 server
· Installed Small Business Server 2000
· Ran internet connection wizard - specifying address of ADSL router and external DNS settings (which were automatically added to the DNS forwarding tabs)
· Having established that things appeared to be working correctly I begain the configuration of exchange
      * First I went into the properties for the default policy under recipients --> recipient policies
      * I added my domain (@mydomain) to the existing active directory domain
      * Second, I added my email account information to the small business pop 3 connector
      *  Third I set up the SMTP connector to use DNS to send (as opposed to a smart host). I ensured that the local bridgehead server had been automatically added. Finally I confirmed that the wildcard had been added to the address space ensuring that emails would be allowed to any domain
      *  Fourth (and finally) I added the relevant email address to the user details in the active directory and set it as primary.


My questions are:

* Is this the "correct" procedure for installing exchange - both generally and in terms of those "best practises" people are always banging on about.

* Everything is sending and receiving fine (internally and externally) but when I hit send and receive in Outlook 2003 I get the following error message:
          Task 'Microsoft Exchange Server' reported error (0x8004010F) : 'The operation failed. An object could not be found.'

Strangely this doesn't happen when it sends and receives automatically

* Finally how do I configure a catchall account from within exchange so that emails sent to non-existent accounts don't get the post master's message

Thanks in advance guys...
0
elliot2002
Asked:
elliot2002
  • 4
  • 3
2 Solutions
 
Ron MalmsteadInformation Services ManagerCommented:
0
 
SembeeCommented:
There is nothing built in for an Exchange "Catch All".

A couple of solutions are around though.
http://support.microsoft.com/?kbid=324021

If you would prefer something pre-built then take a look at Mailbasket Lite http://www.turbogeeks.com/utilities/default.asp

With errors in the Outlook sync log it would help if you posted exactly which element was generating the error. Normally posting the lines immediately above and below the error will show what is causing the problem.

As for the "correct" way to install Exchange, that all depends on your environment.
Using the POP3 connector is something I like to avoid, Exchange prefers to receive email directly using SMTP. If you are on ADSL then you can use SMTP. If you have a dynamic IP address then it is still possible, just requires a little more care with the configuration of your domain. http://www.amset.info/exchange/dynamicip.asp

You may have to change your SMTP Connector to use a smart host (which will be your ISPs SMTP server) as many ISPs will not accept email from an ADSL IP address.

As long as you haven't made any other changes then you should be relay secure as well. Exchange is relay secure out of the box, but people do change things that can open themselves up again.

Finally, we do have an Exchange TA here on EE: http://www.experts-exchange.com/Networking/Email_Groupware/Exchange_Server/

Simon.
Exchange MVP.
0
 
elliot2002Author Commented:
Many thanks for all the feedback,

I will go and see if I can extract any more information from the error log...

I am interested to know what the disadvantages of using pop3 as I have heard this alluded to before but not known exactly why - can you shed any light?

Also I'd like to learn a bit more about what it means to be relay secure - can you explain or point me in the direction of any resources/

Thanks again...
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
elliot2002Author Commented:
Sorry to bombard you with more questions but I really want to get my head round all of this,

I was just looking through that article about dynamic DNS and SMTP retrieving. What I couldn't work out was the basic procedure for configuring Exchange to receive through SMTP.

In an ideal situation with a static IP address:

* How would I go about getting the MX records changed
* What exactly would I need to configure in exchange

cheers...
0
 
SembeeCommented:
Relay secure means that your machine is not an open relay. Spammers like open relays and will find one on the Internet very quickly. Exchange is relay secure out of the box, but inexperienced admins will change things without realising the consequences and turn Exchange in to an open relay.

The major problem with POP3 is that it is too easy to configure the client to download email and not leave a copy on the server. You then have an irate user who has lost their email. Plus there is the additional concern that by default the username and password is sent across the internet in the clear.

With regards to a dynamic IP address, there isn't much to it.
Exchange will accept anything that is thrown at it, so all you need to do is configure your firewall/router to forward traffic on port 25 (SMTP) to the Exchange server. The Exchange server will then deal with the messages, rejecting them etc.

To get the email to the Exchange server in the first place you need to have MX records pointing at your external IP address. Depending on how your domain name registrar works this maybe something that you do, or something that is done for you. You will have to ask them.

An MX record needs to be a host - mail.domain.com. It cannot be an IP address 123.123.123.123. Therefore you will need a host pointing at an IP address, then point the MX record at the host.

Simon.
Exchange MVP.
0
 
elliot2002Author Commented:
Thanks for the in-depth explanation Simon - that's really helpful,

So just to confirm - am I right in thinking that all the configuration for receiving through SMTP is done via your mail provider and router / firewall (and not within exchange) and that exchange just automatically deals with everything that directed to it. Do I need to set anything in the SMTP virtual server properties, or will it just come through and be routed to the appropriate internal address automatically.

Finally - and this really is the last thing - would I use port forwarding from the router configuration menu to forward everything the specific IP Address of my exchange server...

Thanks again.
0
 
SembeeCommented:
Exchange uses the SMTP Server that is supplied as part of IIS. Therefore your router has nothing to do with it - it simply forwards the SMTP traffic to the Exchange server. There is nothing more to setup.

The SMTP component of Exchange accepts the email and then routes it internally as required - eventually putting it in to the correct mailbox. Nothing needs to be done to the SMTP VS for this to happen.

Port forwarding on the router is what you would use. You only need to forward port 25 traffic - which is SMTP. If you are implementing external access to Exchange via OWA, then you will need to forward port 80 (http) or 443 (https).

Simon.
0
 
elliot2002Author Commented:
Many thanks for answering my questions so thoroughly,

And I'm not even going to ask what OWA is ;-)
0

Featured Post

Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now